Posts made by shird

@shird said in r5767 Host is not registered / Invalid MAC after I set an image:

Updated to 5778.

Still having issues with doing a full registration. Apache is currently reporting the following error:

[Wed Jun 29 09:47:03.453736 2016] [:error] [pid 10683] [client x.x.x.x:33658] PHP Fatal error:  Call to a member function get() on string in /var/www/fog/lib/fog/host.class.php on line 373

Quick reg is showing as “Attempting to register host …Failed” however Apache is reporting the same error as above.

Apologies, working now. User error! Time to get some coffee…

Thanks again for the help Tom.

Updated to 5778.

Still having issues with doing a full registration. Apache is currently reporting the following error:

[Wed Jun 29 09:47:03.453736 2016] [:error] [pid 10683] [client x.x.x.x:33658] PHP Fatal error:  Call to a member function get() on string in /var/www/fog/lib/fog/host.class.php on line 373

Quick reg is showing as “Attempting to register host …Failed” however Apache is reporting the same error as above.

@Tom-Elliott Cool. Shall give it a go. Thanks again Tom.

@Tom-Elliott Sure but it’ll be tomorrow now as I’ll soon be out the office.

Updated to SVN R5769 and now getting “Cannot register host (/bin/fog.auto.reg)” when attempting to Quick Reg.
Full Registration sticks on trying to register and a blinking cursor while text flows upward off the screen.

Apache error log showing the following:

PHP Fatal error:  Call to a member function get() on string in /var/www/fog/lib/fog/host.class.php on line 373

@Quazz On doing it now. Tom posted while I was writing my post out!

Also having this issue after upgrading to Running Version 8279 - SVN Revision: 5767

Checked Apache error log and it is identically to that posted by Quazz

Opened the host(s) up in IE and it seems to have done the trick. However I did notice a load of newline slashes in the description box (possibly a bug from a previous version) which were going on forever more. I’ve deleted these out and then cleared the Chrome cache and it now works. I suspect Chrome has possibly choked on something.

Thanks for the help

Their is only 4 as our project with FOG was kind of stuck in limbo, so they’re mainly test boxes.

I can try a cache clear out to see if that makes a difference.

Just recently upgraded to 7819. However I’m finding that when I go to Host Management > List All Hosts > and then select a host, the host page loads, however it is blank and is stuck constantly loading. This then prompts a non-responsive Chrome box (see screenshot).

I’ve checked the Apache access and error logs but I can’t find anything that seems untoward.

The global settings appear to be working now that the sloppy domain pre-fix has been removed and the cert issue was cleared up. It still appears to be a bug that the extra erroneous slashes are added, but if the expected input is wrong then that is fair enough really!

Thanks for the help, much appreciated.

Brilliant. That appears to have worked!

is there then an issue with the global setting AD values? Entering each host information is fine for one or two hosts but it will be problematic for several or more?

@Tom-Elliott Gotcha. Will try now.

@Tom-Elliott I’m not sure I understand. What exactly are you asking for me to update?

Interestingly it there appears to be no attempts on logging onto the domain in the NetSetup.log file since I fixed the cert issue. Could it be getting stuck on the Product Key or something else?

Nope, no difference at all Same output as above

@ch3i I’ll give it a bash (no pun intended )

@ch3i Looks like you’re right.

I’ve checked the NetSetup.log file on the client and the reason it is failing authentication is due to the Account name containing lots of erroneous backslashes, as mentioned in my first post. Currently the account name in NetSetup.log looks like this: Account: domain\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

In the FOG.log I get the following:

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 20/11/2015 13:15 Client-Info Version: 0.9.7
 20/11/2015 13:15 HostnameChanger Running...
 20/11/2015 13:15 Middleware::Communication URL: http://192.168.1.156/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=xx:xx:xx:xx:xx:xx||00:00:00:00:00:00:00:E0&newService=1
 20/11/2015 13:15 Middleware::Communication Response: Success
 20/11/2015 13:15 Middleware::Communication URL: http://192.168.1.156/fog/service/hostname.php?moduleid=hostnamechanger&mac=xx:xx:xx:xx:xx:xx||00:00:00:00:00:00:00:E0&newService=1
 20/11/2015 13:15 Middleware::Communication Response: Success
 20/11/2015 13:15 HostnameChanger Checking Hostname
 20/11/2015 13:15 HostnameChanger Hostname is correct
 20/11/2015 13:15 HostnameChanger Activing host with product key
------------------------------------------------------------------------------

And nothing appears to happen beyond it.

I’ve tried using a different account and restarting the FOG service, however no joy and I get the same as above.

It would seem rebooting the server then issuing the following command ./installfog.sh --recreate-CA --recreate-keys and re-installing the client (with a reboot of the client in-between) has done the tick for the cert error.

Still having problems with auto-joining on AD though. I’m now getting Unknown Return Code: 2202. Is it worth creating a new forum post for?

Slight update.

The bug in question only seems to appear when you click on the host AD details, not the overall FOG AD options.

I’ve re-checked over the client logs and it would appear that has an invalid certificate. Is there any documentation on how to regenerate certs and apply them to the client as I can’t seem to find any? I suspect I’m being a bit blind…

Thanks.