FOG Service Client not updating on existing image

[Psycholiquid]

@Wayne-Workman No it is the same server I have always had, the image is no more than 2 weeks old.

[Wayne Workman]

Then we need @Jbob 's help on this.

[Psycholiquid]

@Wayne-Workman Yeah I figured. I am uninstalling and reinstalling and that is resolving the issue for now

[Psycholiquid]

Hmm looking at the commit I am seeing the client is supposed to be 0.9.7 but when I download the client form ym FOG server I am only getting 0.9.5.

Perhaps wrong version in trunk or I am not getting the right one from the background downloader?

[Psycholiquid]

OK this is what I have so far. The uninstall / reinstall is a crap shoot.

The new server trunk is giving me version 0.9.5. I have 0.9.5 installed in my image. So I am not even sure why it is trying to update the client unless something has changed in the code of it that is above my head.

I am uninstalling it from a freshly imaged machine and everything is fine. I download the new file from the FOG server ot make sure I am using what is on that page there and when I reinstalled it says it is version 0.9.5 which is what was in there in the first place and I get the same problem of machines not changing name and adding to domain.

However to get around this I just turn off the client updater in the service and it allows everything to work as intended.

TLDR:

Leave the Client as is for now as it is still working.
Turn off Client updater service on either the whole server or the client you have just imaged and everything will continue to flow.

[Wayne Workman]

@Jbob just informed me that this error you have is caused by the fog installer downloading the wrong version of the client during installation.

He hinted that it may be due to the roll-back that happened a day/two ago. @Tom-Elliott

[Tom Elliott]

@Wayne-Workman What roll back? I did not make a roll back to the system file which keeps track of the client version.

While I did revert some code, I did not do a “roll back” of any files.

[Wayne Workman]

@Tom-Elliott no idea, don’t shoot the messenger lol.

[Psycholiquid]

/puts rope away. What lynch mob?

[Wayne Workman]

https://forums.fogproject.org/topic/6184/svn-4393-cloud-5445-fogservice-msi-missing-on-fresh-insall

[Psycholiquid]

@Tom-Elliott said:

@Wayne-Workman What roll back? I did not make a roll back to the system file which keeps track of the client version.

While I did revert some code, I did not do a “roll back” of any files.

Perhaps the .msi wasn’t uploaded when the commit was done. Please don’t think that I have any idea what I am talking about I am just guessing. I was always under the impression that the client files were downloaded form somewhere else and that was done in the background after the server install.

[Wayne Workman]

wget https://github.com/FOGProject/fog-client/releases/download/0.9.7/FOGService.msi -O /var/www/html/fog/client/FOGService.msi
chown apache:apache /var/www/html/fog/client/FOGService.msi
chmod 644 /var/www/html/fog/client/FOGService.msi

destination path and owner:group might need altered depending on distribution.

[Psycholiquid]

@Wayne-Workman as a workaround that worked like a champ. All I had to do was drop the file in the folder using the command provided. So until repaired others should do this or a form of this.

[george1421]

I guess a question that is still not clear to me is when you ran the install.sh on the current trunk, the installer “should” download the latest client. Did that step complete as expected? Or was there an error saying that needed to manually down it?

IF your fog server sits behind a proxy server you need to update wget (what the installer uses to get the msi) with your proxy server settings.

[Edit] Well if you followed Wayne’s instructions and it worked, then something in the installer or svn trunk is broken. The wget in Wayne’s instructions should have thrown an error if there was a proxy issue [/Edit]

[Psycholiquid]

@george1421 I didn’t get any errors when I did the upgrade but he is right after a fresh install it just isn’t there.

[Tom Elliott]

Fixed in trunk in that it should be downloading the file properly and this has been confirmed on another thread.