FOG installation errors
-
@TaTa Ok, so seems like there never was a DB server installed. To resolve this issue I’d consider removing the package
mariadb101u-config
manually. As you can see here it should hold the “config file my.cnf and my.cnf.d directory”. Probably best to take backup copies of those files before remove the package. Usefind /etc -iname "*my*"
to get a list of files to backup.Then run
yum remove mariadb101u-config
and changefogproject/lib/redhat/config.sh
again. Put inmysql-community-client mysql-community-server
instead ofmariadb mariadb-server
and re-run the installer. -
@Sebastian-Roth Thank you! I’m getting a bit further. The installer can’t set a password for fogproject account due
New password: BAD PASSWORD: The password is shorter than 14 characters.
Is there a way I can set it manually or change password length in the script so will be 14 characters or more? -
@TaTa Take a look at
fogproject/lib/common/functions.sh
line 1261. At the end of the line where it says.../dev/urandom | fold -w12 | head -n1)
change the figure12
to a higher value.By the way. If you want to install with a proper root password set for the database you will run into an issue with the current version. I hope to get this fixed soon!
-
@Sebastian-Roth I changed it to 14 and 16 but is getting this error. Looks like password is not complex enough
Changing shell for fogproject. New password: BAD PASSWORD: The password contains less than 1 digits Retype new password: BAD PASSWORD: is too simple Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service Changing password for user fogproject. New password: Retype new password: Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service New password: BAD PASSWORD: The password contains less than 1 uppercase letters Retype new password: BAD PASSWORD: is too simple Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service Changing password for user fogproject. New password: Retype new password: Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service Changing password for user fogproject. New password: Retype new password: Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service Changing password for user fogproject.
-
@TaTa The data being pulled in for the password is out of urandom, so it is not implausible that, as the log indicates, a given line may not include a digit or upper case letter. You may be able to run the installer a few more times and get a random password that conforms to the system’s password requirements. You may also be able to create a partial
/opt/fog/.fogsettings
with strong passwords compliant with your systems password policies. Format and settings are available in the Wiki. I haven’t tested this, but my understanding is that anything not set in.fogsettings
is requested by the installer.Edit: the setting you are likely interested in is
password=
. -
@Daniel-Miller I created the files but it’s still not working. This is a new installation. I don’t think it looks into .fogsettings before creating this new account.
-
I no longer getting password too simple. It looks like it’s not accepting the password. I can set password for fogproject manually but the installation does not like this account created beforehand.
Changing password for user fogproject. New password: Retype new password: Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service Changing password for user fogproject. New password: Retype new password: Retype new password: Password change aborted. New password: Password change aborted. New password: Password change aborted. passwd: Have exhausted maximum number of retries for service Changing password for user fogproject.
-
@TaTa hmm … weird. You might try using chpasswd instead of passwd. I think that is available in RHEL … maybe by default. If it is, in functions.sh#L1262, change:
echo -e "$password\n$password" | passwd $username >>$workingdir/error_logs/fog_error_${version}.log 2>&1
to
echo -e "$username:$password" | chpasswd >>$workingdir/error_logs/fog_error_${version}.log 2>&1
Don’t have a RHEL system handy to test it with, however.
-
@TaTa Actually, what is the result of
getenforce
?Was searching around a bit and apparently, SELinux can cause some strange behavior…
https://forums.fogproject.org/topic/6926/setting-up-fog-password-fails-on-clean-new-centos-7-installInstructions for setting SELinux to permissive or disabled can be found at https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
-
@Daniel-Miller Thank you for your replies. I already set it to permissive. Changing line 1262 to
echo -e "$username:$password" | chpasswd >>$workingdir/error_logs/fog_error_${version}.log 2>&1
solved setting up passsword issue for fogproject account.I went to update database schema but getting
Database connection unavailable
. It looks like mysqld is not starting. In /etc/my.cnf files (I can’t find /etc/mysql/my.cnf), socket is pointing to /var/lib/mysql/mysql.sock. I checked mysql.sock and the file exists.mysql -u root and mysql -u root -p gave me
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
Trying to restart mysql gave me this error:
Redirecting to /bin/systemctl restart mysql.service Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
-
@TaTa I think your server config file should be at
/etc/my.cnf.d/server.cnf
.
Can you post the output ofsystemctl status mysqld.service
andjournalctl -xe
? -
/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.
-
@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. -
@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. -
@TaTa said in FOG installation errors:
Schema Update Fail. Unable to update schema
Any more information you get about why it fails? Error logs?
-
@Sebastian-Roth No error in mysqld log.
-
@TaTa What about Apache und PHP logs?
-
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.
-
@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?
-
@TaTa under /var/www/fog