My database connection appears to be invalid?
-
This post is deleted! -
This post is deleted! -
In centos 7 the way to start maridadb on boot is probably:
systemctl eanble mysqld
I’m still waiting to hear back on the commands I posted.
-
systemctl enable mysqld
Typo correction!
I will reboot my FOG server later today and give you the results of your suggestions. Right now I am reveling in the wonders of 5GBps imagine speed. 1.2.0 on my old hardware topped out at 1.2GBps
-
@AngryScientist said in My database connection appears to be invalid?:
Right now I am reveling in the wonders of 5GBps imagine speed. 1.2.0 on my old hardware topped out at 1.2GBps
A lot of that has to do with the performance improvements of FOG 1.3.0 RC, a change was made to how the images are compressed and decompressed for imaging and some people reported 50 to 100% speed increases.
-
RC-22 Officially released.
Please update and hopefully you’ll see all the latest goodies and what not. (Hopefully this will be fixed for you too.)
-
@Tom-Elliott
I know how to do a git pull, but what is the official upgrade procedure? -
-
In very simple terms:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
Essentially, open a terminal.
Cd to the installer directory.
If you loaded the repo from git, make sure you’re on the dev-branch:
git checkout dev-branch
Ensure you’re environment is setup without customizations:
git reset --hard
Pull the latest:
git pull
Cd to the BIN directory:
cd bin
Install as normal.
./installfog.sh -y
-
Time to un-zombie the thread.
I updated to RC-36, and same same. I had to
sudo systemctl start mysqld
to get the database connection running. -
@AngryScientist Are you sure it wasn’t:
systemctl start mysql
or evensystemctl start mariadb
?I’m trying to validate what the problem is here, and I’m fairly sure we’d have seen a bunch of issues with this operationally speaking. (We have a bunch of people using CentOS 7).
-
@AngryScientist It would be interesting to know if the contents of your .fogsettings file is messed up and then upgrading caused the installer to look at bad data again??
My production server is running Centos 7, I think we are on RC34 and that upgraded cleanly.