Fog Service does not start due to time-out

[Tom Elliott]

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.

[Frank]

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.

[Tom Elliott]

@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: http://172.16.1.43/fog/service/jobs.php?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
 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”?

[Frank]

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

[Joe Schmitt]

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

[Frank]

@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.

[Frank]

@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]

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

[Wayne Workman]

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

[Frank]

@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.

[Frank]

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

[Tom Elliott]

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

[Frank]

@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.

[Frank]

@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]

Just wondering if this is still a problem with newer versions of the client?

[Frank]

@Tom-Elliott I will try to test it with the old machine again.

[Sebastian Roth]

@Frank Is this still an issue with the newer client?