I have a script that @Wayne-Workman wrote, that shows pending host as they come in. I noticed that when a host comes in as pending…all previously accepted/known hosts show as pending as well. When I manually add the host from the list in the log output from said script, all host disappear from pending and all looks as it should.

18/03/2016 10:54:02
 
Pending Hosts:
3557	dmNew1
 
Number of Approved Hosts:
1756
 
Number of Total Hosts:
1757
 
Number of Total MAC addresses:
3558
 
uptime Output:
 10:54:02 up  2:11,  2 users,  load average: 1.00, 1.26, 1.40

I reset the encryption keys after deleting all hosts and adding again from the old database backup from 6549.

the host dmnew was manually set to pending, which shows correctly; however all hosts without a key are showing back up under pending hosts. This has happened since updating to 6777 from 6549. and now I’m currently on 6815.

When I accept the pending hosts listed from output of script, all goes back to normal

I just had to do this and can verify that changing parameters for /images directory in .fogsettings and rerunning installer…then changing it in gui worked like a charm with no export modifcation necessary as fog did it for me. Mounted of course in /etc/fstab as UUID.

@george1421 I had to use *.pushbullet.com and *.api.pushbullet.com for web filtering url in Lightspeed setup

Per svn 6303 multicast clients show “Attempting to check in …Failed”

Apache error log

[Wed Feb 17 10:24:36.668646 2016] [:error] [pid 19608] [client 10.72.217.149:43896] PHP Fatal error: Uncaught Error: Call to a member function get() on unknown in /var/www/html/fog/lib/reg-task/taskqueue.class.php:51\nStack trace:\n#0 /var/www/html/fog/service/mc_checkin.php(3): TaskQueue->checkIn()\n#1 {main}\n thrown in /var/www/html/fog/lib/reg-task/taskqueue.class.php on line 51
[Wed Feb 17 10:24:37.672038 2016] [:error] [pid 19693] [client 10.72.217.148:41360] PHP Fatal error: Uncaught Error: Call to a member function get() on unknown in /var/www/html/fog/lib/reg-task/taskqueue.class.php:51\nStack trace:\n#0 /var/www/html/fog/service/mc_checkin.php(3): TaskQueue->checkIn()\n#1 {main}\n thrown in /var/www/html/fog/lib/reg-task/taskqueue.class.php on line 51
[Wed Feb 17 10:24:38.523917 2016] [:error] [pid 12583] [client 10.72.217.147:44200] PHP Fatal error: Uncaught Error: Call to a member function get() on unknown in /var/www/html/fog/lib/reg-task/taskqueue.class.php:51\nStack trace:\n#0 /var/www/html/fog/service/mc_checkin.php(3): TaskQueue->checkIn()\n#1 {main}\n thrown in /var/www/html/fog/lib/reg-task/taskqueue.class.php on line 51

those were the 4 clients, and it re-iterates every 5 seconds.

Regular imaging check in works fine. I should add that this is multicast from storage node.

@george1421

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\

Value
HiberbootEnabled

REG_DWORD set to 0 hex

@Wayne-Workman UPDATE Apparently disabling firewalld.service didn’t stick. Working now
my apologies for assuming it was set correctly.

It would be nice to get a msg when snapin completion occurs. Possibly selectable reports via pushbullet setup page ?

@Sebastian-Roth yes that is correct, I’m sorry I didn’t really explain it thoroughly. ipxe.kpxe works really well so far with all our systems, is there any particular advantages to undionly.kpxe over ipxe.kpxe ?

@Tom-Elliott thanks to you and Mr. Workman…I would have had no way to know which host was showing as pending if it wasn’t for his script.

thanks for all the mysql pointers, and that last line worked like a charm.

@Sebastian-Roth Error looks very similar, but doesn’t even get to the Setting up MySQL user and database

I know there isn’t the whole log, but all other options either skipped or ok to this point.

Foginstall.log

