Fog Client service stops responding



  • Server
    • FOG Version: 1.3.2 (689680) SVN: 6059
    • OS: Ubuntu 16.04.1 LTS
    Client
    • Service Version: 0.11.8
    • OS: Ubuntu 16.04.2 LTS
    • Mono Version: 4.2.1 (Debian 4.2.1.102+dfsg2-7ubuntu4)
    Description

    In our environment we have successfully installed the SmartInstaller.exe using mono and have successfully gathered images and deployed images in Ubuntu. However, when the system sits idle for a while, the service enters a failed state. After this happens, you can no longer successfully run the service without a reboot. The only way to restore connectivity to the FOG server from the client host is to reboot the OS and have the service start at boot.

    Below are attached log files from the client host.

    (mod edit to embed logs)
    0_1490980571103_fog.log
    0_1490980602389_syslog.log

    Mar 31 10:09:51 Pascua-02 systemd[1]: Stopped FOGService.
    Mar 31 10:09:51 Pascua-02 systemd[1]: FOGService.service: Unit entered failed state.
    Mar 31 10:09:51 Pascua-02 systemd[1]: FOGService.service: Failed with result 'timeout'.
    Mar 31 10:12:01 Pascua-02 systemd[1]: Configuration file /lib/systemd/system/FOGService.service is marked executable. Please remove executable permission bits. Proceeding anyway.
    Mar 31 10:12:01 Pascua-02 systemd[1]: Starting FOGService...
    Mar 31 10:12:01 Pascua-02 control.sh[15378]: cat: /opt/fog-service/service.lock: No such file or directory
    Mar 31 10:12:01 Pascua-02 control.sh[15378]: starting fog-service
    Mar 31 10:12:01 Pascua-02 control.sh[15378]: fog-service started
    Mar 31 10:12:01 Pascua-02 systemd[1]: Started FOGService.
    Mar 31 10:12:02 Pascua-02 mono: /opt/fog-service/FOGService.exe: Service  started
    Mar 31 10:12:02 Pascua-02 systemd[1]: Started Session c3 of user root.
    root@Pascua-02:/opt/fog-service#
    
    ################### Service Stopped Manually
    
     3/31/2017 10:08 AM Controller Stop
     3/31/2017 10:08 AM Service Stop requested
     3/31/2017 10:08 AM Bus {
      "self": true,
      "channel": "Status",
      "data": "{\n  \"action\": \"unload\"\n}"
    }
     3/31/2017 10:08 AM Bus Emmiting message on channel: Status
     3/31/2017 10:12 AM Main Overriding exception handling
     3/31/2017 10:12 AM Main Bootstrapping Zazzles
     3/31/2017 10:12 AM Controller Initialize
     3/31/2017 10:12 AM Zazzles Creating main thread
     3/31/2017 10:12 AM Zazzles Service construction complete
     3/31/2017 10:12 AM Controller Start
    
     3/31/2017 10:12 AM Service Starting service
     3/31/2017 10:12 AM Bus Became bus server
     3/31/2017 10:12 AM Bus {
      "self": true,
      "channel": "Status",
      "data": "{\n  \"action\": \"load\"\n}"
    }
     3/31/2017 10:12 AM Bus Emmiting message on channel: Status
     3/31/2017 10:12 AM Service Invoking early JIT compilation on needed binaries
    
    ################### Service Started Manually
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Version: 0.11.8
     3/31/2017 10:12 AM Client-Info OS:      Linux
     3/31/2017 10:12 AM Middleware::Authentication Waiting for authentication timeout to pass
     3/31/2017 10:12 AM Middleware::Communication Download: http://10.10.100.252/fog/management/other/ssl/srvpublic.crt
     3/31/2017 10:12 AM Data::RSA FOG Server CA cert found
     3/31/2017 10:12 AM Middleware::Authentication Cert OK
     3/31/2017 10:12 AM Middleware::Communication POST URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&authorize&newService
     3/31/2017 10:12 AM Middleware::Response Success
     3/31/2017 10:12 AM Middleware::Authentication Authenticated
    
    
     3/31/2017 10:12 AM Bus Registering ParseBus in channel Power
     3/31/2017 10:12 AM Middleware::Communication URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&configure&newService&json
     3/31/2017 10:12 AM Middleware::Response Success
     3/31/2017 10:12 AM Middleware::Communication Download: http://10.10.100.252/fog/management/other/fogimg.png
     3/31/2017 10:12 AM Middleware::Communication URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&mac=C4:6E:1F:04:54:27|B8:AC:6F:85:32:6D|52:54:00:71:D1:FE|52:54:00:71:D1:FE|B8:AC:6F:85:32:6D|52:54:00:9F:A0:77|52:54:00:2D:A7:62|52:54:00:2D:A7:62|FE:00:DD:C0:A1:06|FE:54:00:D0:9F:64|FE:00:DD:C0:A1:65|FE:54:00:7C:BC:97|FE:06:0A:0E:A1:00|FE:06:0A:0E:A1:01|FE:06:0A:0E:A1:02|FE:06:0A:0E:A1:03|52:54:00:51:61:E8|52:54:00:51:61:E8|FE:00:DD:C0:B1:07|FE:54:00:86:86:3E|FE:00:DD:C0:B1:66|FE:54:00:FB:99:70|FE:06:0A:0E:B1:00|FE:06:0A:0E:B1:01|FE:06:0A:0E:B1:02|FE:06:0A:0E:B1:03|FE:06:0A:0E:B1:04|FE:06:0A:0E:B1:05|52:54:00:A7:08:1F|52:54:00:A7:08:1F|FE:00:DD:C0:C1:08|FE:54:00:98:34:A7|FE:00:DD:C0:C1:67|FE:54:00:1E:E7:85|FE:06:0A:0E:C1:00|FE:06:0A:0E:C1:01|FE:06:0A:0E:C1:02|FE:06:0A:0E:C1:03|FE:06:0A:0E:C1:04|FE:06:0A:0E:C1:05|52:54:00:C2:F6:BD|52:54:00:C2:F6:BD|FE:00:DD:C0:D1:09|FE:54:00:A2:37:BE|FE:00:DD:C0:D1:68|FE:54:00:0A:C1:A7|FE:06:0A:0E:D1:00|FE:06:0A:0E:D1:01|FE:06:0A:0E:D1:02|FE:06:0A:0E:D1:03|FE:54:00:A8:95:EB|FE:54:00:53:C0:10|FE:54:00:AD:1C:98|FE:54:00:1A:59:4F|FE:54:00:43:73:5C|FE:54:00:F3:69:66|FE:06:0A:0E:A1:02|FE:06:0A:0E:A1:03|FE:06:0A:0E:D1:03|FE:06:0A:0E:D1:02|FE:06:0A:0E:A1:00|FE:06:0A:0E:A1:01|FE:06:0A:0E:B1:04|FE:06:0A:0E:B1:05|FE:06:0A:0E:C1:00|FE:06:0A:0E:C1:01|FE:06:0A:0E:B1:02|FE:06:0A:0E:C1:02&newService&json
     3/31/2017 10:12 AM Middleware::Response ERROR: Could not parse data
     3/31/2017 10:12 AM Middleware::Response ERROR: Unexpected character encountered while parsing value: T. Path '', line 0, position 0.
     3/31/2017 10:12 AM Middleware::Communication URL: http://10.10.100.252/fog/service/getversion.php?clientver&newService&json
     3/31/2017 10:12 AM Middleware::Communication URL: http://10.10.100.252/fog/service/getversion.php?newService&json
     3/31/2017 10:12 AM Service ERROR: Unable to get cycle data
     3/31/2017 10:12 AM Service ERROR: Object reference not set to an instance of an object
     3/31/2017 10:12 AM Middleware::Response Success
     3/31/2017 10:12 AM Service Initializing modules
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    ----------------------------------TaskReboot----------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    --------------------------------PowerManagement-------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    ----------------------------------UserTracker---------------------------------
    ------------------------------------------------------------------------------
     3/31/2017 10:12 AM Client-Info Client Version: 0.11.8
     3/31/2017 10:12 AM Client-Info Client OS:      Linux
     3/31/2017 10:12 AM Client-Info Server Version: 689680
     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
     3/31/2017 10:12 AM Service Sleeping for 150 seconds
    

    Thank you for your time.



  • @Joe-Schmitt said in Fog Client service stops responding:

    @tonytonyistony Nothing else is needed after hitting reset encryption button, the client should have automatically recovered from the failed state. I’ll send you a developer build of the client later today, if you could install it on a single problematic host that would be extremely helpful as it should log what’s causing the error. However, keep in mind developer builds of the client are extremely verbose and not meant for production use as it will likely log sensitive information.

    Awesome! Just let me know what needs to be done and Ill make it happen and get back to you.



  • @Joe-Schmitt said in Fog Client service stops responding:

    but I want to see if it’ll force the client to re-authenticate and fix this issue itself.

    I wanted to say this is the easiest stop gap in my opinion. I could make a cron script that detects the error, then issue some sort of restart, then I wouldn’t need user intervention to fix the issue.


  • Senior Developer

    @tonytonyistony Nothing else is needed after hitting reset encryption button, the client should have automatically recovered from the failed state. I’ll send you a developer build of the client later today, if you could install it on a single problematic host that would be extremely helpful as it should log what’s causing the error. However, keep in mind developer builds of the client are extremely verbose and not meant for production use as it will likely log sensitive information.



  • @Joe-Schmitt said in Fog Client service stops responding:

    @tonytonyistony while the client is in this bad state, (continually logging Could not parse data), could you try going to the host in the web portal and clicking Reset Encryption Data? Its not needed, but I want to see if it’ll force the client to re-authenticate and fix this issue itself.

    This is the log output after hitting the “Reset Encryption Data” button in the server.
    I did not do anything else but cat the “fog.log” file. Is there anything else you wanted me to do on the client side after hitting the reset button on the server?

    #Fog.log
    ------------------------------------------------------------------------------
    ----------------------------------UserTracker---------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 9:58 AM Client-Info Client Version: 0.11.8
     4/5/2017 9:58 AM Client-Info Client OS:      Linux
     4/5/2017 9:58 AM Client-Info Server Version: 689680
     4/5/2017 9:58 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 9:58 AM Middleware::Response ERROR: Object reference not set to an instance of an object
     4/5/2017 9:58 AM Service Sleeping for 125 seconds
     4/5/2017 10:01 AM Middleware::Communication URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&configure&newService&json
     4/5/2017 10:01 AM Middleware::Response Success
     4/5/2017 10:01 AM Middleware::Communication Download: http://10.10.100.252/fog/management/other/fogimg.png
     4/5/2017 10:01 AM Middleware::Communication URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&mac=C4:6E:1F:04:54:27|B8:AC:6F:85:32:6D|52:54:00:71:D1:FE|52:54:00:71:D1:FE|B8:AC:6F:85:32:6D|52:54:00:9F:A0:77|52:54:00:2D:A7:62|52:54:00:2D:A7:62|FE:00:DD:C0:A1:06|FE:54:00:D0:9F:64|FE:00:DD:C0:A1:65|FE:54:00:7C:BC:97|FE:06:0A:0E:A1:00|FE:06:0A:0E:A1:01|FE:06:0A:0E:A1:02|FE:06:0A:0E:A1:03|52:54:00:51:61:E8|52:54:00:51:61:E8|FE:00:DD:C0:B1:07|FE:54:00:86:86:3E|FE:00:DD:C0:B1:66|FE:54:00:FB:99:70|FE:06:0A:0E:B1:00|FE:06:0A:0E:B1:01|FE:06:0A:0E:B1:02|FE:06:0A:0E:B1:03|FE:06:0A:0E:B1:04|FE:06:0A:0E:B1:05|52:54:00:A7:08:1F|52:54:00:A7:08:1F|FE:00:DD:C0:C1:08|FE:54:00:98:34:A7|FE:00:DD:C0:C1:67|FE:54:00:1E:E7:85|FE:06:0A:0E:C1:00|FE:06:0A:0E:C1:01|FE:06:0A:0E:C1:02|FE:06:0A:0E:C1:03|FE:06:0A:0E:C1:04|FE:06:0A:0E:C1:05|52:54:00:C2:F6:BD|52:54:00:C2:F6:BD|FE:00:DD:C0:D1:09|FE:54:00:A2:37:BE|FE:00:DD:C0:D1:68|FE:54:00:0A:C1:A7|FE:06:0A:0E:D1:00|FE:06:0A:0E:D1:01|FE:06:0A:0E:D1:02|FE:06:0A:0E:D1:03|FE:54:00:A8:95:EB|FE:54:00:53:C0:10|FE:54:00:AD:1C:98|FE:54:00:1A:59:4F|FE:54:00:43:73:5C|FE:54:00:F3:69:66|FE:06:0A:0E:A1:02|FE:06:0A:0E:A1:03|FE:06:0A:0E:D1:03|FE:06:0A:0E:D1:02|FE:06:0A:0E:A1:00|FE:06:0A:0E:A1:01|FE:06:0A:0E:B1:04|FE:06:0A:0E:B1:05|FE:06:0A:0E:C1:00|FE:06:0A:0E:C1:01|FE:06:0A:0E:B1:02|FE:06:0A:0E:C1:02&newService&json
     4/5/2017 10:01 AM Middleware::Response ERROR: Could not parse data
     4/5/2017 10:01 AM Middleware::Response ERROR: Unexpected character encountered while parsing value: T. Path '', line 0, position 0.
     4/5/2017 10:01 AM Middleware::Communication URL: http://10.10.100.252/fog/service/getversion.php?clientver&newService&json
     4/5/2017 10:01 AM Middleware::Communication URL: http://10.10.100.252/fog/service/getversion.php?newService&json
     4/5/2017 10:01 AM Service ERROR: Unable to get cycle data
     4/5/2017 10:01 AM Service ERROR: Object reference not set to an instance of an object
     4/5/2017 10:01 AM Middleware::Response Success
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    ----------------------------------TaskReboot----------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    --------------------------------PowerManagement-------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    
    ------------------------------------------------------------------------------
    ----------------------------------UserTracker---------------------------------
    ------------------------------------------------------------------------------
     4/5/2017 10:01 AM Client-Info Client Version: 0.11.8
     4/5/2017 10:01 AM Client-Info Client OS:      Linux
     4/5/2017 10:01 AM Client-Info Server Version: 689680
     4/5/2017 10:01 AM Middleware::Response ERROR: Unable to get subsection
     4/5/2017 10:01 AM Middleware::Response ERROR: Object reference not set to an instance of an object
     4/5/2017 10:01 AM Service Sleeping for 87 seconds
    
    #syslog
    #No new entries
    

  • Senior Developer

    @tonytonyistony while the client is in this bad state, (continually logging Could not parse data), could you try going to the host in the web portal and clicking Reset Encryption Data? Its not needed, but I want to see if it’ll force the client to re-authenticate and fix this issue itself.



  • @Joe-Schmitt

    does the client continue to log, or does the process itself just stop.
    

    It continues to log, repeating what I attached into the forum post until I reboot.


  • Senior Developer

    @tonytonyistony Yeah it basically becomes unresponsive to the Server., does the client continue to log, or does the process itself just stop. I ask because if it crashes completely (the process dies), then its likely an OS-specific issue. Whereas if the client continues to log but is unresponsive to the server, then its possible that an irrecoverable bad state does exist in the client’s code, and that needs to be patched.

    As for these messages:

    Mar 31 10:09:51 Pascua-02 systemd[1]: FOGService.service: Unit entered failed state.
    Mar 31 10:09:51 Pascua-02 systemd[1]: FOGService.service: Failed with result 'timeout'.
    

    they are likely due to how we wrap the client on Linux. Keep in mind we are actually making a Windows oriented service run under every common *nix based daemon / service system. It’s likely that Ubuntu’s daemon system does not like how our service wrappers handle things, but it definitely won’t harm anything or cause any failed code. We could probably fix the client’s service wrapper for Ubuntu, but we’re a tad stretched for developers right now and its a fairly low priority ticket.



  • Joe

    Thank you for the accolades. Im in tech support myself, and I know the feeling of spending more time collecting data, than actually troubleshooting.

    I just wanted to respond that I got your message, and once I get in to the office on Monday I can have a much more detailed dialog. I could even grant remote access to the device.

    But to briefly answer your question…

    "Does the client stop entirely,?"
    

    Yeah it basically becomes unresponsive to the Server. We issue a reboot/re-image from the server to the client and it does nothing. Once I go back and check the logs on the client all I see is what I attached above. Once I reboot and check the logs, they look perfect and the server can communicate.

    With my experience using Linux, this part concerns me. However, it doesn’t explain that it works after boot.

    3/31/2017 10:12 AM Middleware::Communication URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&mac=C4:6E:1F:04:54:27|B8:AC:6F:85:32:6D|52:54:00:71:D1:FE|52:54:00:71:D1:FE|B8:AC:6F:85:32:6D|52:54:00:9F:A0:77|52:54:00:2D:A7:62|52:54:00:2D:A7:62|FE:00:DD:C0:A1:06|FE:54:00:D0:9F:64|FE:00:DD:C0:A1:65|FE:54:00:7C:BC:97|FE:06:0A:0E:A1:00|FE:06:0A:0E:A1:01|FE:06:0A:0E:A1:02|FE:06:0A:0E:A1:03|52:54:00:51:61:E8|52:54:00:51:61:E8|FE:00:DD:C0:B1:07|FE:54:00:86:86:3E|FE:00:DD:C0:B1:66|FE:54:00:FB:99:70|FE:06:0A:0E:B1:00|FE:06:0A:0E:B1:01|FE:06:0A:0E:B1:02|FE:06:0A:0E:B1:03|FE:06:0A:0E:B1:04|FE:06:0A:0E:B1:05|52:54:00:A7:08:1F|52:54:00:A7:08:1F|FE:00:DD:C0:C1:08|FE:54:00:98:34:A7|FE:00:DD:C0:C1:67|FE:54:00:1E:E7:85|FE:06:0A:0E:C1:00|FE:06:0A:0E:C1:01|FE:06:0A:0E:C1:02|FE:06:0A:0E:C1:03|FE:06:0A:0E:C1:04|FE:06:0A:0E:C1:05|52:54:00:C2:F6:BD|52:54:00:C2:F6:BD|FE:00:DD:C0:D1:09|FE:54:00:A2:37:BE|FE:00:DD:C0:D1:68|FE:54:00:0A:C1:A7|FE:06:0A:0E:D1:00|FE:06:0A:0E:D1:01|FE:06:0A:0E:D1:02|FE:06:0A:0E:D1:03|FE:54:00:A8:95:EB|FE:54:00:53:C0:10|FE:54:00:AD:1C:98|FE:54:00:1A:59:4F|FE:54:00:43:73:5C|FE:54:00:F3:69:66|FE:06:0A:0E:A1:02|FE:06:0A:0E:A1:03|FE:06:0A:0E:D1:03|FE:06:0A:0E:D1:02|FE:06:0A:0E:A1:00|FE:06:0A:0E:A1:01|FE:06:0A:0E:B1:04|FE:06:0A:0E:B1:05|FE:06:0A:0E:C1:00|FE:06:0A:0E:C1:01|FE:06:0A:0E:B1:02|FE:06:0A:0E:C1:02&newService&json
    3/31/2017 10:12 AM Middleware::Response ERROR: Could not parse data
    3/31/2017 10:12 AM Middleware::Response ERROR: Unexpected character encountered while parsing value: T. Path '', line 0, position 0.
    

    I wonder if some code was deprecated when Ubuntu 16.04.1 updated to .2


  • Senior Developer

    @tonytonyistony said in Fog Client service stops responding:

    can no longer successfully run the service without a reboot. The only way to restore connectivity to the FOG server from the client host is to reboot the OS and have the service start at boot.

    First off thank you for gathering all the information ahead of time, it definitely helps us out.
    Does the client stop entirely, or are the logs essentially all:

     3/31/2017 10:12 AM Middleware::Response ERROR: Unable to get subsection
     3/31/2017 10:12 AM Middleware::Response ERROR: Object reference not set to an instance of an object
    

Log in to reply
 

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