fog agent 0.11.9 response module disabled



  • Server
    • FOG Version: 1.3.5-RC-12
    • OS: ubuntu 14.04
    Client
    • Service Version: 0.11.9
    • OS: windows 10
    Description

    We upgraded 10 fog 1.3.4 from a previous version which agent version was 0.9.x
    We noticed agent didn’t upgrade so we moved to 1.3.5-RC15 as we read that was solved.
    Now agent is upgraded to 0.11.9 but after reseting encription data, agent seems to be stalled in a loop. Log file repeats these lines:

    --------------------------------Authentication--------------------------------

    10/03/2017 9:11 Client-Info Version: 0.11.9
    10/03/2017 9:11 Client-Info OS: Windows
    10/03/2017 9:11 Middleware::Authentication Waiting for authentication timeout to pass
    10/03/2017 9:11 Middleware::Communication Download: http://172.16.1.43/fog/management/other/ssl/srvpublic.crt
    10/03/2017 9:11 Data::RSA FOG Server CA cert found
    10/03/2017 9:11 Middleware::Authentication Cert OK
    10/03/2017 9:11 Middleware::Communication POST URL: http://172.16.1.43/fog/management/index.php?sub=requestClientInfo&authorize&newService
    10/03/2017 9:11 Middleware::Response Success
    10/03/2017 9:11 Middleware::Authentication Authenticated

    10/03/2017 9:11 Bus Registering ParseBus in channel Power
    10/03/2017 9:11 Middleware::Communication URL: http://172.16.1.43/fog/management/index.php?sub=requestClientInfo&configure&newService&json
    10/03/2017 9:11 Middleware::Response Success
    10/03/2017 9:11 Middleware::Communication URL: http://172.16.1.43/fog/management/index.php?sub=requestClientInfo&mac=00:0E:0C:5E:17:AE||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
    10/03/2017 9:11 Middleware::Response Success
    10/03/2017 9:11 Middleware::Communication URL: http://172.16.1.43/fog/service/getversion.php?clientver&newService&json
    10/03/2017 9:11 Middleware::Communication URL: http://172.16.1.43/fog/service/getversion.php?newService&json

    10/03/2017 9:11 Service Creating user agent cache
    10/03/2017 9:11 Middleware::Response Module is disabled on the host
    10/03/2017 9:11 Middleware::Response Module is disabled globally on the FOG server
    10/03/2017 9:11 Middleware::Response Success
    10/03/2017 9:11 Service Initializing modules


    ---------------------------------ClientUpdater--------------------------------

    10/03/2017 9:11 Client-Info Client Version: 0.11.9
    10/03/2017 9:11 Client-Info Client OS: Windows
    10/03/2017 9:11 Client-Info Server Version: 1.3.5-RC-12
    10/03/2017 9:11 Middleware::Response Success
    10/03/2017 9:11 Middleware::Communication Download: http://172.16.1.43/fog/client/SmartInstaller.exe
    10/03/2017 9:11 Data::RSA FOG Project cert found
    10/03/2017 9:11 ClientUpdater Update file is authentic

    10/03/2017 9:11 Bus {
    “self”: true,
    “channel”: “Update”,
    “data”: “{\r\n “action”: “start”\r\n}”
    }
    10/03/2017 9:11 Bus Emmiting message on channel: Update
    10/03/2017 9:11 Service-Update Spawning update helper
    10/03/2017 9:11 UpdaterHelper Shutting down service…
    10/03/2017 9:11 UpdaterHelper Killing remaining processes…
    10/03/2017 9:11 UpdaterHelper Applying update…
    10/03/2017 9:12 UpdaterHelper Starting service…
    10/03/2017 9:12 Main Overriding exception handling
    10/03/2017 9:12 Main Bootstrapping Zazzles
    10/03/2017 9:12 Controller Initialize
    10/03/2017 9:12 Zazzles Creating main thread
    10/03/2017 9:12 Zazzles Service construction complete
    10/03/2017 9:12 Controller Start

    10/03/2017 9:12 Service Starting service
    10/03/2017 9:12 Bus Became bus server
    10/03/2017 9:12 Bus {
    “self”: true,
    “channel”: “Status”,
    “data”: “{\r\n “action”: “load”\r\n}”
    }
    10/03/2017 9:12 Bus Emmiting message on channel: Status
    10/03/2017 9:12 Service Invoking early JIT compilation on needed binaries

    We dont’t know how to go on.



  • Sorry! It’s ok!
    Agent was stopped for some reason. Now log seems ok.
    Thanks a lot!



  • Thanks @Tom-Elliott
    I have upgrade it, and rebooted client computer, and still the same log.
    Something more to do?


  • Senior Developer

    RC 13 has been pushed to address this issue.


 

348
Online

41.8k
Users

12.3k
Topics

116.0k
Posts