Posts made by Marcus Allen

@jamesb Can you try reinstalling the version you had before upgrading? Like a fresh install, then restore your sql backup? I’m sure it is just that something went awry with the upgrade process that has something locked up.

I’d try restoring to your latest backup, then attempting the upgrade again. I also upgraded to 3764 this morning and have no issues when it comes to changing the FOG config settings.

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.

Along with my other issues that I’ve been having this week, after upgrading to the latest version of Fog, I’ve now run into the biggest one. I cant register any hosts anymore. Not sure why, it just goes to “Attempting to Register Host” then its like someone presses the enter key over and over (generating a new line until the screen appears to be blank).

Looking at the apache logs, I see this come up:

[Wed Jul 08 13:26:08.273023 2015] [:error] [pid 2535] [client 10.1.31.92:38024] PHP Fatal error: Using $this when not in object context in /var/www/fog/service/auto.register.php on line 143

I’m using ubuntu 14.04, with Fog 3725

Yes. Nothing has changed except the upgrade of fog. Now I’m currently using the Domain Admin account to ensure that it has permissions needed.

I’ve updated to the latest SVN to try and fix some other issues, however it seems to have stopped AD from working with Fog. I just tried to rename a machine (also using the newest FOG Client on this machine).

The computer auto-reboots and renames appropriately, however it gives a Trust Relationship error indicating the computer name cant be found. What happens is that it doesnt update the name in Active Directory. I have fog rename the machine back to the old name, and it works again.

Here is the fog.log file:

7/7/2015 11:44 AM Middleware::Communication Response: Success
7/7/2015 11:44 AM Middleware::Communication URL: http://MYFOGIPADDRESS/fog/service/hostname.php?moduleid=hostnamechanger&mac=MYPCSMACADDRESS|&newService=1
7/7/2015 11:44 AM Middleware::Communication Response: Success
7/7/2015 11:44 AM HostnameChanger Checking Hostname
7/7/2015 11:44 AM HostnameChanger Hostname is correct
7/7/2015 11:44 AM HostnameChanger Registering host with active directory
7/7/2015 11:44 AM HostnameChanger ERROR: Required Domain Joining information is missing
7/7/2015 11:44 AM HostnameChanger Activing host with product key

ERROR: Required Domain Joining information is missing obviously means something is missing, but I dont know what. All of the fields are filled in.

@Wayne-Workman Unfortunately I have no idea what that means for me haha! I’ve messed with it a bit more today, but haven’t found out why.

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.

Got Fog updated to 1.2.0. The 210’s still don’t work though, still gets stuck on the iPXE right before the fog GUI loads (before the php files get called).

Looks to me that it might be a driver issue, but I’m not positive.

@Wayne-Workman Gotcha. I have backups of the images, I suppose a better way to word my concern would’ve been to say “incompatible” with the new version.

I have backups of the hosts and config DBs, as well as images, so I’m not concerned about that! Backups are key. I don’t feel bad for those who don’t do backups haha.

@Wayne-Workman I’d be willing to try out 1.2.0, but I heard I may lose all of my existing images. Is that true?

Secure boot is off in the BIOS, it is setup to use undionly.kkpxe already. We’ve been using Fog for about a year at this point, and this seems to be the only machine causing issues.

@Wayne-Workman

Fog is on 1.1.2. (We tried version 1.2.0, however ran into AD issues not registering Full Host machines). At this point, I’m just trying to boot into FOG’s Registration GUI. It is the only machine out of 9 models we have that won’t go.

I applied the latest kernel in hopes that was it, but it was not. It sounds like the same issue that Baron was having.

Were you able to get the 210’s to image? We have 300 that just arrive and I’m not having much luck.