FOG installation errors

[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.

[Daniel Miller]

@TaTa What is the result of select vvalue from fog.schemaVersion;?

[TaTa]

@Daniel-Miller I was able to update database schema. I have to created the account with localhost and altered fogstorage account and set the host to ‘%’ but storage node and create new image still didn’t work. Then I deleted fogstorage and fog database and uninstalled fog and then reinstalled FOG and was able to update database schema without issue. But Storage node and creating new image still don’t work. I’m pretty sure there are some settings in mysql that is causing this.

[Daniel Miller]

@TaTa said in FOG installation errors:

But Storage node and creating new image still don’t work.

What message(s) appear when accessing the storage node or attempting to create a new image? Can you post the Apache error (/var/log/httpd/error_log), php error (/var/log/php*-fpm.log), and mysql error logs (/var/log/mysql/error)? It may also be helpful to verify your error log verbosity is at least 2 in your my.cnf.

[TaTa]

I re-ran the installation. Everything was working properly. I rebooted the server. the same issues came back. Re-ran installation, issue fixed. How do I make sure all of the required services are running?

[Sebastian Roth]

@TaTa said in FOG installation errors:

the same issues came back.

Which exact issue do you mean. Since starting the topic we ran into half a dozen issues and I am not sure which one you see now.

[TaTa]

@Sebastian-Roth Storage Node unable to connect and create a new image in Images/Create new images