PHP Fatal error in User.class.php on line 61? Build 4910
-
Maybe my FOG installation is broken, but I get a blank screen when navigating to the FOG web interface after updating to 4910.
From apache2/error.log;
[Mon Oct 12 09:22:11.650668 2015] [:error] [pid 2947] [client 10.1.21.170:18594] PHP Fatal error: Call to a member function getSetting() on null in /var/www/html/fog/lib/fog/User.class.php on line 61, referer: (our fog URL)
Line 61 is:
$this->inactivitySessionTimeout = $this->FOGCore->getSetting('FOG_INACTIVITY_TIMEOUT');
Problem with the version or problem with me?
Thanks!
-
@Trevelyan said:
FOG_INACTIVITY_TIMEOUT
Hi, in your Fog System Settings > Login Settings what’s the value of
FOG_INACTIVITY_TIMEOUT
? -
Hi,
For me, with 4910 I can’t login, nothing happens, stays on index.php page.
With 4906 no problem -
I’m with Matthieu, updated from 48** to 4910 this morning can’t login.
-
@ch3i said:
FOG_INACTIVITY_TIMEOUT
Its set to 12 in the database but I can’t actually get to any FOG page - which is the problem…
-
@Trevelyan said:
@ch3i said:
FOG_INACTIVITY_TIMEOUT
Its set to 12 in the database but I can’t actually get to any FOG page - which is the problem…
OK, problem with the version
-
@Andy-Nicolson For those who wants to return to previous version, you can do a
svn up -r 4132
and then make install to return to git 4906 version.
Or wait for Tom resolve bug -
Mathieu,
Thank you.
-
Should be fixed in latest. Thanks for reporting. I am just trying to ensure safer/secure session handling.
-
Hey Tom,
All fixed here on 4914.
Thanks.
-
Has it broken snapins too now? Clients on the desktop say “Unknown reponse”; an exerpt is below:
12/10/2015 15:22 Middleware::Communication Unknown Response: Unity de-license#!okJOBTASKID=1760JOBCREATION=2015-10-12 15:21:17SNAPINNAME=Unity de-licenseSNAP… and so on
-
@Trevelyan I am unable to replicate the issue. It looks like, based on your system, the messages returned all as one big line. What happens if you go to: http://your.fog.ip.addr/fog/service/snapins.checkin.php?mac=MACOFHOST&newService
-
@Trevelyan Figured out the problem. There was an old debugging line added unintentionally. It has been fixed in the latest.