Posts made by Marcus Allen

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

log.log

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

snippet.txt

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?

I should also follow up with this:

Currently on this machine is the legacy version of Fog. I will need to find a way to remove the legacy version and install the new version, without touching 3500 computers. I’m going to remove the legacy version manually first, then try to reinstall the new version to see if that helps.

Not sure why this isn’t working, but I’m getting an error trying to install the Fog Client MSI.

It tells me Unable to Install Fog Project CA: The system cannot find the specified file. I did check and ensure that the fog address is correct during the install process and the web root is /fog

I’m having issues with the join to AD and renaming of machines with the OLD client, but version 0.9.5 seemed to work fine on whatever machines already had it (I had version 0.9.3/0.9.4 installed on some test machines and they appeared to “auto upgrade”). The rename and join to AD worked after clicking “reset encryption data”

@Uncle-Frank

It literally says, repeated over and over:

9/22/2015 7:04 PM FOG::SnapinClient Module is disabled on this host

Nothing else. Thats it for the last several hours, except replace the word “host” with “mac” earlier in the day until I manually added the mac by going into the individual host and adding it there.

We have the snapinmodule disabled as we don’t use it. I just forgot to uncheck the box when installing the fog client again.

@Uncle-Frank Settings are Correct.

@Tom-Elliot Sorry about that…Still on version 4738. The client is the legacy one. We have 4 pending macs.

@Wayne-Workman said:

Apologies - the service is called FOGImageReplicator Make sure that’s running, and try to restart it.

To touch on this. I had this problem and by rebooting this on the node first, then the node master last - it seemed to fix it. But I havent had this issue on the latest updates (trunk versions) of FOG.

It seems to be the same few machines, but these machines worked earlier in the year when we first imaged them. I’m almost wondering if it has something to do with not doing a “full” inventory somehow.

The error in the c:\fog.log said something along the lines of “XXXModule is disabled on this mac”

I’m having several machines that are not auto-renaming or auto-joining to AD and the only common denominator I’ve found is they are sitting in the Pending MAC list. This is fine if I could approve the MAC, but I cannot and have not ever been able to.

I dont know if this will fix my issue, but I’d like to try.

Tailed log file does this:

[Tue Sep 22 16:20:43.210001 2015] [:error] [pid 22025] [client 10.1.5.1:53977] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 84 bytes) in /var/www/html/fog/lib/db/MySQL.class.php on line 115, referer: http://fog.hpsvikings.org/fog/management/index.php?node=report&sub=pend-mac

Thanks!

@Tom-Elliott

Upgraded! Thanks again sir for all of your hard work! It really is appreciated.

@Tom-Elliott

Thanks a bunch! You got the imaging going. There is still the can’t modify header information error, but I don’t look at the logs too often, so it doesnt bother me as much! I included them just in case you’d like to check it out though!

tailed file.txt

@Tom-Elliott

Here is the tailed file. 10.1.1.28 is a storage node, .24 is the main fog server, .22 is the storage master.

13.249 is the client.

tailed file.txt