No Web Interface After Upgrade

[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.

[Sebastian Roth]

You should find the log file in /var/log/apache2/error.log on your FOG server…

[Tom Elliott]

@Sebastian-Roth I believe I found the issue. It wasn’t, per say, a problem, but it was/is.

I’ve done some rewriting to hopefully thwart this problem now. Hopefully I’ve made the DB stuff MUCH more stable as I don’t know what/why there were continuous problems. What I did find out is that INSERT/UPDATE/DELETE statements do NOT return rows of data, this (I hope/believe) was the problem of 0 ID’s being entered into the DB, as well as invalid hosts being added.

I am hoping that things will be better, for all.

[scheffman]

This post is deleted!