blank page on installing/updating fog schema
-
Tom Elliot kindly helped me out with an issue with the latest git installer where it was firing a continual message:
Sorry, answer not recognized.This was resolved and installer now completes however when clicking on the install/upgrade schema link in a browser it navigates to http://my-fogserver-ip/fog/management/index.php?node=schemaupdater but sits at a blank page.
has anyone else encountered similar? Might be something simple like a syntax error in installfog.sh file or similar.
cheers. Kiweegie
-
how was the previous error resolved?
-
I too am having the same error of blank screen on schema update page with the latest trunk. on Ubuntu 14.04.
-
@Wayne-Workman Hi Wayne, Tom logged on remotely to my fog server to inspect the installfog.sh file and found a syntactical error within. I believe it was along the lines of looking for the Linux version calling /etc/*-release or similar and while my machine is running Centos 6.7 and returns output as follows:
CentOS release 6.7 (Final) CentOS release 6.7 (Final) CentOS release 6.7 (Final)The code was transposing or omitting parts of that output so was failing at that point. Tom corrected whatever was wrong using sed. I didn’t see the exact part which was edited I’m afraid.
regards, Kiweegie.
-
I bit the bullet and reinstalled from scratch, still using Centos but ensuring iptables and selinux were disabled before anything else. Used git rather than svn this time and now the installer has completed and I’ve been able to update schema.
Not sure where the issue was however to avoid the extra noise, please mark this one as resolved.
regards Kiweegie.
-
@Kiweegie said:
Used git rather than svn this time and now the installer has completed and I’ve been able to update schema.
For future readers - both SVN and GIT are equally valid methods for upgrading to developmental versions of FOG Trunk. We have many methods because services can go down for maintenance, they can come under dDOS attack, and of course they can fail too. When SourceForge went down for over a week, we were all happy that GitHub was still fine. I personally favor SVN simply for the numerical revision numbers and simplicity of moving to a very specific revision. This is much more difficult to do using GIT.
-
I just updated to the latest svn version 3981 too, in an attempt to resolve a fog pxe boot issue. And I’m also getting the same blank screen when attempting to update the schema.
Looking in the http error log I see the following error:
PHP Fatal error: Call to a member function get() on boolean in /var/www/html/fog/lib/plugins/accesscontrol/hooks/RemoveUpload.hook.php on line 28 -
@george1421 said:
I just updated to the latest svn version 3981 too, in an attempt to resolve a fog pxe boot issue. And I’m also getting the same blank screen when attempting to update the schema.
Looking in the http error log I see the following error:
PHP Fatal error: Call to a member function get() on boolean in /var/www/html/fog/lib/plugins/accesscontrol/hooks/RemoveUpload.hook.php on line 28What version of Linux? What version of fog did you update from?
-
Sorry I was short on the details.
Centos 6.7
While I don’t have the SVN number I upgraded from, the fog login console graphic had 4388 in the graphic. I can estimate (pretty close) the last svn update was done on 11-Aug-15 -
Bump
Any idea on how we can solve this issue? We are unable to login or even interface with the software from the FOG PXE menus since they interact with PHP. We get this error in the apache error log if we try to interact with the web interface or via the PXE menus:
PHP Fatal error: Call to a member function get() on boolean in /var/www/html/fog/lib/plugins/accesscontrol/hooks/RemoveUpload.hook.php on line 28
-
@george1421 Try updating. I don’t know if it will work, but I know you’re getting the issue, and I hope the latest will fix the problem.
-
Thank you for responding Tom. I just ran the svn update and attempted to reinstall the update. I got the same blank page for schema update and error message in the apache error log. So no luck here.
Right now we are unable to deploy new client machines. So after cloning this vm, I’m going to roll back the image to before the attempted upgrade. I did find the issue which was the trigger that caused me to attempt the upgrade. After I get the vm restored and fix the other issue, we’re all good.
If you want me to test anything additional I’ll keep the broken vm for a while.
-
@george1421 I don’t think it’s specific to the VM at all. It would seem, to me, that you are using the accesscontrol plugin? I say this because that’s what the error is pointing it. It’s having a hard time finding the FOGUser variable. Would you be willing to disable the accesscontrol plugin?
I’m almost sure, though, that something isn’t right with the update. What is the version displaying in the cloud for your FOG installation?
-
Yes the access control plugin is installed but I haven’t used it/changed from the default settings yet.
Is there a way to externally disable this plugin? I’m unable to get the management interface to display at all. Every time I call up the management interface it tries to access the schema update and I end up with the blank page.
-
I have the vm restored to the previous state and I’m able to login with version 4388 on the cloud. This vm has the access control, ldap and location plugins installed.
On the vm that was cloned, I renamed the folders for access control and ldap then restarted the httpd service. On this vm I’m now able to reach the schema update page. After the schema update was updated the version number on the cloud is 4652.
After I was able to login I removed the plugins access control and ldap and restarted httpd. I was able to login OK, so I added back in ldap, access control and restarted http. This time on the login page I noticed (as with version 4388) the estimated fog sites and latest version values weren’t displayed only the rotating circles. I was able to login OK. I then removed the ldap plugin again. At the login page the estimated sites just showed the rotating circles. And finally I logged in and removed the access control plugin. Now at the login page I get the values of 4199 and version 1.2.0 (?? since I though this was 1.3.0). I added back in the ldap plugin without issue.
So you guess that it was the access control modules is spot on. I’ll wait a day or two so we can get the images deployed on the production FOG server then attempt to upgrade that one again.
