FOG installation errors

[TaTa]

/etc/my.cnf.d/ exists but it contains no files.

systemctl status mysqld.service
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
   Active: activating (start) since Wed 2019-11-13 11:34:24 EST; 3s ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 44776 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
  Control: 44806 (mysqld)
   CGroup: /system.slice/mysqld.service
           ├─44806 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid --skip...
           └─44809 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid --skip...

Nov 13 11:34:24 fogprodapp01 systemd[1]: Starting MySQL Server...

-- Unit mysqld.service has failed.
--
-- The result is failed.
Nov 13 11:35:30 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
Nov 13 11:35:30 fogprodapp01 systemd[1]: mysqld.service failed.
Nov 13 11:35:30 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
Nov 13 11:35:30 fogprodapp01 systemd[1]: Stopped MySQL Server.
-- Subject: Unit mysqld.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has finished shutting down.
Nov 13 11:35:30 fogprodapp01 systemd[1]: Starting MySQL Server...
-- Subject: Unit mysqld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has begun starting up.
Nov 13 11:35:33 fogprodapp01 nrpe[45775]: warning: /etc/hosts.deny, line 13: missing newline or
Nov 13 11:35:34 fogprodapp01 mysqld[45781]: Unable to determine if daemon is running: No such f
Nov 13 11:35:34 fogprodapp01 systemd[1]: mysqld.service: control process exited, code=exited st
Nov 13 11:35:34 fogprodapp01 systemd[1]: Failed to start MySQL Server.
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has failed.
--
-- The result is failed.
Nov 13 11:35:34 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
Nov 13 11:35:34 fogprodapp01 systemd[1]: mysqld.service failed.
Nov 13 11:35:34 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
Nov 13 11:35:34 fogprodapp01 systemd[1]: Stopped MySQL Server.
-- Subject: Unit mysqld.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has finished shutting down.
Nov 13 11:35:34 fogprodapp01 systemd[1]: Starting MySQL Server...
-- Subject: Unit mysqld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has begun starting up.
[root@fogprodapp01 my.cnf.d]#
[root@fogprodapp01 my.cnf.d]# clear
[root@fogprodapp01 my.cnf.d]# journalctl -xe
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has failed.
--
-- The result is failed.
Nov 13 11:36:00 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
Nov 13 11:36:00 fogprodapp01 systemd[1]: mysqld.service failed.
Nov 13 11:36:00 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
Nov 13 11:36:00 fogprodapp01 systemd[1]: Stopped MySQL Server.
-- Subject: Unit mysqld.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has finished shutting down.
Nov 13 11:36:00 fogprodapp01 systemd[1]: Starting MySQL Server...
-- Subject: Unit mysqld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has begun starting up.
Nov 13 11:36:04 fogprodapp01 mysqld[46228]: Unable to determine if daemon is running: No such f
Nov 13 11:36:04 fogprodapp01 systemd[1]: mysqld.service: control process exited, code=exited st
Nov 13 11:36:04 fogprodapp01 systemd[1]: Failed to start MySQL Server.
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has failed.
--
-- The result is failed.
Nov 13 11:36:04 fogprodapp01 systemd[1]: Unit mysqld.service entered failed state.
Nov 13 11:36:04 fogprodapp01 systemd[1]: mysqld.service failed.
Nov 13 11:36:04 fogprodapp01 systemd[1]: mysqld.service holdoff time over, scheduling restart.
Nov 13 11:36:04 fogprodapp01 systemd[1]: Stopped MySQL Server.
-- Subject: Unit mysqld.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has finished shutting down.
Nov 13 11:36:04 fogprodapp01 systemd[1]: Starting MySQL Server...
-- Subject: Unit mysqld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has begun starting up.

[Sebastian Roth]

@TaTa There should be a log file somewhere in /var/log/mysql/error.log or similar. Please take a look to see why it doesn’t seem to properly start.

[TaTa]

@Sebastian-Roth Thank you for pointing me to the right direction. It was mysqld.pid file that was missing. I created it and re-ran the installation and reached to the point where it asks to update database schema but getting Schema Update Fail. Unable to update schema. I put in the same password during the installation where it asked “Is the MySQL password blank?”. I’m able to mysql -u root -p and put in that same password.

