Client Updater Loop



  • Hello,
    I think there is something pretty wrong there, no ?
    0_1450429828621_Sans titre.png

    It keeps downloading client from server in loop. :scream:
    Can I blame someone for making my network a battlefield ? :skull:
    I had to stop apache2 to end this but that doesn’t give me solution to fix the upgrade on every computer of my network unless going on them to run the 0.9.9 msi manually or remove the 0.9.7.
    I even have this when I see 0.9.7 and 0.9.9 on add/remove software panel…

    Here are the result for having the 2 version installed :

    C:\Windows\system32>wmic product where "name like 'FOG Service'" get Version
    Version
    0.9.9
    0.9.7
    

    And logs of this computer :

     18/12/2015 10:47 Data::RSA FOG Server CA cert found
     18/12/2015 10:47 Update Helper Starting service...
     18/12/2015 10:47 Bus Became bus server
     18/12/2015 10:47 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     18/12/2015 10:47 Bus Emmiting message on channel: Status
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     18/12/2015 10:47 Client-Info Version: 0.9.7
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
     18/12/2015 10:47 Data::RSA FOG Server CA cert found
     18/12/2015 10:47 Middleware::Authentication Cert OK
     18/12/2015 10:47 Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
     18/12/2015 10:47 Middleware::Communication Response: Success
     18/12/2015 10:47 Middleware::Authentication Authenticated
    
     18/12/2015 10:47 Bus Registering ParseBus in channel Power
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     18/12/2015 10:47 Client-Info Version: 0.9.7
     18/12/2015 10:47 ClientUpdater Running...
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=78:E7:D1:D2:F3:5A||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     18/12/2015 10:47 Middleware::Communication Response: Success
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/service/getversion.php?client&newService=1
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/client/FOGService.msi
     18/12/2015 10:47 Data::RSA FOG Project cert found
     18/12/2015 10:47 ClientUpdater Update file is authentic
    ------------------------------------------------------------------------------
    
     18/12/2015 10:47 Bus {
      "channel": "Update",
      "data": "{\r\n  \"action\": \"start\"\r\n}"
    }
     18/12/2015 10:47 Bus Emmiting message on channel: Update
     18/12/2015 10:47 Service-Update Spawning update helper
     18/12/2015 10:47 Bus Registering ParseBus in channel Power
     18/12/2015 10:47 Update Helper Shutting down service...
     18/12/2015 10:47 Service Stop requested
     18/12/2015 10:47 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"unload\"\r\n}"
    }
     18/12/2015 10:47 Bus Emmiting message on channel: Status
     18/12/2015 10:47 Update Helper Killing remaining FOG processes...
     18/12/2015 10:47 Update Helper Applying MSI...
     18/12/2015 10:47 Update Helper --> msiexec /i "C:\Program Files\FOG\tmp\FOGService.msi" /quiet USETRAY="1" HTTPS="0" WEBADDRESS="fog-server" WEBROOT="/fog" ROOTLOG="1"
     18/12/2015 10:47 Data::RSA FOG Server CA cert found
     18/12/2015 10:47 Update Helper Starting service...
     18/12/2015 10:47 Bus Became bus server
     18/12/2015 10:47 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     18/12/2015 10:47 Bus Emmiting message on channel: Status
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     18/12/2015 10:47 Client-Info Version: 0.9.7
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
     18/12/2015 10:47 Data::RSA FOG Server CA cert found
     18/12/2015 10:47 Middleware::Authentication Cert OK
     18/12/2015 10:47 Middleware::Communication POST URL: http://fog-server/fog/management/index.php?sub=authorize
     18/12/2015 10:47 Middleware::Communication Response: Success
     18/12/2015 10:47 Middleware::Authentication Authenticated
    
     18/12/2015 10:47 Bus Registering ParseBus in channel Power
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     18/12/2015 10:47 Client-Info Version: 0.9.7
     18/12/2015 10:47 ClientUpdater Running...
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=78:E7:D1:D2:F3:5A||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     18/12/2015 10:47 Middleware::Communication Response: Success
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/service/getversion.php?client&newService=1
     18/12/2015 10:47 Middleware::Communication URL: http://fog-server/fog/client/FOGService.msi
     18/12/2015 10:47 Data::RSA FOG Project cert found
     18/12/2015 10:47 ClientUpdater Update file is authentic
    ------------------------------------------------------------------------------
    
     18/12/2015 10:47 Bus {
      "channel": "Update",
      "data": "{\r\n  \"action\": \"start\"\r\n}"
    }
     18/12/2015 10:47 Bus Emmiting message on channel: Update
     18/12/2015 10:47 Service-Update Spawning update helper
     18/12/2015 10:48 Bus Registering ParseBus in channel Power
     18/12/2015 10:48 Update Helper Shutting down service...
     18/12/2015 10:48 Service Stop requested
     18/12/2015 10:48 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"unload\"\r\n}"
    }
     18/12/2015 10:48 Bus Emmiting message on channel: Status
     18/12/2015 10:48 Update Helper Killing remaining FOG processes...
     18/12/2015 10:48 Update Helper Applying MSI...
     18/12/2015 10:48 Update Helper --> msiexec /i "C:\Program Files\FOG\tmp\FOGService.msi" /quiet USETRAY="1" HTTPS="0" WEBADDRESS="fog-server" WEBROOT="/fog" ROOTLOG="1"
     18/12/2015 10:48 Data::RSA FOG Server CA cert found
     18/12/2015 10:48 Update Helper Starting service...
     18/12/2015 10:48 Bus Became bus server
     18/12/2015 10:48 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     18/12/2015 10:48 Bus Emmiting message on channel: Status
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     18/12/2015 10:48 Client-Info Version: 0.9.7
     18/12/2015 10:48 Middleware::Communication URL: http://fog-server/fog/management/other/ssl/srvpublic.crt
    

  • Senior Developer

    I’m solving this thread as the issue involved was not caused by fog at all.



  • @Jbob Thank you for your help too. :-)


  • Senior Developer

    @jmeyer , the client was meant to be upgraded in a linear fashion, but with GPO mucking things up that linear upgrade path is now broken. The best approach is what Tom suggested. Use GPO to remove ALL CLIENTS completely. v0.9.7. v0.9.9, everything needs to be wiped. Then use GPO once to deploy v0.9.9, once deployed remove the GPO policy, or be very careful when you create the policy so that its a one-time only deal.



  • @Tom-Elliott That’s what i was thinking. Thank you.


  • Senior Developer

    A snapin should NOT be used to Upgrade the client. THe snapin should ONLY be used to remove the clients.

    Use a GPO (or maybe a startup script) to only install a new client on the systems IF there is no client installed on them already.



  • @Wayne-Workman It’s set on computer startup. I can’t restart all my network like this… I fixed only a few manually.



  • @Tom-Elliott
    I live in loops… lol

    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     18/12/2015 16:25 Client-Info Version: 0.9.9
     18/12/2015 16:25 SnapinClient Running...
     18/12/2015 16:25 Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=1C:C1:DE:51:16:C1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     18/12/2015 16:25 Middleware::Communication Response: Success
     18/12/2015 16:25 Middleware::Communication URL: http://fog-server/fog/service/snapins.checkin.php?mac=1C:C1:DE:51:16:C1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     18/12/2015 16:25 Middleware::Communication Response: Success
     18/12/2015 16:25 SnapinClient Snapin Found:
     18/12/2015 16:25 SnapinClient     ID: 201
     18/12/2015 16:25 SnapinClient     RunWith: 
     18/12/2015 16:25 SnapinClient     RunWithArgs: 
     18/12/2015 16:25 SnapinClient     Name: Upgrade Client FOG
     18/12/2015 16:25 SnapinClient     File: upgradefogclient.bat
     18/12/2015 16:25 SnapinClient     Created: 2015-12-18 15:21:44
     18/12/2015 16:25 SnapinClient     Args: 
     18/12/2015 16:25 SnapinClient     Reboot: 0
     18/12/2015 16:25 Middleware::Communication URL: http://fog-server/fog/service/snapins.file.php?mac=1C:C1:DE:51:16:C1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=201
     18/12/2015 16:25 Bus {
      "channel": "Notification",
      "data": "{\r\n  \"title\": \"Upgrade Client FOG\",\r\n  \"message\": \"FOG is installing Upgrade Client FOG\",\r\n  \"duration\": 10\r\n}"
    }
     18/12/2015 16:25 Bus Emmiting message on channel: Notification
     18/12/2015 16:25 SnapinClient Starting snapin...
     18/12/2015 16:25 Service Stop requested
     18/12/2015 16:25 SnapinClient ERROR: Could not start snapin
     18/12/2015 16:25 SnapinClient ERROR: Le thread a été abandonné.
     18/12/2015 16:25 Service ERROR: Le thread a été abandonné.
     18/12/2015 16:25 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"unload\"\r\n}"
    }
     18/12/2015 16:25 Bus Emmiting message on channel: Status
     18/12/2015 16:26 RegistryHandler ERROR: Could not retrieve Software\Wow6432Node\FOG\Server
     18/12/2015 16:26 RegistryHandler ERROR: Null key
     18/12/2015 16:26 RegistryHandler 32 bit registry detected
     18/12/2015 16:26 Middleware::Communication URL: http://fog-server/fog/management/other/ca.cert.der
     18/12/2015 16:26 Bus Became bus server
     18/12/2015 16:26 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     18/12/2015 16:26 Bus Emmiting message on channel: Status
    

  • Senior Developer

    @jmeyer How do you check for a newer version in a file that is the “most recent?”


  • Moderator

    @jmeyer said:

    My current script remove the 3 clients (old, 0.9.7 and 0.9.9) before installing the 0.9.9.
    But this is not great since it will do this in loop.

    If you’re removing 3.0.29, 0.97, and 0.9.9 and then installing the latest - why is the latest client trying to update over and over?



  • @Wayne-Workman If he releases a new version that remove all old version (under 0.9.9) and upgrade the last (0.9.9), won’t it solve my problem ?
    Will 0.9.7 client will download a 0.9.9+ version and clean the multiple install ?

    My current script remove the 3 clients (old, 0.9.7 and 0.9.9) before installing the 0.9.9.
    But this is not great since it will do this in loop.


  • Moderator

    @jmeyer That’s something that @Jbob would need to confirm.



  • @Tom-Elliott So a check looking for newer version was forgotten in 0.9.7 install to avoid such install ? Client shouldn’t have been installed if 0.9.9 was already installed.


  • Moderator

    @jmeyer Yeah.

    So… whatever is the latest version available on your FOG server - all new fog clients automatically update to that version.

    But your GPO was forcing a older version - so now you have a mess.

    Wipe the slate clean and start over. use msiexec to remove everything like ‘FOG Service’ and undo your group policy deployment. Let that go until there are no clients left, then use group policy to push out the latest.


  • Senior Developer

    @jmeyer Correct.

    ANd because the service was overwritten with 0.9.7, but the installed client is 0.9.9, it won’t fix it.



  • @Tom-Elliott If I understand well, i have kept deloying the 0.9.7 when 0.9.9 was already installed automatically ?


  • Senior Developer

    I’ll try to explain, as clearly as I can, what I believe has happened.

    First the GPO you setup (or whatever you setup) was set to remove the Old Client from systems and install (at that time 0.9.7).

    Old client was removed successfully, and new client was installed successfully.

    The new client (for that was setup as 0.9.7).

    You updated FOG, all the clients updated to 0.9.9.

    The GPO and/or script you had to do the remove/install then overwrote.

    0.9.7 did not exist and was then created.

    It overwrote the 0.9.9 service.

    Now the fun part begins.

    The service now believes it is 0.9.7, and the clients are constantly scanning and downloading the new client.

    Windows sees 0.9.9 is installed and nothing happens. The clients keep checking in and doing the same thing over and over and over.


  • Senior Developer

    @jmeyer you should be able to use a snapin to remove all instances of the fog client. Then add a check to the gpo that if there is no client to install the latest. This should fix the problems. Without knowing the environment and what other policies all I can give is suggestions on how I would approach the issue.


  • Senior Developer

    Disable the client updater module on all computers, that will halt the massive network traffic.



  • @Tom-Elliott That’s was more for the way to do it that I was looking for. i can’t go on 200 computer to do this manually.


Log in to reply
 

467
Online

39.4k
Users

11.1k
Topics

105.4k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.