Unable to get subsection and error: (500)
-
I’m seeing the following in the Apache error log…
[Thu May 12 15:10:39 2016] [error] [client 192.168.6.105] PHP Fatal error: Function name must be a string in /var/www/html/fog/lib/client/printerclient.class.php on line 7 [Thu May 12 15:10:13 2016] [error] [client 192.168.6.105] PHP Fatal error: Function name must be a string in /var/www/html/fog/lib/client/printerclient.class.php on line 7 [Thu May 12 15:09:56 2016] [error] [client 192.168.6.104] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 197, referer: http://fogsrvr.vanfcog.org/fog/management/index.php?node=host&sub=edit&id=138 [Thu May 12 15:01:09 2016] [error] [client 192.168.6.105] File does not exist: /var/www/html/favicon.ico, referer: http://fogsrvr/fog/project [Thu May 12 15:01:09 2016] [error] [client 192.168.6.105] File does not exist: /var/www/html/fog/project [Thu May 12 14:57:41 2016] [error] [client 192.168.6.105] PHP Fatal error: Function name must be a string in /var/www/html/fog/lib/client/printerclient.class.php on line 7 [Thu May 12 14:55:49 2016] [error] [client 192.168.6.105] PHP Fatal error: Function name must be a string in /var/www/html/fog/lib/client/printerclient.class.php on line 7 [Thu May 12 14:54:21 2016] [error] [client 192.168.6.105] PHP Fatal error: Function name must be a string in /var/www/html/fog/lib/client/printerclient.class.php on line 7
Of those errors the “PHP Fatal error: Function name must be a string in /var/www/html/fog/lib/client/printerclient.class.php on line 7” appears in the log probably a few hundred times.
-
@Curtis-Allworth Please update and try again, should work.
-
@Tom-Elliott Thank you so much! That resolved it.
-
I am getting this error too. When you say update, do you mean the server or client services?
-
@MadsMagnus If the server is giving this issue (which it is), then update the server.
-
I see nothing in my apache2 log since monday… Quite strange.
-
@MadsMagnus What do you mean?
Did you update?
-
Literally my apache2 log does not have a new post since monday… A lot has happened since monday ^^ But I probably got the FOG server running properly there.
I will snapshot my VM and give it an update.
-
@Tom-Elliott said in Unable to get subsection and error: (500):
@MadsMagnus If the server is giving this issue (which it is), then update the server.
Worked for me, Thanks.
-
Server updated to 7907 but still the same… Does the newest trunk have an updated FOGservice aswell?
Unable to get subsection
Object reference not set to an instance of an object
Unable to run module
Object reference not set to an instance of an object -
@MadsMagnus, the client hasn’t been updated yet. I verified and the latest revision (7931) sends all of the correct data to the client. 7907 should as well. More than likely there’s and Authentication section in your fog.log file which will state it failed to authenticate (probably an invalid security token). Try “Resetting Encryption Data” for the computer having this issue?
-
Not exactly sure what you mean by that.
But I do see this in the log:
Authentication ERROR: Could not get security token
Authentication ERROR: Could not find file C:\Program Files (x86)\FOG\token.dat -
Same for me
Version 7937 Debian 8
-
@MadsMagnus The “reset encryption” can be done from the host’s general menu, it’s a huge button at the top that says “reset encryption data”. You can also do this via groups using the same method.
-
This worked perfectly. Now the log just says:
“Users still logged in and enforce is disabled, delaying any further actions”
I cannot seem to find a solution to this, let alone understand what they mean by “enforce”
-
I use FOG_ENFORCE_HOST_CHANGES in the Active Directory Defaults Section.
Perhaps that …
-
Yeah maybe it will work if I am part of an AD, but the machine I am testing this on is the Windows image - so no AD for this bad boy.
-
Asking @joe-schmitt to take a second look. In the mean time, @MadsMagnus please post a newer log.
-
I just tried adding some real hosts (non VM), they are renaming just fine.