@Sebastian-Roth

Sounds great! Like I said, let me know what you all are working on and I’ll do my best. I do have some background in programming but it’s been a bit. I am trying to pick up Python and do a little teaching here at our district.

I worked in UNIX for a couple years at one of my first computer jobs. They hired me because I liked tinkering in Linux. I’ve used Linux since the first iterations of Redhat. :-) The FOG project does draw you in. It’s a great thing. Some of us can’t afford to throw cash at it but certainly am willing to donate time.

So keep me posted! Thanks!

@Sebastian-Roth

I’d love to help out where I can. I’m not really a Windows guy. I’m more of a UNIX / Linux guy stuck in a Windows world. But I can certainly test things in my lab. I have a couple labs that get used very little that would offer a good test bed for features in the field.

Let me know what types of things you all need help with and I’ll see where my skillset works best.

@Sebastian-Roth
@Tom-Elliott

Let me know how I can help. I have a lab that gets used very infrequently that I can test things on if need be. (Time permitting…) My time begins to get more free here in about a month or two and then gets more busy again in February. I’d be more than happy to help out the project!

@Joe-Gill said in FOG service quits running:

@Tom-Elliott
@Sebastian-Roth

So I rebooted two different machines that were having this problem. The service restarted on one and not the other. Ha!

Thanks!

I checked the update settings on the machine that the service wasn’t running after the reboot… You guessed it, a Windows Update was running (installing). I’m gussing that is the caust of this entire issue.

Reboot will likely resolve it after the update install is completed. Hope this helps someone else down the road.

@Tom-Elliott
@Sebastian-Roth

So I rebooted two different machines that were having this problem. The service restarted on one and not the other. Ha!

Thanks!

@Tom-Elliott

I will try a reboot on the machine I had quit checking in yesterday and see.

@Sebastian-Roth

I just noticed something… While looking for log files again this morning… I had one machine that the service literally quit working yesterday… My event logs show events just AFTER the FOG service quit logging…

This machine is on Windows 10 1709 build 16299.15…

Guess what happened after that? Windows ran an update!

We do all of our updates from a Windows WSUS…

Hopefully this helps!!

@Sebastian-Roth

Here is the entire FOG log on one of the 8/20/19 machines. I can post it as code too if you’d like it. I just thought a log file may be simpler.

Thanks!

fog.log

@Sebastian-Roth said in FOG service quits running:

Thanks heaps for looking into it. Do I get this right, most of the machines having the issue showed (in the logs) the service stopped working on the very same day, all on 8/20/19??

Not a problem! I am happy to help out the project. The service quit on a handful of machines on 8/20/19 and some were in July.

So far all of my logs are not showing anything back when the problem occurred.

So the event logs go back to that date but there is no notice/warning/error in the event logs?

The event logs don’t go back far enough to show anything. In other words the event logs don’t start until after the service quit working (days later).

I have noticed that a commonality in the FOG logs is that this issue happens after FOG sleeps or reboots.

Do you mean PC reboot? Can you post an example log when it seems to happen on “reboot”?

I’ll go grab an entire log and post it here.

@Sebastian-Roth

Alright, I have a bit of info to share here…

I have a machine with Windows 10 1709 OS Build 16299.15 and an identical machine (sitting next to it) that has Windows 10 1703 Build 15063.0. The 1709 machine FOG service is not running. The 1703 FOG service IS running.

I checked multiple machines and none seem to have logs that go back far enough to any events that happened on the day the service quit. That said the things these all have in common (on some machines) occurred two days prior to a system update. (8/20/19) The update occurred on 8/22/19… I had a few outliers that happened mid July.

Oddly enough, I was out of the office the week (8/19/19) this event occurred. I checked with the other tech and we had no physical issues that day and the folks that were here used this very lab that day.

So far all of my logs are not showing anything back when the problem occurred. I have noticed that a commonality in the FOG logs is that this issue happens after FOG sleeps or reboots.

Let me know what else I can provide you. I have several machines in the same lab that have this issue. I had a few that after I logged into AD, the service checked in and everything seems to be working.

Cheers,

Joe