@GFm Good to know, thanks for testing and reporting back.

Hey All, the issue was resolved. Its the problem with php.ini -> time zone not set. After going through same problem & solution in other thread - tried the same. Set the time zone and removed leading ;

This successfully completed the schema update and installation.

Thanks for your great help guys!

Just wanted to update. I have been busy here at work so I have not been able to do anymore testing on the init files. So sorry for the delay.

@Sebastian-Roth Yes this issue has been resolved with the update

@cortoM This might be solving it for you but it actually really just a quick hack. If you are still keen to find out why FOG is choosing the wrong device on your system we need more information. See Wayne’s and my previous post.

@Sebastian-Roth @Tom-Elliott

Gentlmen, that fixed the issue. Thank you so much for your support!!! You guys are the bomb!!!

Chris

@Wayne-Workman
Ok, thanks for your precisions, i’ll work on NFS storage later.

Perfect now! Installer and configs are all correct. From my side the problem is solved. Thanks!

@Sebastian-Roth Sounds good yeah, I’d love to help out 🙂

@Sebastian-Roth Good points.

@Wayne-Workman ok. I wish we could have come out with an answer. I guess it was just a PMS moment.

@Wayne-Workman said:

@jayphizzle said:

Can some mod mark the tread as unsolved?
Or should i open a new thread?

I’d say open a new thread, I’d call this a bug as it doesn’t work right if a different language is being used by the system.

@Jbob

Ok ‘new’ Bug reported here: https://forums.fogproject.org/topic/6934/endless-windows-key-activation-burning-oem-keys

@ch3i said:

@boeleke The legacy password is for the legacy client : it’s useless in your case.
Could you post the fog.log present on a client at c:\fog.log ?

Hi ch3i,

i was testing it again today & all i working fine till now.
Thanks!

Bump… would be good for CentOS fresh install as well.

@Sebastian-Roth Thank You Sebastian. Really appreciate all developers effort here. FOG is wonderful tool. I simply love it. You guys are extremely responsive as well.

@BardWood I don’t think it will work. The FOG Trunk methods involved with synchronizing storage nodes with their masters has greatly changed, along with the ability to now cross-share images with storage groups. I would not advise mixing versions as you would like, I think it’ll only lead to disaster. The location plugin has also been modified to cause remote nodes at a remote location to PXE boot directly from their local node. Also, the 1.2.0 nodes probably can’t support this functionality

You’d be better off just updating everything to fog trunk, OR just staying at 1.2.0 till 1.3.0 is released.

@Sebastian-Roth I’m in the habit now of looking at what is stored in the DB for the nfsGroupMembers table. His credentials stored there worked for connecting to the fog server via FTP. 😕

I also checked firewall and SELinux. Both were disabled.

Only thing I could see that was different and unusual was PHP 7.

That said - I don’t disagree with a packet capture.

Needed to not use root as msqluser for storage node.
Set it back to fogstorage with password from the fog webgui fog config →fog settings → storage node settings (something like that)
Put that in the storage node servers /opt/fog/.fogsettings and redid the install again. All is well again

@Sebastian-Roth The real question is the original issue that caused this post to be opened in the first place fixed?

@Kiweegie, are you solving this because the password/snapin issue is fixed or your server is no longer sufferring from the High CPU Usage from multiple httpd processes?