[Sebastian Roth]

@TaTa said in FOG installation errors:

Schema Update Fail. Unable to update schema

Any more information you get about why it fails? Error logs?

[TaTa]

@Sebastian-Roth No error in mysqld log.

[Sebastian Roth]

@TaTa What about Apache und PHP logs?

[Daniel Miller]

You may also have a fog_schema_update_error.log someplace. It looks like schemaupdaterpage.page.php drops that if it encounters an error. I’m not entirely sure where it would drop it, however.

[TaTa]

@Daniel-Miller fog schema update or similar name does not exist in /var/log/fog. Could it be somewhere that I’m not aware of?

[Tom Elliott]

@TaTa under /var/www/fog

[TaTa]

@Tom-Elliott Thank you Tom. It looks like password for fogstorage account password does not meet password policy requirement. Where do I go to change it? I searched in the forums and it looks like there is a fix for it by disabling password validation in mysql https://forums.fogproject.org/topic/11378/fog-show-me-blank-page-on-fresh-install-ubuntu-16-04/12. It would be more ideal if I can change it to a stronger password to meet password policy.

Update ID: 16
Database Error: Failed to query: Error: SQLSTATE[HY000]: General error: 1819 Your password does not satisfy the current policy requirements Error Message: Error Code: "HY000", Error Message: ["HY000",1819,"Your password does not satisfy the current policy requirements"], Debug: SQL: [58] CREATE USER 'fogstorage'@'%' IDENTIFIED BY 'fs30609984138'
Params:  0

[TaTa]

I took are of password policy issue but getting a new error

“HY000”,1396,“Operation CREATE USER failed for ‘fogstorage’@‘%’”]. It doesn’t look like empty hostname as ‘%’.

[TaTa]

I was able to go pass that stage by changing ‘%’ to localhost. I’m not sure if it does any harm. I’m getting “Storage Node Update Warning Unable to connect using ip, user, and/or password provided!” I confirmed that fogproject account has proper access to /images folder. Any thoughts?

[Daniel Miller]

@TaTa The % in the host attribute is the mysql wildcard. This indicates that the user account is allowed to login from any machine. Changing this to localhost means you can only log in from a connection mysql / mariadb explicitly identifies as localhost. Unfortunately, localhost isn’t the only possible identifier possible for a local connection, for example it could use 127.0.0.1, so it is possible that this configuration would deny connections initiated on the same machine, which would result in that storage node warning.

[TaTa]

@Daniel-Miller mysql does not allow using the wildcard. How do i get around it? This might be related to freezing screen when clicking on “Create New Image” and “No master nodes available” when listing all images?

[Daniel Miller]

@TaTa What indicates to you that the wildcard is not allowed? See MySQL’s documentation on creating accounts. It would be helpful to see both the error message encountered as well as the output of select user,host from mysql.user;

[TaTa]

@Daniel-Miller You are right. I checked my other fog server and it does have a wildcard but this one is localhost.

i’m getting this error when creating one using the wildcard (after dropping fogstorage user).
ERROR 1396 (HY000): Operation CREATE USER failed for ‘fogstorage’@‘%’

±--------------±--------------+
| user | host |
±--------------±--------------+
| root | [myserverIP |
| fogstorage | localhost |
| mysql.session | localhost |
| mysql.sys | localhost |
| root | localhost |
±--------------±--------------+

[Sebastian Roth]

@TaTa said in FOG installation errors:

ERROR 1396 (HY000): Operation CREATE USER failed for ‘fogstorage’@’%’

No more error message???

[TaTa]

@Sebastian-Roth No more. Just that single line.

[Daniel Miller]

@TaTa each username-host pairing is considered a distinct user, so there is no need to drop fogstorage@localhost before adding fogstorage@‘%’. That being said, if the user fogstorage@‘%’ has existed in the MySQL instance at any time since either A) the MySQL service has been restarted or B) the privilege table has been reloaded, the user you are attempting to add likely still exists in memory which would result in error 1396 if you attempt to add the same user again. Try restarting the mysql service or performing a flush privileges; in mysql and try again.

[TaTa]

@Daniel-Miller I did flush privileges a few times before reporting it. I even restarted the server a few times/ stopped/started mysql but no go.