SVN 4860 No General Info

[Raymond Bell]

Yes i will be around Thanks

[Tom Elliott]

@Raymond-Bell I have an idea as to what’s wrong already, and I’ll verify if it is indeed the case and let you know. I think what you’re seeing is specific to the location plugin.

[Raymond Bell]

@Tom-Elliott Ok thanks just let me know. I just got a storage node at each Building ( ES, JH, HS ) is the reason i am using location.

[Raymond Bell]

@Tom-Elliott Should i disable location service? And try?

[Tom Elliott]

If you need to do work right now, then I say yes, disable it, but do not DELETE it. I don’t have a nice way to disable/enable plugins, but I think the SQL Query:
UPDATE plugins SET pState=0 WHERE pName='location'; should do the trick

[george1421]

FWIW I’m also seeing the same thing. No host management details. I upgraded this AM from 4388 to 4850 and now 4860 today. I rolled back the VM to repeat the upgrade steps with the same results.

Executing the sql command to disable the location plug has no impact on the host management details. I did confirm that the bit was changed to 0. I did reboot the server just to ensure the value wasn’t cached anywhere. Upon login I did notice the location icon is still visible in the console.

In my install I only have the location and LDAP services installed.

[george1421]

In reviewing the Apache error logs I did see this error being generated when I try to access host information.

[Tue Oct 06 15:45:37 2015] [error] [client 192.168.1.167] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/fog/lib/pages/HostManagementPage.class.php on line 403, referer: http://192.168.1.53/fog/management/index.php?node=host&sub=list

It only appears to be a problem with the host general pane, the other ones work as intended.

[Raymond Bell]

@Tom-Elliott I dont need to disable i am still able to image just can not see information.

[Tom Elliott]

@Raymond-Bell This is now fixed, please update and verify for me as well?

[Raymond Bell]

Doing it now TY

will let you know

[Raymond Bell]

@Tom-Elliott The update fixed the issue…
Thanks

[george1421]

I can also confirm that version 4866 resolved the issue.