Fog Installation Error - Cannot restart MySQL
-
Server
- FOG Version: 1.3.0-RC2
- OS: Centos 6
Description
I’m trying to update from RC2 to the latest (RC13 but this happend on RC11 as well).
The installation fails when trying to restart mysql. The error looks like this:
* Setting up and starting MySQL...............................Failed!
When I try to manually start mysql after that I get this:
/etc/init.d/mysqld: line 103: syntax error near unexpected token `fi' /etc/init.d/mysqld: line 103: ` fi'
So I go into the mysqld init file and I see the following:
# If startsos if [ "$1" = "sos" ] ; then # MYOPTIONS="$MYOPTIONS --skip-grant-tables --skip-networking" fi
When I remove the comment from the MYOPTIONS line, everything starts correctly, but fog is still on RC2.
Any thoughts?
-
in bash, if statements cannot have empty ‘happenings’.
Comment out all three lines and try again.
-
The reason it’s still showing rc2 is most likely due to what I call bleedover.
Please run:
sudo rm -rf /var/www/fog /var/www/html/fog
then rerun the installer. -
I removed the folder and reran the installer and it still fails. It doesn’t create any files in /var/www/fog or /var/www/html/fog
How do I change the installer so that it doesn’t overwrite my myslqd init file?
-
@88fingerslukee the installer does not touch any init files. Ever.
-
@88fingerslukee clarify it only installs the fog service init files
-
I don’t know how to clarify that. What I know is that the installer fails at trying to restart mysqld. If I edit the mysqld init file adn re-run the installer, the init file is overwritten.
Nothing else gets installed because of the failure.
-
@88fingerslukee FOG is not rewriting the init.d file. My “clarify” is referring to me clarifying that we only install the fog service files.
-
So apparently, unbeknownst to me, the init.d was being commented simply because it contains one of the things I’m searching for (skip-networking). I’m sorry I screwed it up Please forgive?
-
@88fingerslukee Thanks for the remote session. I’d have never found it. This makes sense though. The other threads that had the issue only stated the uncommented it and things worked, I didn’t know this was happening on any re-install.