No Web Interface After Upgrade

[Wayne Workman]

@ArchFan I think it’s a debian 7 problem. Changes were made not too long ago that enabled fog to support Debian 8. this might be a compatibility issue.

Do you have backups of your database ? hosts?

[ArchFan]

I can get to the default apache page if that helps any. Attempting to go to the <ip>/fog/management page, it tries to redirect to the schema updater which fails to load

[ArchFan]

@Wayne-Workman Alright. I do have a backup that would probably at least get us close to the current setup. I need to virtualize it anyway, so I may just re-create the entire server from scratch and copy the files I need. Maybe if I just do a Debian 8 install, copy the .fogsettings file, postdownloadscripts, and image that’ll be a quicker job. I’ve just been doing quick images, so we have no hosts in the DB other than the VM I use to upload images

[Wayne Workman]

@ArchFan Sounds like a game plan.

Before you do that, can you verify that /var/www/fog exists still? or did debian 7 move to /var/www/html/ yet?

It might be just a simple symbolic link that could fix this… maybe.

[ArchFan]

@Wayne-Workman Here’s the contents of both directories

[Wayne Workman]

@ArchFan Yeah I think that is what happened.

First, you have a symlink that doesn’t look to be doing anything… we can remove that…

rm -rf /var/www/fog

Then you can reinstall fog using the webroot argument like this:

./installfog.sh --webroot /var/www/fog

[Malos]

Does your mysql root password have a $ in it?

[ArchFan]

@Malos No, it was just blank

[ArchFan]

I ended up just creating a VM, moving the .fogsettings, postdownloadscripts, and driver files to the new VM and then uploading an updated image. It needed virtualized anyway so I could free up the hardware for something else. Thanks for the help guys

[ArchFan]

So I’ve attempted to update to the latest git version twice (different versions) since starting over with a new VM. Unfortunately each time I update, I go back to the HTTP 500 error. I reverted to a snapshot the last time, but I’d really like to apply the latest updates. Any suggestions?

Apache logs attached[ FogApacheLog.txt

[Tom Elliott]

I’m finding this particular issue a little odd seeing as there isn’t a line number 269 in FOGCore on current.

[ArchFan]

That indeed seems odd. I’ve tried with and without the Debian updates, neither seemed to have any effect on the 500 error either. If you have any time in the near future, I can get you connected if you want to take a look. Otherwise I’ll just revert again and settle for the older version

[Tom Elliott]

@ArchFan I do want to connect but we are handling iPad roll outs to our schools most of this and next week. I would actually want to look at what is keeping line 269 present. My guess is you are seeing the old issue of non linked links running files that no longer have the specified methods associated.

[ArchFan]

@Tom-Elliott Sounds good Tom, just let me know when you’re ready and I’ll connect you. I don’t think we’re imaging anything for a while - we just deployed a few dozen replacements

[Sebastian Roth]

@ArchFan We had some weird things happening on debian systems lately. I don’t think they are all related but maybe those threads can help you figure out whats going wrong:
https://forums.fogproject.org/topic/6005/windows7-restarts-at-bootup-when-it-reaches-classpnp-sys-after-being-imaged-with-fog
https://forums.fogproject.org/topic/5993/rev-4201-blank-page-when-trying-to-install-update-database-schema

I’d suggest remove /var/www/fog again, then update to current trunk and run the installer again (not just webroot install but full).

[Tom Elliott]

Now that I have a little more foresight I believe what you are running into is a linked link that is causing issues.

Can you please run the commands:

sudo rm /var/www/fog
sudo rm /var/www/html/fog

And rerun the installer. I don’t know if you have any isos in the web folder of fog so of course backup any needed data first.

Of note, do not add a trailing slash on the file names as we want to delete the links, not the content of those links.

[Wayne Workman]

@Tom-Elliott said:

I believe what you are running into is a linked link that is causing issues.

I think for some reason several people are recently suffering from this.

[pmonstad]

I have the exact same trouble. Now I have no access to my FOG-system. My own fault as the svn is not stable, I know. Any idea how to fix this? I will try the mentioned stuff tomorrow.

[Tom Elliott]

@Wayne-Workman I’ve added code to test and remove these links if they are present.

I don’t know if it will be a solid fix for the issue but at least I think it is a step in the right direction.

[Tom Elliott]

@pmonstad whenever there is a blank screen it usually means an error for unexpected method calls or what have you. It means there is likely an error thrown in the Apache error logs so please get me some of the lines so I can better help and fix the problem.