After digging through the logs Hanz found that mysql_upgrade needed to be called to fix this issue. It’s very interesting we have not had too many people running into this but I am sure this is valuable information for others seeing this.

@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.

@tom-elliott I think you can close this…apparently one node (of the 😎 missed an upgrade and was still running odler version…I’ll keep an eye on it this week to confirm.

@joe-schmitt you can close this sorry to waste your time…it is working correctly.

@hanz Thank you very much for your feedback.

@Tom-Elliott The client is what I suspect is different as I haven’t actually been pushing the client for the last 3 months as I was instructed to remove the client from all but a couple labs. So this is the first attempt for a couple months to have the clients pushed to computers before we image them in order to take full advantage of multicasting from the local nodes. Now it seems that the process used before isn’t working completely together. If I push a client to a computer, it registers with fog, and I see the machine, I suppose (as I haven’t tested) that the snapins and power management will work on these hosts just as they always have. The problem is when I pxe boot the laptops, they show as not registered.

Now I have been running this system here for a couple years since trunk became available so it’s possible I have junk clients registered already, but I didn’t see these machines as I deleted them after removing the clients (at least not in the gui). I can verify this issue does not arise on desktop machines. I just don’t understand why the client would think it wasn’t registered.

I have no idea how any macs could be shared, as we haven’t done anything to initiate that. All clients are currently running Windows 7 so the “randomizing” of any wireless nics isn’t the issue here, but rather in the manner the client registers the hosts.

Quickreg works flawlessly, but it uses different mechanisms to register the nics I’m assuming since it’s still in a pre-boot environment.

Thank you sir for your response, it is working correctly…Just updated and was going through the motions checking functions.

@Hanz Login history has not been removed at all.

Fix is in RC-4

This is fixed (and verified fixed) in 1.3.1-RC-2.

@Tom-Elliott worked like a charm sir

I’ve tried the up-comming rc-14 with Fedora and it installs without any issues beyond needing firewall and SELinux configured as you would normally need to do.

@demontraven Forgive my sounding rude, but this has no impact on actual functionality. (Sorry I know it’s rude, but I’m just being honest).

That said, for now please run this command:
wget -O /var/www/fog/lib/fog/fogcore.class.php https://raw.githubusercontent.com/FOGProject/fogproject/5726017bed15f89e25fc9ad8fc19ec1b523b4f88/packages/web/lib/fog/fogcore.class.php

This should fix the uptime issue for you.

@Tom-Elliott My apologies, this can be marked as solved. I was restarting fogservice to test for the popups for shutdown, and restart tasking; however restarting the fogservice doesn’t really reset the client like I thought. It requires that the client checks in on it’s normal time ( sleep service time) for the popups to appear.

@Tom-Elliott yessir

@Joe-Schmitt thank you sir

@Tom-Elliott ok that worked after the refresh…didn’t know I had to do that

@Tom-Elliott yessir, I do believe we are back to original speeds…

@Tom-Elliott you are a beast sir, thank you

@Tom-Elliott 7613 cleared up both this issue and the original snapin issue…You Da Man