@UWPVIOLATOR it would appear we have similar issues. Our Dell Precisions are doing something similar “Precision T3610 Invalid entry length (16). Fixed up to 11.” This is breaking our postdownload driver scripts as well. If you do a debug task on one of the machines and run dmidecode -t 1 you should see the invalid portion at the bottom. I can confirm on a T3610 that dmidecode 3.0-3 fixes the issue, it appears that fog is using version 3.0 (cannot confirm this though).
Best posts made by Jason Shoemake
-
RE: Invalid entry length (0). DMI table is broken! Stop.
-
RE: Invalid entry length (0). DMI table is broken! Stop.
@george1421 sorry if I had a typo somewhere, but 3.0-2 does not work. I have confirmed that anything newer than that does indeed work. Using 3.1-1 and your fix everything is working across the board now on our server. Thanks a lot, hopefully this will be helpful for @UWPVIOLATOR as well.
-
RE: LDAP Plugin - ID Must Be Set To Edit Error
@noelpd @george1421 not sure if this helps, but we had a similar issue with the location plugin and the fix was in this thread from Tom. This also solved an issue with the Wol Broadcast… Needed to remove and add the plugins back after running the fix…
https://forums.fogproject.org/topic/10364/issues-after-upgrading-from-1-4-3-to-1-4-4
Latest posts made by Jason Shoemake
-
RE: LDAP Plugin - ID Must Be Set To Edit Error
@noelpd @george1421 not sure if this helps, but we had a similar issue with the location plugin and the fix was in this thread from Tom. This also solved an issue with the Wol Broadcast… Needed to remove and add the plugins back after running the fix…
https://forums.fogproject.org/topic/10364/issues-after-upgrading-from-1-4-3-to-1-4-4
-
RE: Invalid entry length (0). DMI table is broken! Stop.
@george1421 sorry if I had a typo somewhere, but 3.0-2 does not work. I have confirmed that anything newer than that does indeed work. Using 3.1-1 and your fix everything is working across the board now on our server. Thanks a lot, hopefully this will be helpful for @UWPVIOLATOR as well.
-
RE: Invalid entry length (0). DMI table is broken! Stop.
@george1421 you are correct CentOS 7 is 3.0-2, Latest Fedora 26 is 3.1-1, Ubuntu 17.04 is 3.0-4.
I tested 3.0-2 and 3.0-4 on the precision using a USB stick and can confirm the error is indeed resolved in versions newer than 3.0-2
Thanks for the response.
-
RE: Invalid entry length (0). DMI table is broken! Stop.
@UWPVIOLATOR it would appear we have similar issues. Our Dell Precisions are doing something similar “Precision T3610 Invalid entry length (16). Fixed up to 11.” This is breaking our postdownload driver scripts as well. If you do a debug task on one of the machines and run dmidecode -t 1 you should see the invalid portion at the bottom. I can confirm on a T3610 that dmidecode 3.0-3 fixes the issue, it appears that fog is using version 3.0 (cannot confirm this though).
-
RE: Issues with RC 26/27
@Tom-Elliott everything seems to be working fine now using the working-branch, both inventory and the image task, thanks.
-
RE: Issues with RC 26/27
@Tom-Elliott Yes, pulled the latest, fixed the issue with imaging. Full Host registration still does not create a task nor does it populate Primary User and Other Tag.
-
RE: Issues with RC 26/27
If I do a quick image or create a task from the web interface it is now working. However, when we perform a full host registration no image task gets created and Primary user and Other tag do not get populated. Issues seemed to pop up with RC 26, not sure if that helps.Please let me know if you need any additional info from me, thanks.
[Thu Dec 01 10:20:11.147911 2016] [:error] [pid 128344] [client 10.230.11.26:57676] PHP Fatal error: Call to a member function isValid() on null in /var/www/html/fog/lib/fog/host.class.php on line 1609```
-
Issues with RC 26/27
Server
- FOG Version: RC 27
- OS: CentOS 7
Description
With RC 26 we noticed when performing a full registration that inventory data, specifically primary name and other tag were not being populated and an image task was not being created. Updated to RC 27 this morning to see if those issues were fixed (are not fixed), and now when we try to do an image we get an in queue message and failed to check in (only 1 imaging task). I have attached a few lines from the apache error log, please let me know if you need any additional information, thanks.
[Thu Dec 01 08:25:04.247048 2016] [:error] [pid 1667] [client 10.230.11.26:44516] PHP Fatal error: Call to undefined method TaskQueue::StorageGroup() in /var/www/html/fog/lib/reg-task/taskingelement.class.php on line 115 [Thu Dec 01 08:25:09.350237 2016] [:error] [pid 8986] [client 10.230.11.26:44518] PHP Fatal error: Call to undefined method TaskQueue::StorageGroup() in /var/www/html/fog/lib/reg-task/taskingelement.class.php on line 115 [Thu Dec 01 08:25:14.437912 2016] [:error] [pid 1667] [client 10.230.11.26:44520] PHP Fatal error: Call to undefined method TaskQueue::StorageGroup() in /var/www/html/fog/lib/reg-task/taskingelement.class.php on line 115 [Thu Dec 01 08:25:19.532576 2016] [:error] [pid 1665] [client 10.230.11.26:44522] PHP Fatal error: Call to undefined method TaskQueue::StorageGroup() in /var/www/html/fog/lib/reg-task/taskingelement.class.php on line 115 [Thu Dec 01 08:25:24.631734 2016] [:error] [pid 1667] [client 10.230.11.26:44524] PHP Fatal error: Call to undefined method TaskQueue::StorageGroup() in /var/www/html/fog/lib/reg-task/taskingelement.class.php on line 115 Thu Dec 01 08:13:34.378029 2016] [:error] [pid 33906] [client 10.230.11.60:53583] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 153```
-
RE: Error Returned: Reattempting to update database...Failed
I’m having the same error message when updating an image. The image appears to get stuck in the dev folder. Running through the ftp fixes in the wiki did nothing for me. On a side note I had a similar issue with RC1, appeared to be fixed in RC2 or RC3. Attempting to upload the image as new at the moment.
-
RE: Change Needed for VM to PXE boot to FOG...
Running the latest version of fog .33b and I can confirm this is an issue with Hyper-V. Works fine from VirtualBox