FOG services - are they supposed to start on system boot?

[Trevelyan]

I haven’t really noticed this before until I was just browsing the replicator, task scheduler and multicast logs. They seemed to have been updated fairly frequently, but then they stopped. It was then that I noticed that the respective services just weren’t running at all and had to be manually started. However, at first they fail; until I manually attempt to stop them (although they didn’t appear to be running):

Restarting FOG Computer Imaging Solution: FOGImageReplicator                 start-stop-daemon: warning: failed to kill 1154: No such process
Restarting FOG Computer Imaging Solution: FOGScheduler                       start-stop-daemon: warning: failed to kill 1230: No such process
Restarting FOG Computer Imaging Solution: FOGMulticastManager                start-stop-daemon: warning: failed to kill 1197: No such process

Now when I try to start them, they work. They’re started from init.d - so are they supposed to have been started on system boot?

Cheers

[Tom Elliott]

@Trevelyan said:

I haven’t really noticed this before until I was just browsing the replicator, task scheduler and multicast logs. They seemed to have been updated fairly frequently, but then they stopped. It was then that I noticed that the respective services just weren’t running at all and had to be manually started. However, at first they fail; until I manually attempt to stop them (although they didn’t appear to be running):

• Restarting FOG Computer Imaging Solution: FOGImageReplicator start-stop-daemon: warning: failed to kill 1154: No such process
• Restarting FOG Computer Imaging Solution: FOGScheduler start-stop-daemon: warning: failed to kill 1230: No such process
• Restarting FOG Computer Imaging Solution: FOGMulticastManager start-stop-daemon: warning: failed to kill 1197: No such process

Now when I try to start them, they work. They’re started from init.d - so are they supposed to have been started on system boot?

Cheers

This is because you’re most likely running ubuntu? Just a guess.

There’s already a ton documented about this. Basically, what’s happening, the services are all starting up as expected, including the FOG Services. At some point, however, the mysql server crashes or is restarted without properly restarting the FOG services. This causes these services to die, but they cannot be restarted because the original item it’s expecting to remove cannot be found.

[Trevelyan]

Yeah I am still looking through this - if the answer is on the forum, I’ll find it. Just the google links are broken and I’m trying to search for the same topics here

Cheers!

[Wayne Workman]

The basic answer is to delay the startup of FOG services by like 30 seconds.

[Trevelyan]

Is this issue something that a lot of people will normally encounter though? Or just for Ubuntu [14.04?] users?

What kind of effect will this have if I don’t change it, other than having no logs to view? Tasks seem to still work as does multicasting and I would assume image replication too? (Although I haven’t got that working yet).

I’ll force a delay but keep an eye on any fixes that might come up. Cheers guys!

[Wayne Workman]

It’s very common on Ubuntu. Others on other systems have occasionally ran into the issue also. I know on Fedora Workstation 21 in Hyper-V, I had the issue. But with Fedora 21 Server in Hyper-V I don’t have the issue.

It’s just all about the timing, really.

And yes, that post you found is how you’d fix it.

And, there’s no reason to put up with having zero logs. Different systems experience different problems. For some, imaging doesn’t even work unless you make those services wait for a bit.