The current *fogstorage* database password does not meet high
   security standards. We will generate a new password and update
   all the settings on this FOG server for you. Please take note
   of the following credentials that you need to manually update
   on all your storage nodes' /opt/fog/.fogsettings configuration
   files and re-run (!) the FOG installer:
   snmysqluser='fogstorage'
   snmysqlpass='5dpy!GfbeoTr3EPFmLVl'

   Press [Enter] to proceed after you noted down the credentials.

Failed!

Fog_Error_1.5.9-RC2.8.log

chsh: Shell not changed.
Changing shell for fogproject.
New password: Retype new password: Changing password for user fogproject.
passwd: all authentication tokens updated successfully.
ERROR 1558 (HY000) at line 8: Column count of mysql.proc is wrong. Expected 21,>

@Sebastian-Roth typed

@Sebastian-Roth yessir, but not with blank password mysql -u root…

Does this look strange or anything ? this is under fog database

MariaDB [fog]> select user, password, host from mysql.user;
+------------+-------------------------------------------+------------+
| user       | password                                  | host       |
+------------+-------------------------------------------+------------+
| root       | (I removed)                               | localhost  |
| root       |                                           | fog-server |
| root       |                                           | 127.0.0.1  |
| root       |                                           | ::1        |
|            |                                           | localhost  |
|            |                                           | fog-server |
| fogstorage | (I removed)           t                   | %          |
+------------+-------------------------------------------+------------+
7 rows in set (0.000 sec)

MariaDB [fog]>

@Sebastian-Roth

 To improve the overall security the installer will create an
   unpriviledged database user account for FOG's database access.
   Please provide the database *root* user password. Be asured
   that this password will only be used while the FOG installer
   is running and won't be stored anywhere:

   Failed! Terminating installer now.
[root@fog-server bin]#

GNU nano 4.2 fog_error_1.5.8.19.log
xinetd-2.3.15-28.fc30.x86_64
xz-devel-5.2.4-5.fc30.x86_64
chsh: Shell not changed.
Changing shell for fogproject.
New password: Retype new password: Changing password for user fogproject.
passwd: all authentication tokens updated successfully.

error log posted above

Server running Fedora 30 on Hyper-V VM and after being prompted to enter root passwordand hitting ENTER I get the following error…

The current fogstorage database password does not meet high
   security standards. We will generate a new password and update
   all the settings on this FOG server for you. Please take note
   of the following credentials that you need to manually update
   on all your storage nodes' /opt/fog/.fogsettings configuration
   files and re-run (!) the FOG installer:
   snmysqluser='fogstorage'
   snmysqlpass='fIQ03SoTJxHjKD@0D0xL'

   Press [Enter] to proceed after you noted down the credentials.

 * Setting up MySQL user and database..........................Failed!
[root@fog-server bin]#

I’ve read that there are workarounds for blank passwords, but I can access mysql -u root -p correctly with password. Before and after attempted installation. Any suggestions ?

@george1421 I had to use *.pushbullet.com and *.api.pushbullet.com for web filtering url in Lightspeed setup

@fry_p lightspeed…I eventually figured it out thank you though

@fry_p which site did you whitelist ? *.api.pushbullet.com or .pushbullet.com/ I tried whitelisting, but with no success.

@dawildqc Curious why pxe boot screenshot is showing 2 gateway ip addresses… 192.168.5.5 and 192.168.5.7 ? I’d assume that could be an issue with connectivity

@george1421 The weird and suspicious part is that 1.5.5 was last known working version, 1.5.7…I’ll also note that the parrallel behavior has always performed that way, at least for quite some versions now. I could actually transfer a single new captured image to all nodes at the same time and they would all run at their perspective top speeds (I have 4 schools that only have 100Mb connection and the rest are all gigabit. This speed is definitely new though.

Note I just manually transfered the file via ftp and the speed was back to normal at another node…then on this node in question and it is indeed a port going bad or the cable itself only allowing a very minimal top speed of 10-15 Mb. This can be closed, but I appreciate the new command.