Clients Booting into FOG are Met With "Attempting to check in......failed"
-
We have had an issue where when clients are booting into FOG to run a scheduled task they fail a check in and just repeat the message.
This was on both the stable build and dev-branch. I updated to 1.6-working and everything is working normally. I’m curious what the issue was.
I have some error code as well regarding PHP:
[Tue Jan 13 13:24:55.033900 2026] [proxy_fcgi:error] [pid 2534002] [client xxx.xxx.xxx.xxx:53259] AH01071: Got error ‘PHP message: PHP Warning: Attempt to read property “dev” on null in /var/www/fog/lib/pages/dashboardpage.class.php on line 586; PHP message: PHP Warning: Attempt to read property “rx” on null in /var/www/fog/lib/pages/dashboardpage.class.php on line 588; PHP message: PHP Warning: Attempt to read property “tx” on null in /var/www/fog/lib/pages/dashboardpage.class.php on line 589’, referer: http://xxx.xxx.xxx.xxx/fog/management/index.php?node=home
[Tue Jan 13 13:45:24.932457 2026] [proxy_fcgi:error] [pid 2534000] [client xxx.xxx.xxx.xxx:47848] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:396\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(396): min()\n#1 /var/www/fog/lib/reg-task/taskqueue.class.php(112): Image->getStorageGroup()\n#2 /var/www/fog/service/Pre_Stage1.php(24): TaskQueue->checkIn()\n#3 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 396’The error log was just a repeat of the above.
I’m just curious what broke within FOG or PHP to cause this issue.Thank you!
-
@FOGBreaker101 Please update and try again.
I am not 100% sure what the actual error is, but what I’m seeing from a DB standpoint there is a totally different issue occurring and that I could work around.
Can you try to update and try again? If you’re still having an issue and I can try to take a look.
-
@Tom-Elliott I had updated to 1.6-working after dropping the fog table in mysql and everyting is working correctly now. I posted this mainly as a “why did this happen” thing. I’m sorry for the confusion.
Before I went to 1.6 I had dropped the fog table from mysql and deleted .fogsettings from /opt/fog as well so it would do a new install without carrying any settings. Even doing an install after that it was still giving the error when trying to capture an image.
-
@FOGBreaker101 over the last couple of days we found there was a bug in fog that could create required items inappropriately. We made some code to try to prevent that altogether, as well as fixed the issue directly causing the bug. This showed us some other bug(s) and likely we’ll get more reports of new bugs yet. But hopefully this helps explain the why it happened.
It did get us to make better logging and functionality of the pdodb class so all in all a worthwhile improvement.
