latest SVN - 09.24.15
-
Ok, maybe it’s me but I’m not sure why after updating to latest SVN 4055 (even though fog logo is showing build 4752), my web interface is all messed up. I did press the update schema button on the webpage before hitting enter in SSH, so not sure why this happened. It’s the same for all browsers. Anyone else having this issue?
http://postimg.org/image/yt8p4r509/
http://postimg.org/image/x8f2s4tf7/
Help please?
-
@hmoobgolian Have you try to display the web page in private mode, maybe a cache problem ?
-
Nope, tried in private browsing mode and same results. I also tried in three different browsers too (IE, FF, Chrome).
-
@hmoobgolian Hmm…Looks like something funny happened. Can you restore your pre-upgrade backup and upgrade using the following command?
./installfog.sh -y
This will auto update the schema and take the “human” interaction out.
-
@Marcus-Allen Sorry for sounding like a noob, but how do I restore my pre-upgrade configs? I hope it keeps all revisions of the old configs as I was stupid enough to run the same svn upgrade twice, thinking I did something wrong the first time. If it does automatically save old the old configs where would the path be? I see some files under /home/fog_web_4752.BACKUP? Not sure where they originally came from though.
-
@hmoobgolian There’s been talk among the @Developers about automatically backing up the database at each installation… I’m not sure if that’s been implemented yet or not.
-
@Wayne-Workman It has not been implemented yet.
-
@hmoobgolian I meant restoring it from your backup that YOU took before upgrading. If you didn’t do that, then unfortunately you cant go back.
-
Thanks all. I ended up uninstalling (using wiki) and reinstalling the latest SVN to fix the problem. Question though, what would be the correct backup procedure? Can anyone point me in the right direction?
-
@hmoobgolian The important stuff is outlined at the bottom here: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
-
I have added better backup code that now stores a backup of the database. With that it seems there was a problem with Debian based systems in some cases where the link between /var/www/fog/ and /var/www/html/fog.
I’m fairly sure I’ve traced that down as well but I don’t feel it’s a significant enough issue to keep this open.