@Tom-Elliott
As a curiosity, after two hours of 37 PCs deployment , 10 are finished, 10 are rolling, 17 are waiting. Tasks table is 815000 records long and tasks db files are 138MiB total.
Don’t get me wrong, FOG is awesome tool - seriously.

@siarkowski
Corrupeted DB or schema is highly possible.
I’ll backup tables: users, hosts, groups and images data and make a fresh FOG install.
I"ll let you know as soon as I’ll do it. It will be no sooner then next week I’m afraid.

@Tom-Elliott
I finished all running deploy tasks, cleaned task table.
At this moment partition was over 5GiB free disk space.
I started 37PCs deploy task and the story is same again. Database tasks table files were 40kB before I started the task and after 30 minutes database tasks table files are over 4MB.
Services work fine, tasks are processed, but tasks table is over 26000 records long and it’s increasing.
I’m pretty sure if I start task for 200 PCs disk will run out of space after few hours

@Tom-Elliott
Thanks for replay.

In the tasks menu, scheduled Tasks there are no entries. However but in database table scheduledTasks the are two entries:

±-----±------------±-------±-------±-------------±---------±-------±------±--------±------±----------±--------------±----------±-----------±---------±---------±---------±---------±---------±-----------±---------+
| stID | stName | stDesc | stType | stTaskTypeID | stMinute | stHour | stDOM | stMonth | stDOW | stIsGroup | stGroupHostID | stImageID | stShutDown | stOther1 | stOther2 | stOther3 | stOther4 | stOther5 | stDateTime | stActive |
±-----±------------±-------±-------±-------------±---------±-------±------±--------±------±----------±--------------±----------±-----------±---------±---------±---------±---------±---------±-----------±---------+
| 1 | Deploy Task | | S | 1 | | | | | | 1 | 6 | 0 | | | -1 | fog | 1 | | 1681921800 | 0 |
| 2 | Deploy Task | | S | 1 | | | | | | 1 | 8 | 0 | | | -1 | fog | 1 | | 1741105800 | 0 |
±-----±------------±-------±-------±-------------±---------±-------±------±--------±------±----------±--------------±----------±-----------±---------±---------±---------±---------±---------±-----------±---------+

Hello All,

Happy New Year!

Since I upgraded FOG to 1.5.10.1734 I noticed Apache is returning 503. I started deployment for over 200 PCs and after few hours 503 occurred.

I could SSH the server, and I found it is run out of disk space. It was occupied by database files, to be precise tasks table.

I started MySQL client and found a huge number of entries with strange data.
"
| taskID | taskName | taskCreateTime | taskCheckIn | taskHostID | taskImageID | taskStateID | taskIsDebug | taskCreateBy | taskForce | taskScheduledStartTime | taskTypeID | taskPCT | taskBPM | taskTimeElapsed | taskTimeRemaining | taskDataCopied | taskPercentText | taskDataTotal | taskNFSGroupID | taskNFSMemberID | taskNFSFailures | taskLastMemberID | taskWOL | taskPassreset | taskShutdown |
±---------±---------±--------------------±--------------------±-----------±------------±------------±------------±-------------±----------±-----------------------±-----------±-----------±--------±----------------±------------------±---------------±----------------±--------------±---------------±----------------±----------------±-----------------±--------±--------------±-------------+
| 12687010 | | 2026-01-02 09:52:02 | 0000-00-00 00:00:00 | 0 | 0 | 1 | 0 | fog | | 0000-00-00 00:00:00 | 0 | 0000000000 | | | | | | | 0 | 0 | | 0 | | | |
±---------±---------±--------------------±--------------------±-----------±------------±------------±------------±-------------±----------±-----------------------±-----------±-----------±--------±----------------±------------------±---------------±----------------±--------------±---------------±----------------±----------------±-----------------±--------±--------------±-------------+
1 row in set (0.00 sec)
"

There are no entry in images table with ImageID equal to 0.

I deleted all data in task table with taskStateID equal to 1 and taskImageID equal to 0.
Tasks resumed, but I had to delete data in task table with taskImageID equal to 0 to avoid disk run out of space.

After all task were finished I cleaned task table, there were entries with taskStateID equal to 4 or 5 only.

OK, I starter a single PC deploy task and watched task table. A single entry with taskStateID equal to 1 apeared, after client started the task it was altered to taskStateID equal to 3, after task was finished it was altered to taskStatedID equal to 4. That’s how it should wark.

I started a 31 PCs deploy task, at the beging 31 new entries apeard in task table with taskStateID equal to 1, 10 PCs started to deploy and 10 entries were altered to taskStateID equal to 3. However I noticed a huge number of enries apeared, all of them with taskStateID equal to 1 and taskImageID equal to 0. After all 31 PCs deployments were finished I checked tasks table. In the task table there were over 500000 entries with taskStateId equal to 1 and taskImageID equal to 0!

I cleaned task table again and started deployment for 11 PCs.
It started nice with 11 new entries in task table with taskStateID equal to 1. 10 PCs started to deploy and 10 entries were altered to taskStateID equal to 3. Again new entries with taskStateID equal to 1 and taskImageID equal to 0 sarted to apear. A single new entry appeared about every second. It corresponds with task slot check at client side, I think so. I forced paused deploy to start and new entries stopped.

Did You have similar situation.
I’ll be grateful for any advice.

Best
Marcin