I tried again and saw this in the fog error log:

With all the failed to stop fog services and failed to stop/start mysql, could this be the issue? I simply let the script do its thing so not sure why the below stuff would be failing.

New password: Retype new password: Changing password for user fog.
passwd: all authentication tokens updated successfully.
Failed to stop FOGMulticastManager.service: Unit FOGMulticastManager.service not loaded.
Failed to stop FOGImageReplicator.service: Unit FOGImageReplicator.service not loaded.
Failed to stop FOGSnapinReplicator.service: Unit FOGSnapinReplicator.service not loaded.
Failed to stop FOGScheduler.service: Unit FOGScheduler.service not loaded.
Failed to stop FOGPingHosts.service: Unit FOGPingHosts.service not loaded.
Failed to stop FOGSnapinHash.service: Unit FOGSnapinHash.service not loaded.
Failed to stop FOGImageSize.service: Unit FOGImageSize.service not loaded.
Failed to execute operation: No such file or directory
Failed to stop mysql.service: Unit mysql.service not loaded.
Failed to start mysql.service: Unit not found.
Unit mysql.service could not be found.
Failed to execute operation: No such file or directory
Failed to stop mysqld.service: Unit mysqld.service not loaded.
Failed to start mysqld.service: Unit not found.
Unit mysqld.service could not be found.
Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /usr/lib/systemd/system/mariadb.service.
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2018-05-07 16:26:05 EDT; 2s ago
Process: 18790 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
Process: 18711 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 18789 (mysqld_safe)
CGroup: /system.slice/mariadb.service
├─18789 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─18951 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock

May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: MySQL manual for more instructions.
May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: Please report any problems at http://mariadb.org/jira
May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: The latest information about MariaDB is available at http://mariadb.org/.
May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: You can find additional information about the MySQL part at:
May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: http://dev.mysql.com
May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: Consider joining MariaDB’s strong and vibrant community:
May 07 16:26:02 mcs-fog-cen7 mariadb-prepare-db-dir[18711]: https://mariadb.org/get-involved/
May 07 16:26:02 mcs-fog-cen7 mysqld_safe[18789]: 180507 16:26:02 mysqld_safe Logging to ‘/var/log/mariadb/mariadb.log’.
May 07 16:26:02 mcs-fog-cen7 mysqld_safe[18789]: 180507 16:26:02 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
May 07 16:26:05 mcs-fog-cen7 systemd[1]: Started MariaDB database server.
Failed to stop FOGMulticastManager.service: Unit FOGMulticastManager.service not loaded.
Failed to stop FOGImageReplicator.service: Unit FOGImageReplicator.service not loaded.
Failed to stop FOGSnapinReplicator.service: Unit FOGSnapinReplicator.service not loaded.
Failed to stop FOGScheduler.service: Unit FOGScheduler.service not loaded.
Failed to stop FOGPingHosts.service: Unit FOGPingHosts.service not loaded.
Failed to stop FOGSnapinHash.service: Unit FOGSnapinHash.service not loaded.
Failed to stop FOGImageSize.service: Unit FOGImageSize.service not loaded.
Failed to execute operation: No such file or directory
Failed to stop mysql.service: Unit mysql.service not loaded.
Failed to start mysql.service: Unit not found.
Unit mysql.service could not be found.
Failed to execute operation: No such file or directory
Failed to stop mysqld.service: Unit mysqld.service not loaded.
Failed to start mysqld.service: Unit not found.
Unit mysqld.service could not be found.
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2018-05-07 16:26:48 EDT; 2s ago
Process: 19204 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
Process: 19173 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 19203 (mysqld_safe)
CGroup: /system.slice/mariadb.service
├─19203 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─19366 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock

