Server 500 error after upgrading to 0.33b
-
I have not made any changes to the MySQL.class.php files.
-
yes - it’s upgrading an existing installation,
-
I don’t know how well that method will work as there’s quite a few changes to the new setup. You might try making a backup and start with a new database.
-
How will that work for all my existing hosts and images?
-
That’s still an issue in question. I have to figure out the variants between the db tables. So a simple export/import won’t work at the moment. I haven’t had time to try that out yet.
Major difference, if you’re not afraid of db inserts, is for hosts, there is no hostOS on fog 0.33 but there is on 0.32.
-
OK, I’ve gone for it and dropped the database, then re-installed.
Next issue is that half of the menu options appear chines/taiwanese
-
You have to choose the language options. Make sure en_US is chosen when logging in.
-
Doh! Schoolboy error.
Thanks so much for your help. I think I’ve a long way to go to get 0.33b up ad running to the same standard as 0.32 but if it means I can back up 64bit editions of Windows, it’s worth the graft.
-
Hey i’m getting the same error after updating from .032 to .033b. ([url]http://192.168.5.5/fog/commons/schemaupdater/index.php?redir=1[/url]) Unable to connect to Database. What are the steps that you guys followed to get everything back up and running
-
When you installed your system did you setup a password for MySQL?
Have you Commented out the my.cnf bind-address line?
Does your mysql root user have a wildcard entry to enable connections from other hosts?
-
This post is deleted! -
actually i’m not sure… kind of new to it all to be truthful. i dont believe i set up a password for sql and where do i find the my.cnf bind-address line? i dont believe it does.
-
ok it appears that i actually did set up an password for my SQL. I edited the config file and everything is now working as far as login
