I found this in the apache logs when it happens.

[Wed Apr 11 13:52:45.028047 2018] [proxy_fcgi:error] [pid 2841] (70007)The timeout specified has expired: [client 10.10.150.73:62324] AH01075: Error dispatching request to :, referer: http://10fogserver/fog/management/index.php?node=host&sub=deploy&id=160&type=1

I am getting this as well… its hit and miss. If I refresh the page the web interface comes back.

You can mark this as solved.

@wayne-workman

I figured it out!
I took a look at the snapinGroupAssoc table and notice that there were some very odd numbers in the sgaStorageID column varying from 1, 4 and even 22.
I then ran this query to empty the entire snapinGroupAssoc table:

SET FOREIGN_KEY_CHECKS = 0;
TRUNCATE snapinGroupAssoc;

I then clicked on the “List All Snapins” from the web interface and the snapinGroupAssoc table was repopulated with the Default storage ID for all Snapins, from there I went to each Snapin and assigned the second storage group and the checkmark for primary works!

the snapin hash service wasn’t working for the majority of my snapins because the storage group didn’t match any of my actual storage ID’s in the database.

@wayne-workman
I only have 2 storage groups.
I looked this morning and the snapin hash was still empty on the majority of the snapins.
the one thing I did notice is that the permissions were set to fog:apache on the snapins without hashes and when I upload a snapin through the web interface the permissions are fog:fog.

@tom-elliott

==> fogsnapinhash.log <==
[03-15-18 4:48:28 pm]  * Trying Snapin hash for: Synergize Client v13.1, ID: 116
[03-15-18 4:48:28 pm]  * Getting snapin hash and size for: Synergize Client v13.1.
[03-15-18 4:48:28 pm]  | Hash: 46ddfd39e74b31fc97f78ce17c6208a5619884e2b75d2c10a53ab5ae842a1fb634230126de53cf11d1305dab04fdcca95c5b50886d453c2fc5f33c46740feb26
[03-15-18 4:48:28 pm]  * Trying Snapin hash for: Synergize Indexing v13.1, ID: 115
[03-15-18 4:48:28 pm]  * Getting snapin hash and size for: Synergize Indexing v13.1.
[03-15-18 4:48:29 pm]  | Hash: 1749c4c8bd5dc664796a0c56305ee2204a26bbc1166e7c263ec51a8f02b70f4a253803f4af141d2da5d4462b3aa599ff88d062fa3313aadf06ae58255b5b0c4f
[03-15-18 4:48:29 pm]  * Trying Snapin hash for: UAG Components, ID: 56
[03-15-18 4:48:29 pm]  * Getting snapin hash and size for: UAG Components.
[03-15-18 4:48:29 pm]  | Hash: d78f69a8ebe78a44e338fb53c6bb287577e24895ded8d233559c74c3c5b063af1cae5fdb2e8637053a4e201da87e16347fa735e11d258788351956b7d9c6db83
[03-15-18 4:48:29 pm]  * Completed.
[root@10fogserver fog]#

It says completed but there are allot more snapins that need hashes.
I did notice that when setting the primary storage group for a snapin it doesn’t stay checked.
Also when adding or making changes to snapin groups it doesn’t refresh the screen. you have to do it manually by pressing F5 or the browser refresh button.

Video

How long should this take? I see a few hashes in the database but there are allot that is still null.

@wayne-workman
Thanks I will truncate the snapins.sHash table.

UPDATE snapins SET sHash=NULL;

I recently migrated my fog installation to a new server and I am getting allot of snapin hash doesn’t match.
Is there a way to get the hash to match through the shell? Currently, I have been just re-importing them one by one through the GUI.

Thanks!

@wayne-workman @Tom-Elliott
Thanks for the help guys! I was able to get it re-installed although I have one issue, I will open another thread for that.
Thanks again!

At this point I really would like to Uninstall or remove Fog and reinstall it.
I have a database backup. so I can import the hosts table.
is there an updated procedure on how to remove fog all the services for fog?

as for the nodes, they work fine except for one location.

@tom-elliott
It very frustrating when trying to navigate to different hosts and make changes and it ends up at the schema update page that then brings you back to the Dashboard. sometimes it does this 3 or 4 times. I don’t know if these messages are causing this or not.
sorry very frustrated…

@wayne-workman
The errors are all coming from the storage nodes.

here is a complete log example:

[Fri Mar 09 16:19:11.416500 2018] [:error] [pid 5845] [client 192.168.18.39:57380] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
[Fri Mar 09 16:19:12.090818 2018] [:error] [pid 8867] [client 10.17.40.39:33785] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
[Fri Mar 09 16:19:35.050565 2018] [:error] [pid 23438] [client 10.10.112.39:37637] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
[Fri Mar 09 16:20:10.797218 2018] [:error] [pid 23438] [client 10.30.40.39:38838] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
[Fri Mar 09 16:21:21.500537 2018] [:error] [pid 7753] [client 192.168.18.39:57682] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
[Fri Mar 09 16:22:20.815902 2018] [:error] [pid 16364] [client 10.30.40.39:39060] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
[Fri Mar 09 16:22:21.809934 2018] [:error] [pid 21826] [client 192.168.10.39:50058] PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447

@wayne-workman
Sorry, Fog version 1.5.0 on Centos 7.

I am seeing allot of these errors in my apache logs:

PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447
PHP Fatal error:  Call to a member function lastInsertId() on boolean in /var/www/html/fog/lib/db/pdodb.class.php on line 447, referer: http://10fogserver/fog/management/index.php

Thanks!

@sebastian-roth
Here is a new VIDEO with the new kernels and inits.

Just so I am clear what is the git repository link I should be using?

@sebastian-roth
The kernel panics with Kernel too old.
Video

@sebastian-roth
Here is a new video

@sebastian-roth

I updated the inits and I the problem persists.

@sebastian-roth said in Fog 1.5.0 Storage Node Problems with PXE booting?:

10fogserver

Sorry i should have been more clear… the 10fogserver is management, 30fogserver is the node we are having issues with.
I was only mentioning the browser issue because I thought it may be causing the PXE problem.

I will try the new init files and update.
Thanks!