Database issue on latest trunk

[Bob Henderson]

8132 . I pulled from git earlier this morning. I was on um…7875 I think?

This vm does nothing but FOG, so last night I had went in to update it as I usually did weekly-ish, came back to this this morning.

[plegrand]

MAy be you should find out these :
define(‘DATABASE_HOST’,’’);
define(‘DATABASE_USERNAME’,’’);
define(‘DATABASE_PASSWORD’,“”); if there is a password

[Bob Henderson]

@plegrand

Yep, just pulled this in from my backup of the machine.

Before hand, it had the right credentials, root setup and everything as normal.

After the update, it did not.

Odd?

[plegrand]

@Bob-Henderson yes i noticed that also but if you find out these fields it will be work again
Are you sure that you have space enough in all your partitions ?
df -h

[Tom Elliott]

@Bob-Henderson Is this a storage node, or main server?

[Bob Henderson]

@Tom-Elliott

Main server, stand alone. Was working fine until I did the update.

Adding in the host and username resolved the issue instantly.

[Tom Elliott]

@Bob-Henderson and what displays in the /opt/fog/.fogsettings file for the snmysqlhost and snmysqluser information?

[Bob Henderson]

@plegrand

Yep, nothing is over 35% used.

[Bob Henderson]

@Tom-Elliott

Well, that’s odd, those are all blank. No user, pass, host.

It has all my other settings still, like IP and password and such.

[Tom Elliott]

@Bob-Henderson I’m asking to help you.

Please enter your information. ON Main server, the snmysqlhost should be '127.0.0.1'
snmysqluser should be 'root'
snmysqlpass (unless you set a password) should be ''

[plegrand]

@Bob-Henderson I dont know if tom agree with that but i find out these fields :
snmysqluser=‘root’
snmysqlhost=‘127.0.0.1’

[Bob Henderson]

@Tom-Elliott

I’ve put those in now, and had verified that if I put them into config.class.php manually, I got database connection back as well.

So we’ve figured out what broke, but I’m sorta confused as to why it happened in the first place? I appreciate the help, just wouldn’t want someone else to update and get the same issue.

[Bob Henderson]

I just went and updated another node via git as well, and it did the same thing. It appears it wipes out the SQl settings in the fogsettings file. Adding them back in fixes it, but obviously isn’t what we’d want.

[Tom Elliott]

@Bob-Henderson I don’t think it’s wiping them out. It simply has no idea how to handle it from the prior config. I’ll see if I can make some better guesses though.

[Tom Elliott]

Should be fixed in latest…hopefully.

[Bob Henderson]

@Tom-Elliott

no dice. Just updated the testing node to 8138, same issue. Putting the info back in config.class.php gets connection back, but it didn’t have them originally.

[Tom Elliott]

@Bob-Henderson and now after another update?

[Bob Henderson]

@Tom-Elliott

Sorry for the delay, busy day.

Updated to 8143, all seems good.

[cnewman402]

CentOS 7?
sudo su -
setsebool -P httpd_can_network_connect 1

[Wayne Workman]

@cnewman402 This thread is two months old and has been solved. Do you have a similar problem?