May 07 16:26:45 mcs-fog-cen7 systemd[1]: Starting MariaDB database server…
May 07 16:26:46 mcs-fog-cen7 mariadb-prepare-db-dir[19173]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
May 07 16:26:46 mcs-fog-cen7 mysqld_safe[19203]: 180507 16:26:46 mysqld_safe Logging to ‘/var/log/mariadb/mariadb.log’.
May 07 16:26:46 mcs-fog-cen7 mysqld_safe[19203]: 180507 16:26:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
May 07 16:26:48 mcs-fog-cen7 systemd[1]: Started MariaDB database server.
find: ‘/home//fog_web_1.5.2.BACKUP/management/other/’: No such file or directory
Archive: binaries1.5.2.zip
creating: packages/kernels/
inflating: packages/kernels/bzImage
inflating: packages/kernels/bzImage32
creating: packages/inits/
inflating: packages/inits/init_32.xz
inflating: packages/inits/init.xz
creating: packages/clientfiles/
extracting: packages/clientfiles/FOGCrypt.zip
extracting: packages/clientfiles/FogService.zip
inflating: packages/clientfiles/SmartInstaller.exe
inflating: packages/clientfiles/FOGService.msi
inflating: packages/FOGService.msi
inflating: packages/inits/arm_init.cpio.gz
‘…/packages/clientfiles/FOGCrypt.zip’ -> ‘/var/www/html/fog//client/FOGCrypt.zip’
‘…/packages/clientfiles/FOGService.msi’ -> ‘/var/www/html/fog//client/FOGService.msi’
‘…/packages/clientfiles/FogService.zip’ -> ‘/var/www/html/fog//client/FogService.zip’
‘…/packages/clientfiles/SmartInstaller.exe’ -> ‘/var/www/html/fog//client/SmartInstaller.exe’
‘…/packages/kernels/bzImage’ -> ‘/var/www/html/fog//service/ipxe/bzImage’
‘…/packages/kernels/bzImage32’ -> ‘/var/www/html/fog//service/ipxe/bzImage32’
‘…/packages/inits/arm_init.cpio.gz’ -> ‘/var/www/html/fog//service/ipxe/arm_init.cpio.gz’
‘…/packages/inits/init_32.xz’ -> ‘/var/www/html/fog//service/ipxe/init_32.xz’
‘…/packages/inits/init.xz’ -> ‘/var/www/html/fog//service/ipxe/init.xz’
Created symlink from /etc/systemd/system/multi-user.target.wants/httpd.service to /usr/lib/systemd/system/httpd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/php-fpm.service to /usr/lib/systemd/system/php-fpm.service.

@george1421 said in Blank Install Screen Issue, no fogsettings file - Centos 7:

@martinetwork If there isn’t any .fogsettings (i.e. its a hidden file, visible with ls -la in that directory) then your foginstall.sh script didn’t complete. Writing out that configuration file is one of the last things the installer does. If that file is missing then the install is botched.

Unfortunately your apache error log looks suspiciously like the apache service log. I’m not seeing any errors in that log to be concerned about.

Yes, I had checked with ls -al… no fogsettings file. Would that be the more pressing issue then? Also, should the file already be there at this point:

• You still need to install/update your database schema.

• This can be done by opening a web browser and going to:

  http://10.x.x.x/fog/management

• Press [Enter] key when database is updated/installed.

What about the line in the error log: No slotmem from mod_heartmonitor?

Mon May 07 15:33:27.211347 2018] [core:notice] [pid 21443] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Mon May 07 15:33:27.213829 2018] [suexec:notice] [pid 21443] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon May 07 15:33:27.267898 2018] [auth_digest:notice] [pid 21443] AH01757: generating secret for digest authentication …
[Mon May 07 15:33:27.269661 2018] [lbmethod_heartbeat:notice] [pid 21443] AH02282: No slotmem from mod_heartmonitor
[Mon May 07 15:33:27.315001 2018] [mpm_prefork:notice] [pid 21443] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured – resuming normal operations
[Mon May 07 15:33:27.315061 2018] [core:notice] [pid 21443] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’

I also just did the install from scratch all over again and have the same issue. Any where else that could be causing this issue???

Also shouldn’t there be a .fogsettings file already in /opt/fog?

Here is the error log:

