So…in desperation, I found this article:
https://wiki.fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0
This method boots up the 210 G1, however it breaks all the other machines from booting to the GUI PXE haha. I dont really understand what that “chainloading” is doing though.
So, I’m not quite sure what the issue was but I couldnt wait to get back to imaging. I ended up getting new install going and now its working fine.
@Rusty Just curious, but are your phones not on a separate VLAN? Most of the time companies run phones in parallel, but different LANs.
@Rusty Just curious, but are your phones not on a separate VLAN? Most of the time companies run phones in parallel, but different LANs.
@Tom-Elliott Tom I can confirm that I had to do a FULL wipe as well for it to work. I think it may be database related. I upgraded to the latest, took a copy of the DB then did a FULL wipe. Tested it and everything worked. Restored the database backup, and it started the issue again. Not a huge deal since I have my snapshots and went to a known working version again though.
@hmoobgolian I meant restoring it from your backup that YOU took before upgrading. If you didn’t do that, then unfortunately you cant go back.
Sorry to keep blowing this up with more information, but I seem to have narrowed it down to this:
Looks like 500 errors, but I’m tailing the error log and I havent seen 1 error come up. I corrected the strpos() error first as that was hard to manage looking at.
EDIT:
OK - after running that specific line in a browser from my personal machine, I get the following message. Not sure if it helps at all though:
[Thu Sep 24 14:34:00.303317 2015] [:error] [pid 25564] [client 10.1.5.1:49202] PHP Fatal error: Uncaught exception 'Exception' with message 'Invalid MAC Address!' in /var/www/html/fog/lib/fog/FOGBase.class.php:539\nStack trace:\n#0 /var/www/html/fog/lib/reg-task/TaskingElement.class.php(12): FOGBase->getHostItem(false)\n#1 [internal function]: TaskingElement->__construct('')\n#2 /var/www/html/fog/lib/fog/FOGBase.class.php(108): ReflectionClass->newInstance('')\n#3 /var/www/html/fog/service/Pre_Stage1.php(3): FOGBase->getClass('TaskQueue')\n#4 {main}\n thrown in /var/www/html/fog/lib/fog/FOGBase.class.php on line 539
Here is the access_log with a snippet around the host that is currently sitting on the checking in prompt. IP is 10.1.13.86
I think the relevent line is this one:
10.1.13.86 - - [24/Sep/2015:09:08:28 -0400] "GET /fog/service/Pre_Stage1.php?mac=48:5b:39:5d:c0:5f&type=down HTTP/1.1" 500 - "-" "Wget/1.16.3 (linux-gnu)"
The problem is that the error log file doesnt start ANY errors until I did the upgrade to try and correct this, beginning at 9:13AM.
@hmoobgolian Hmm…Looks like something funny happened. Can you restore your pre-upgrade backup and upgrade using the following command?
./installfog.sh -y
This will auto update the schema and take the “human” interaction out.
Well, my issue is back after updating to build 4743.
See attached error log. error_log
I updated yesterday to build 4743 and it stopped working, so I updated again today to 4752 and it still is not working.
@Killklli
I would suggest starting fresh then to see if it comes up. You are also updating your storage nodes, correct? I’m not sure if you need to update the storage, but it wouldn’t hurt to try.
@Marcus-Allen Hmm…this only seems to work on existing machines. From a newly re-imaged computer, the renaming still doesnt work…but I have another topic open about that.
@Jbob
To follow up. If I remove the legacy client first, then it installs. I’m now wondering if there is a way to install the new client through GPO after removing the old client?