SQL not working after update to 1.3.0 RC10
-
@maveriick Try to run the installer like this:
snmysqlhost='127.0.0.1' ./installfog.sh -y
-
Ok, So I tried that and the installer went all the way through.
But when I try to log in i get the same thing.
You guys are awesome and I look forward to getting this back up and running! -
@maveriick so, inside of
/opt/fog/.fogsettings
changesnmysqlhost=
to 127.0.0.1, save, and re-run the installer, you should be good. -
Getting the same thing.
Gonna sleep on it tonight… C-ya in the AM.
Rob -
@maveriick that’s weird. So, same thing as in the installer fails, or same thing with the web interface?
-
The installer comes to the update database Schema. Then when I go to the Fog Management page as directed I attempt to install/upgrade now and it just is stuck in that loop. If I add in the switch and arguments below it also comes to that page. It does seem very weird.
Not sure where to go next. -
@maveriick can you manually create the fog database then try the schema update? I think it’s failing due to the debug method call. So it never returns to allow the queries to run
-
Ok, Being not overly informed on SQL and databases. How do I manually create the database?
Thanks,
Rob -
@maveriick run on cli
mysql -u root
Then just run
create database fog
-
Tom,
Not sure how long this should take…
I ran this about 20 minutes ago.
Thanks,
Rob -
@maveriick enter the ; and press enter to terminate the command…
all command must have ended with ; -
Thanks,
That at least gets me a bit more…
I received an error 1007 (hy000): Can’t create database ‘fog’; database exists.
I am assuming I need to move or delete the DB? If so how do I do that? -
@maveriick
Always make a backup first. Using fog suggestion should work (cd; mysqldump --allow-keywords -x -v fog > fogbackup.sql
)
To drop a database :drop database fog;
-
@Thiago I have done the recommendation without issue. But am still looping on the Fog Management… What could I be doing wrong?
Thanks,
Rob -
@maveriick After dropped the database, did you created another one? (just like @Tom-Elliott said)
-
@Thiago Yes I did. I also rebooted and ran this again.
Still with the same issues.
Thanks,
Rob