New fog server installation 1.5.8 on centos 7

[Mightmar]

hello again, with new installation we have now node offline,

and version 1.5.9 RC

it was after 2 unsuccessful installations at begin, do we mess something, how to check it?

[Sebastian Roth]

@Mightmar Let’s start with the basics. Did you disable SELinux and the firewall?

[Mightmar]

Hi Sebastian, yes both are disabled basing on this https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
what else to check ?

[Sebastian Roth]

@Mightmar Did the installer run all the way to the end? Please take a look in the bin directory where you ran the installfog.sh script. Find a subdir called error_logs in there and two log files. Post the last 10 lines of both logs here.

[Mightmar]

fog_error_1.5.9. RC.log

Jul 08 16:06:23 PLGDVFOG01 systemd[1]: Starting The PHP FastCGI Process Manager...
Jul 08 16:06:23 PLGDVFOG01 systemd[1]: Started The PHP FastCGI Process Manager.
--2020-07-08 16:06:26--  https://10.180.8.90//fog//maintenance/backup_db.php
Connecting to 10.180.8.90:443... connected.
WARNING: cannot verify 10.180.8.90's certificate, issued by ‘/CN=FOG Server CA’:
  Self-signed certificate encountered.
HTTP request sent, awaiting response... 302 Found
Location: ?node=schema [following]
--2020-07-08 16:06:26--  https://10.180.8.90//fog//maintenance/backup_db.php?node=schema
Connecting to 10.180.8.90:443... connected.
WARNING: cannot verify 10.180.8.90's certificate, issued by ‘/CN=FOG Server CA’:
  Self-signed certificate encountered.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/home//fogDBbackups/fog_sql_1.5.9-RC2_20200708_040626.sql’

     0K .                                                      70.1M=0s

2020-07-08 16:06:26 (70.1 MB/s) - ‘/home//fogDBbackups/fog_sql_1.5.9-RC2_20200708_040626.sql’ saved [1305]

ERROR 1146 (42S02) at line 1: Table 'fog.globalSettings' doesn't exist

fog install. log

   To improve the overall security the installer will create an
   unpriviledged database user account for FOG's database access.
   Please provide the database *root* user password. Be asured
   that this password will only be used while the FOG installer
   is running and won't be stored anywhere: 

OK
 * Backing up user reports.....................................Done
 * Stopping web service........................................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 the language binaries..............................Done
 * Creating config file........................................OK
 * Downloading kernel, init and fog-client binaries............Done
 * Copying binaries to destination paths.......................OK
 * 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 (SSL)........................OK
 * Starting and checking status of web services................OK
 * Changing permissions on apache log files....................OK
 * Backing up database.........................................Done

 * You still need to install/update your database schema.
 * This can be done by opening a web browser and going to:

   https://10.180.8.90/fog/management

 * Press [Enter] key when database is updated/installed.
 * Update fogstorage database password.........................Failed!

[Sebastian Roth]

@Mightmar I assume you hit ENTER before opening the URL to let it do it’s magic DB schema creation/update.

Well, no problem. Just re-run the installer exactly as you did before. This time it doesn’t matter if you really open the web interface URL at the right point because the schema should be updated already.

[Mightmar]

its working, thank you!