Fog Service does not start due to time-out

  • Server
    • FOG Version: 1.3.5-RC14
    • OS: Ubuntu 14.05
    • Service Version: 0.11.10
    • OS: Windows 10

    Sometimes Fog Service does not start, and in Events Viewer appears an error with code 7009 about time-out (30000 ms)while connecting with FOGService.
    I don’t know if it is actually a bug because perhaps is related to busy slow system.
    It could be useful if other people reports the same issue.

  • @Tom-Elliott Hi again.
    I’ve tested another (smaller) image and all the tests (capture, deploy, fog agent boot start) went ok. So I think it’s strongly related to client computer capabilities. I’m testing with an old HP dc5700 Core2 Duo 2 GB RAM. I guess there won’t be issues on a little newer computer.

  • @Tom-Elliott Sorry for the delay. Nom client does not have any AV client but windows defender, that I have taken off the scheduler. I’m wondering if it’s something related to any driver. I’m going to apply latest patches and see what happens.

  • Senior Developer

    @Frank Do you have an AV client on the system? (I’m just asking because I, too, want to figure out what’s happening.)

  • @Joe-Schmitt After a second boot, agent started. I guess it is a difficult issue to track.

  • @Joe-Schmitt The image is not syspreped. I have optimized disk, and after that agent have started again on boot. But after capturing image once again, problem have risen again, and agent does not start on boot.

  • Moderator

    @Frank Please answer @Joe-Schmitt’s questions below - he’s the guy that wrote the fog client.

  • Senior Developer

    Is it possible an Antivirus program is preventing startup of the client? (Just going on a wild guess here.)

  • @Tom-Elliott I’ve optimized disk and agent have started at boot. So it seems strongly related to system performance. I’m goig to make another capture just to check.

  • @Tom-Elliott There is no task currently. The task indicated in log file was a capture, which finished ok. After that, fog agent has not started at boot time.

  • Senior Developer

    Is it only not starting after imaging? If so is your image syspreped? Did you follow the sysprep guide with client in the wiki?

  • @Tom-Elliott Yes, it was an image capture, and it went ok, but agent has not started at boot time since that.

  • Senior Developer

    @Frank Is the host in some tasking currently scheduled on the FOG Server?

    I don’t think this would have anything to do with it, but the last message in the log appears to indicate there was a tasking given to it.

     15/03/2017 8:40 Service Sleeping for 171 seconds
     15/03/2017 8:41 Middleware::Communication URL:||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
     15/03/2017 8:41 Middleware::Response Success
     15/03/2017 8:41 Power Creating shutdown request
     15/03/2017 8:41 Power Parameters: /r /c "TaskReboot" /t 0
     15/03/2017 8:41 Bus {
      "self": true,
      "channel": "Power",
      "data": "{\r\n  \"action\": \"shuttingdown\"\r\n}"
     15/03/2017 8:41 Bus Emmiting message on channel: Power

    Is this still the case, or did the system properly restart, and this is when you noticed the issue with the “startup timeout”?

  • 0_1489580840910_fog.log
    Here goes fog.log file. Now its 13:27 here and you will see last time log is about 8:40. I’ve restarted the computer several times since and fog agent has not started due same timeout error.

  • Senior Developer

    I’ve heard of this happening on a few other locations, and we’ll probably ask for the client log located typically at c:\fog.log.

    I don’t know if we will have a solution to what’s described here, but at least we might be able to provide more information.

Log in to reply

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