no valid Db connection from storage node after upgrade to 1.5.4
-
@Padcotton Sorry, I don’t understand your comment. I was replying to @Sebastian-Roth, no one else.
-
@CoxM Where exactly do you see the failed DB connection error? Can you please take a picture and post here?
-
-
@CoxM Strange thing. Can you please run the following command on your storage node and post results here:
find /var/www/fog -type f -exec grep "FOG_VERSION" {} /dev/null \;
-
-
@CoxM This is strange, not what I expected, can’t replicate the issue and can’t figure out where the message is coming from. Will look into it again.
-
@Sebastian-Roth Thanks
-
@CoxM Please check your config on the updated storage node:
/var/www/fog/lib/fog/config.class.php
Then see if you can connect to the master server’s database using those credentials with the mysql command line client on the storage node:mysql -h POR-FOG -u fogstorage -D fog -p Password: ...
This will probably fail. As the other 1.5.3 node you have is not showing the error I kind of doubt the issue is on the master node. But you can still try to reset the credentials in your master node’s database like that:
mysql -u root -D mysql -p Password: ... ALTER USER 'fogstorage'@'%' IDENTIFIED WITH mysql_native_password BY 'put_password_here';
Please let us know what the issue was. I am wondering if this is something other people run into as well.
-
@Sebastian-Roth Thanks for all your help.
The issues turned out to be the mysql credentials held in the config.class.php file. They had been reset and needed the correct details manually adding. Once that was done all worked fine.
Thanks again,
Matt. -
@CoxM What were the credentials set to. Can you figure out what was wrong. Or did you reset the credentials in the DB to make it work?
-
@Sebastian-Roth Is this db information stored in the .fogsettings file? My thinking is that maybe it was changed/reset in the system before 1.5.4 was installed and the fog installer reset things to the way they were set according to the .fogsettings file(??)
-
@Sebastian-Roth It had reset the user to ‘root’ and the password blank. I have run the ALTER USER commands previously so perhaps that did it.
Once I had manually entered the correct username “fogstorage” and the password, which I still had from the working node, I was up and running.
Thanks,
Matt.