FOG Service Client not updating on existing image


  • Testers

    When imaging a new machine after updating to Trunk 4555 none of my clients can update the FOG Client. (Using Client 0.9.4 before update.) If I uninstall and reinstall the new client everything works as intended. So here is what I am seeing after an image:

    Client Images without issue.
    Once Sysrep Completes the services are turned on for FOG Client
    The service will constantly restart on its own
    Error from FOG client Log is the following for the Client Updater:

    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     11/19/2015 11:44 AM Client-Info Version: 0.9.5
     11/19/2015 11:44 AM ClientUpdater Running...
     11/19/2015 11:44 AM Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=34:64:A9:29:2F:7D||00:00:00:00:00:00:00:E0&newService=1
     11/19/2015 11:44 AM Middleware::Communication Response: Success
     11/19/2015 11:44 AM Middleware::Communication URL: http://fog-server/fog/service/getversion.php?client&newService=1
     11/19/2015 11:44 AM Middleware::Communication URL: http://fog-server/fog/client/FOGService.msi
     11/19/2015 11:44 AM ClientUpdater ERROR: Unable to prepare update helpers
     11/19/2015 11:44 AM ClientUpdater ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\FOGUpdateHelper.exe' because it is being used by another process.
    ------------------------------------------------------------------------------
    
     11/19/2015 11:44 AM Bus {
      "channel": "Update",
      "data": "{\r\n  \"action\": \"start\"\r\n}"
    }
     11/19/2015 11:44 AM Bus Emmiting message on channel: Update
     11/19/2015 11:44 AM Service-Update Spawning update helper
     11/19/2015 11:44 AM Bus Registering ParseBus in channel Power
     11/19/2015 11:44 AM Update Helper Shutting down service...
     11/19/2015 11:44 AM Service Stop requested
     11/19/2015 11:44 AM Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"unload\"\r\n}"
    }
     11/19/2015 11:44 AM Bus Emmiting message on channel: Status
     11/19/2015 11:44 AM Update Helper Killing remaining FOG processes...
     11/19/2015 11:44 AM Update Helper Applying MSI...
     11/19/2015 11:44 AM Update Helper --> msiexec /i "C:\Program Files (x86)\FOG\tmp\FOGService.msi" /quiet USETRAY="" HTTPS="0" WEBADDRESS="fog-server" WEBROOT="/fog" ROOTLOG="1"
     11/19/2015 11:44 AM Data::RSA CA cert found
     11/19/2015 11:44 AM Update Helper Starting service...
     11/19/2015 11:45 AM Bus Became bus server
     11/19/2015 11:45 AM Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     11/19/2015 11:45 AM Bus Emmiting message on channel: Status```

  • Senior Developer

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


  • Testers

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


  • Moderator

    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]


  • Testers

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



  • 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.


  • Testers

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




  • Testers

    /puts rope away. What lynch mob?



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


  • Senior Developer

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



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


  • Testers

    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.


  • Testers

    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.

    0_1447953676432_upload-ed4de60b-a0e1-4a3d-8af3-abbfe5f9eb66

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


  • Testers

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



  • Then we need @Jbob 's help on this.


  • Testers

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



  • I’m asking if you rebuilt your fog server from scratch since this image was captured.


  • Testers

    @Wayne-Workman Not sure what your asking. If I updated to latest yes. I am fully updated. I saw a commit with a new client was put in. I think it is version 0.9.7 not so I am 2 version behind at the time of imaging



  • new fog server build?


 

563
Online

5.4k
Users

12.6k
Topics

118.8k
Posts