Rooting around in the source code led us to the mysql database (table: tasks), which showed there were some tasks where taskState was set to ‘1’, indicating that they were in progress and filling the queue. However, none of those showed in the active or scheduled tasks in the control panel.

Manually setting taskState to ‘2’ for those entries in the database cleared it out and allowed the new active “In queue” task to start.

I’m not sure how those old tasks never got their sql entries updated.

That page says “[SIZE=4][FONT=Times][COLOR=#000000]Waiting for a slot, 0 PCs are in front of me.”[/COLOR][/FONT][/SIZE]

I’m going to be looking over the init file and fog script today, see if anything jumps out.
[SIZE=4][FONT=Times][COLOR=#000000][/COLOR][/FONT][/SIZE]

Thanks, I’ll start looking there!

No ideas? I’ve checked all the configs and everything seems to check out. All the database passwords appear to be set up correctly. The log files show nothing out of the ordinary.

A task is started on the client machine and it sits there saying “Waiting for a slot, 0 PCs are in front of me”. In the control panel, you can see it under active tasks, with state “In Line”. At the same time, /op/fog/log/fogscheduler.log says:
[CODE][09-12-12 3:14:44 pm] * [09-12-12 3:14:44 pm] Checking if I am the group manager.
[09-12-12 3:14:44 pm] * [09-12-12 3:14:44 pm] I am the group manager.
[09-12-12 3:14:45 pm] * [09-12-12 3:14:45 pm] No tasks found.[/CODE]

I’ve inherited an issue with our Fog server where a deploy image task won’t run despite 0 PCs in the queue. I’ve been reading up on Fog to familiarize myself, but haven’t been able to find the root of this issue.

What I’ve done:

1. Turn on new machine and network boot
2. Perform full registration, choose image, and let it go
3. It reboots, the task is registered in the Fog tasks interface, and fog on the machine gets ready to image
4. The machine displays “Waiting for a slot, 0 PCs are in front of me. (x min)”

As far as I can tell the Fog install is default. There is the default storage group and a single default node. That node is set to 5 clients max. When I list “All Tasks” there is only this one, and the state is “In Line” (with options to force, delete, etc). Forcing it works fine and is how they’ve done it previously.

The issue is that we’d like the deploys to begin automatically within the queue (currently empty), without having to go into the tasks menu and manually forcing them. We’ll be deploying several hundred machines next month so you can see why.

Thanks for any help!