[Sun May 06 03:13:02.714777 2018] [auth_digest:notice] [pid 25456] AH01757: generating secret for digest authentication …
[Sun May 06 03:13:02.716283 2018] [lbmethod_heartbeat:notice] [pid 25456] AH02282: No slotmem from mod_heartmonitor
[Sun May 06 03:13:02.908076 2018] [mpm_prefork:notice] [pid 25456] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured – resuming normal operations
[Sun May 06 03:13:02.908100 2018] [core:notice] [pid 25456] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
[root@mcs-fog-cen7 httpd]# cat error_log-20180506
[Fri May 04 15:00:55.615223 2018] [core:notice] [pid 22934] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri May 04 15:00:55.617006 2018] [suexec:notice] [pid 22934] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using fe80::fa9d:ff02:2457:8d8c. Set the ‘ServerName’ directive globally to suppress this message
[Fri May 04 15:00:55.662772 2018] [auth_digest:notice] [pid 22934] AH01757: generating secret for digest authentication …
[Fri May 04 15:00:55.664502 2018] [lbmethod_heartbeat:notice] [pid 22934] AH02282: No slotmem from mod_heartmonitor
[Fri May 04 15:00:55.731448 2018] [mpm_prefork:notice] [pid 22934] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured – resuming normal operations
[Fri May 04 15:00:55.731489 2018] [core:notice] [pid 22934] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
[Fri May 04 15:09:04.960288 2018] [mpm_prefork:notice] [pid 22934] AH00170: caught SIGWINCH, shutting down gracefully
[Fri May 04 15:09:06.084758 2018] [core:notice] [pid 24291] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri May 04 15:09:06.086677 2018] [suexec:notice] [pid 24291] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri May 04 15:09:06.132564 2018] [auth_digest:notice] [pid 24291] AH01757: generating secret for digest authentication …
[Fri May 04 15:09:06.133924 2018] [lbmethod_heartbeat:notice] [pid 24291] AH02282: No slotmem from mod_heartmonitor
[Fri May 04 15:09:06.191680 2018] [mpm_prefork:notice] [pid 24291] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured – resuming normal operations
[Fri May 04 15:09:06.191727 2018] [core:notice] [pid 24291] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
[Fri May 04 15:16:34.074263 2018] [mpm_prefork:notice] [pid 24291] AH00170: caught SIGWINCH, shutting down gracefully
[Fri May 04 15:16:35.202779 2018] [core:notice] [pid 25456] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Fri May 04 15:16:35.204918 2018] [suexec:notice] [pid 25456] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri May 04 15:16:35.260768 2018] [auth_digest:notice] [pid 25456] AH01757: generating secret for digest authentication …
[Fri May 04 15:16:35.262292 2018] [lbmethod_heartbeat:notice] [pid 25456] AH02282: No slotmem from mod_heartmonitor
[Fri May 04 15:16:35.293777 2018] [mpm_prefork:notice] [pid 25456] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 configured – resuming normal operations
[Fri May 04 15:16:35.293812 2018] [core:notice] [pid 25456] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
[Sun May 06 03:13:02.530914 2018] [mpm_prefork:notice] [pid 25456] AH00171: Graceful restart requested, doing restart

Hello all,

I am using Centos 7.4 to install fog.

Everything seems to go well with no errors during the install. It says to go to a link to finish with the database. Problem is that when I go to that link the page is completely blank.

I did see one error with Apache regarding ServerName. I changed that and no longer receive that httpd warning but still the screen is blank.

When I go to /opt/fog I don’t see any file called .fogsettings. Is there another place that file should be or am I not far enough along the install process to see it?

Please would love help. Attached should be the error log and coped below are a few last lines of the install log.

I used instructions found here: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#CentOS_7_pre-config

Last lines of install log

• Stopping FOGPingHosts.service Service…OK

• Stopping FOGSnapinHash.service Service…OK

• Stopping FOGImageSize.service Service…OK

• Setting up and starting MySQL…OK

• Setting up Apache and PHP files…OK

• Testing and removing symbolic links if found…OK

• Backing up old data…OK

• Copying new files to web folder…OK

• Creating config file…OK

• Downloading binaries needed…OK

• Unzipping the binaries…Done

• Copying binaries where needed…Done

• Enabling apache and fpm services on boot…OK

• Creating SSL CA…OK

• Creating SSL Private Key…OK

• Creating SSL Certificate…OK

• Creating auth pub key and cert…OK

• Resetting SSL Permissions…OK

• Setting up Apache virtual host (no SSL)…OK

• Starting and checking status of web services…OK

• Changing permissions on apache log files…OK

• Backing up database…OK

• You still need to install/update your database schema.

• This can be done by opening a web browser and going to:

  fog/management0_1525461543512_fog_error_1.5.2.log

Also the link is version 0.29 does that still apply to version 1.4.4?

@wayne-workman I already have WOL enabled on my network though. Plus our PDQ server uses WOL as well and it is working fine. The link above talks about enabling forwarding (which I did and is working on a different server that uses WOL broadcasts). The plugin appears to be more for networks that do not allow WOL broadcasts.

If my network allows broadcast forwarding across vlans, I should not need the plug-in right?

@wayne-workman I saw that there is a plug-in but it looks like it is more for if broadcast forwarding is not turned on for the network. In my case, broadcast forwarding is turned on for the network. WOL is working for our PDQ server to be able to broadcast to different subnets but does not work for the FOG server even though both servers are originating from the same network.

@tom-elliott What is wolbroadcast and could you provide more information? I have been tasked with getting this working on the network for someone else’s fog server so not too familiar with all the terms. Yes, I know WOL is a broadcast. Thanks.

Hi I am running FOG version 1.4.3 on Centos 7. I can’t seem to get Wake On Lan to work. I can have allowed broadcasts to over UDP ports 7 - 9. I can see it even allowed through the firewall but the machine does not turn on.

Machines in the same subnet turn on, however. Is there something that I possibly need to configure on the FOG server to turn on servers in different VLANs?

Thanks