Client 0.11.5 - Sorta crashed under large printer deployment


  • Moderator

    We have about 78 printers in our big fog setup, I assigned them all to my computer so I can troubleshoot the non-working ones. 44 of those deployed properly, the others have configuration issues presumably.

    I then removed the working printers from my host in FOG, and restarted the fog service, and it gave this in the log.

    A couple service restarts later and it seems to be removing the un-assigned printers 1 by 1.

    Just though I’d give @Joe-Schmitt a heads up.

    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     8/12/2016 11:19 AM Client-Info Client Version: 0.11.5
     8/12/2016 11:19 AM Client-Info Client OS:      Windows
     8/12/2016 11:19 AM Client-Info Server Version: 1.3.0-RC-8
     8/12/2016 11:19 AM Middleware::Response Success
     8/12/2016 11:19 AM PrinterManager Getting installed printers
     8/12/2016 11:20 AM Service ERROR: Unable to run module
     8/12/2016 11:20 AM Service ERROR: Thread was being aborted.
     8/12/2016 11:20 AM Controller Stop
     8/12/2016 11:20 AM Service Stop requested
     8/12/2016 11:20 AM Bus {
      "self": true,
      "channel": "Status",
      "data": "{\r\n  \"action\": \"unload\"\r\n}"
    }
     8/12/2016 11:20 AM Bus Emmiting message on channel: Status
     8/12/2016 11:20 AM Main Overriding exception handling
     8/12/2016 11:20 AM Main Bootstrapping Zazzles
     8/12/2016 11:20 AM Controller Initialize
     8/12/2016 11:20 AM Zazzles Creating main thread
     8/12/2016 11:20 AM Zazzles Service construction complete
     8/12/2016 11:20 AM Controller Start
    
     8/12/2016 11:20 AM Service Starting service
     8/12/2016 11:20 AM Bus Became bus server
     8/12/2016 11:20 AM Bus {
      "self": true,
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     8/12/2016 11:20 AM Bus Emmiting message on channel: Status
     8/12/2016 11:20 AM Service Invoking early JIT compilation on needed binaries
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     8/12/2016 11:20 AM Client-Info Version: 0.11.5
     8/12/2016 11:20 AM Client-Info OS:      Windows
     8/12/2016 11:20 AM Middleware::Authentication Waiting for authentication timeout to pass
     8/12/2016 11:20 AM Middleware::Communication Download: http://10.51.1.53/fog/management/other/ssl/srvpublic.crt
     8/12/2016 11:20 AM Data::RSA FOG Server CA cert found
     8/12/2016 11:20 AM Middleware::Authentication Cert OK
     8/12/2016 11:20 AM Middleware::Communication POST URL: http://10.51.1.53/fog/management/index.php?sub=requestClientInfo&authorize&newService
     8/12/2016 11:20 AM Middleware::Response Success
     8/12/2016 11:20 AM Middleware::Authentication Authenticated
    
    
     8/12/2016 11:20 AM Bus Registering ParseBus in channel Power
     8/12/2016 11:20 AM Middleware::Communication URL: http://10.51.1.53/fog/management/index.php?sub=requestClientInfo&mac=90:B1:1C:98:03:8C||00:00:00:00:00:00:00:E0&newService&json
     8/12/2016 11:20 AM Middleware::Response Success
     8/12/2016 11:20 AM Middleware::Communication URL: http://10.51.1.53/fog/service/getversion.php?clientver&newService&json
     8/12/2016 11:20 AM Middleware::Communication URL: http://10.51.1.53/fog/service/getversion.php?newService&json
    
     8/12/2016 11:20 AM Service Creating user agent cache
     8/12/2016 11:20 AM Middleware::Response Invalid time
     8/12/2016 11:20 AM Middleware::Response Success
     8/12/2016 11:20 AM Middleware::Response Module is disabled globally on the FOG server
     8/12/2016 11:20 AM Service Initializing modules
    

Log in to reply
 

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