Fog 1.1.2 corrupts SQL database
-
How does it “corrupt” the database?
-
Please go here to see the report I saved as pdf
[url]http://www.moelleraerospace.com/Fog 112 Corrupt DB.pdf[/url]
-
What version of Fog did you upgrade from?
-
Your report is NOT a corruption of the database.
Your report indicates to me that the mysql service is not running or not setup correctly.
[code]service mysql restart[/code] Try again.
-
I upgraded from 1.1.1 I will try the restart command you suggest Tom. It looked corrupt in that report, didn’t realize it simply was not running.
-
[quote=“Oscar Hilliker, post: 32542, member: 24172”]I upgraded from 1.1.1 I will try the restart command you suggest Tom. It looked corrupt in that report, didn’t realize it simply was not running.[/quote]
Tried [FONT=Consolas]service mysql restart and no luck starting it[/FONT]
-
Can you, possibly, provide more information.
-
Here is the installation log, I don’t know how else to explain it. Regardless of starting or retrying the upgrade the fog UI continues to report the
[SIZE=6][B][FONT=Ubuntu][CENTER][SIZE=32px][COLOR=#666666]Database Schema Installer / Updater[/COLOR][/SIZE][/CENTER][/FONT][/B][/SIZE][FONT=Ubuntu][COLOR=#555555]Update/Install Failed![/COLOR][/FONT]
[url=“/_imported_xf_attachments/1/1123_foginstall.txt?:”]foginstall.txt[/url]
-
When you initially install FOG, did you set a password for the root mysql user?
If so, can you edit:
/var/www/fog/lib/fog/Config.class.php under db_settings make sure the right information is entered. -
no password is set. The odd thing is when I go and reinstall the 1.1.1 the SQL database is fine. Then I try and upgrade to 1.1.2 and it says the SQL schema installer/updater fails .
-
Did you check the Config.class.php file?
I’ll be willing to bet that, then, there is a password set on for the root user when there shouldn’t be. Have you read throughout the forums specifically with this issue?
-
I fixed the installer which during your upgrade looks like it broke it’s only because it’s now functioning properly that you were seeing the issues
-
I checked the Config.class.php file and nothing was in it. Anyways I will stop bothering you with this and use 1.1.1 for now.
-
[quote=“Oscar Hilliker, post: 32627, member: 24172”]I checked the Config.class.php file and nothing was in it. Anyways I will stop bothering you with this and use 1.1.1 for now.[/quote]
I don’t mind being bothered with it.
What do you mean nothing was in it? The file didn’t exist?
-
What I mean is the actual Config.class.php file had nothing in it. However after digging around I found a fog prev folder and it had the Config.class.php file and there is code in it. The odd thing is…there is a password not set by us, it has always been blank. I am not sure how it got there or changed. I will make another attempt at the install and report what happens.
-
Hi,
I believe that the SQL service crashing or timing out causes this (database schema update loop) - we’ve seen it too and it is painful.This link from Tom seems to fix it, especially the bottom section:
[url]https://github.com/mastacontrola/fogproject/issues/1[/url]
Cheers,
D.L. -
Tried Rhythmtone’s website and did all the suggestions then did a Re-try of 1.1.2 and it (SQL) failed, I saw some things about Fog 1.2.0 so I will try that as soon as I can get access to Ubuntu again.
-
Hi Guys,
I had this issue too when I upgraded. The /var/www/fog/lib/fog/Config.class.php had a password in the root user for SQL.
On Ubuntu boxes type sudo gedit /var/www/fog/lib/fog/Config.class.php from a terminal will open the correct file. Check if there is a password set for root, if so remove it leaving just the single quote marks (i.e. empty string). Re-link to Fog via browser and the schema updater should work. Did for me anyway…
This issue only seems to have occurred since 1.1.2 was released. Didn’t have any problems upgrading to 1.1.1.
-
Dear Tom,
don’t really know if my problems a right placed here but i try.
I tested the fog 0.33b in the past. while the test you guys released the 1.0.0 Version and later 1.0.1. With 1.0.1 everything was fine, so my Boss asked me if we can upgrade the FoG 0.32 of our customers. So i tested it and installed it with the SVN method. I upgraded both (a new 0.32 and my 1.01) to 1.1.2 and now it runs absolutely instable. Here some Problems i got:- MySQL Database was corrpted. Had to edit vi /opt/fog/.fogsettings and vi /var/www/fog/lib/fog/Config.class.php and it worked.
- I did an Imageupload from a Fujitsu Esprimo P420 with the 3.14 32-bit kernel. It Uploaded with 360MB/min (while an HP ProDesk 400 GI uploaded with 1 GB/min) but it uploaded it. The i used Sysprep to kill the SID and to create a new blank Image again with the 3.14 32-bit kernel and nothig. This is what i’ve got
-
esas2r: driver will not be loaded because no ATTO esas2r devices were found -
request _module: runaway loop modprobe binfmt-464c -
Starting init: /sbin/init exists but couldn’t’ execute it (error -8) -
request _module: runaway loop modprobe binfmt-464c -
Starting init: /bin/sh exists but couldn’t’ execute it (error -8) -
Kernel_panic – not syncing; No working init found. Try passing init=option to kernel. See linux documentation/init.txt for guidance
so i installed your unofficial 3.15 Kernel 32 bit. same Problem here till i renamed bzImage32 to bzImage and init_32.xz to init.xz
worked.
3) I created a Downloadtask with autoshutdown after deploy. As i started working this morning i saw that the Apache Server crashed and with him my Ubuntu 12.04 LTS and corrupted the deployed Image, so i had to restart the deployment.I dont know what’s happenig. I like the FoG Server but with all this Problems i just cant use it or upgrade the existing in customers infrastruktur. Please help.
Greetings from GermanyAndy
-
I noticed that in the config.class.php file in 1.1.2 there is a password. However the config.class.php in 1.1.1 don’t have a password since we didn’t use one. Also during the 1.1.1 install it ask did you leave password blank?. 1.1.2 doesn’t ask that. It looks like the config.class.php file had the password left in by the developers. However still after making it an empty password 1.1.2 still fails to install. I will wait for an update to fog, looks like they are working on 1.2.0
