High CPU usage from multiple httpd processes version 5800

[george1421]

FWIW, I have mine set to 900 seconds. I don’t deploy snapins post deployment or issue unattended deployments. There is no real value (in my environment) to have a client check-ins faster than every 15 minutes.

[Kiweegie]

@Tom-Elliott Morning Tom not sure if related to changes you made for me late last week or a new issue but since the teamviewer session we had, deployment of images fails with error below:

The offending line in path /var/www/html/fog/lib/fog/fogftpclass.php is on line 104

      if (@ftp_login(self::$link,$username,$password) === false) self::ftperror();

no credentials have changed at all. Snapins deploy fine, only images are affected and we have tried with multiple images.

regards, Kiweegie.

[Tom Elliott]

@Kiweegie I’m not able to replicate this. If snapins are working off of the same nodes that are not sending the image, then is something potentially wrong with how the images are mounted on that system? I know it’s stating an FTP error, so it’s a wee bit odd.

[Kiweegie]

@Wayne-Workman @george1421 Hi Wayne/George

Where do I find the client checkin time setting? I’ve checked fog settings and nothing shows up there. Could you point me in the right direction please?

cheers Kiweegie

[Tom Elliott]

@Kiweegie FOG Configuration Page->FOG Settings->FOG Service->FOG_SERVICE_CHECKIN_TIME,FOG_GRACE_TIMEOUT

[george1421]

@Kiweegie FOG Configuration->FOG Settings->FOG Service->FOG_SERVICE_CHECKIN_TIME

[Kiweegie]

@george1421 said:

FOG Configuration->FOG Settings->FOG Service->FOG_SERVICE_CHECKIN_TIME

cheers George!

[Kiweegie]

@Tom-Elliott Hi Tom unfortunately I was going off the information passed to me by my service desk… which turns out to not be as accurate as I thought

I’ve tried deploying snapin and while there is no error thrown up in the GUI, c:\fog.log on target machine shows the same error as seen when trying to deploy image.

 14/03/2016 13:35 Middleware::Communication Unknown Response: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 104, Message: ftp_login(): Login incorrect.

This would suggest that the fog or ftp user password has been changed but it has not been altered at least not by me. Entry in following 2 locations matched what I had in keepass

Storage Management > All Storage nodes > DefaultMember > Management Password
FOG Configuration > FOG Settings > TFTP Server > FOG_TFTP_FTP_Password

However, resetting the fog user password at commandline fixed the issue…

Don’t understand who or what amended that password as only I have access to the box and it sure wasn’t me!

cheers . Kiweegie.

[Wayne Workman]

@Kiweegie The installer a week to two weeks ago set it wrong if there were certain special characters present in the password. It’s since been fixed though. You should verify that what is inside of .fogsettings is correct, and what shows up for the user/pass in the storage management area is correct, and for the kernel update stuff too. All of this is outlined in the “Troubleshoot FTP” wiki article.

[Sebastian Roth]

@Kiweegie I vaguely remember @Wayne-Workman having seen a fog user password change after running the installer script at some point. Maybe this is related? https://forums.fogproject.org/topic/6649/storage-node-installation-resets-local-fog-user-s-password-to-something-wrong

Cannot actually find the commit that was made to fix this but from what Tom says I thought this was fixed somewhere around version 63xx. Maybe not? Please keep an eye on this and let us know!

[Kiweegie]

@Wayne-Workman HI Wayne thanks for the heads up. fog password in this case is purely alphanumeric though so don’t think that was it. Resetting the fog password has resolved my issue however so happy to have this one marked as solved.

regards Kiweegie.

[Sebastian Roth]

@Wayne-Workman Should have reloaded the page… Good to know that you seam to have verified that this is fixed. Probably it was still wrong in .fogsettings for @Kiweegie?!

[Tom Elliott]

@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?