Transferring all images & all host info from (1.2.0) to (1.2.0)
- FOG Version: 1.2.0
- OS: Ubuntu 12
- Service Version:
Forgive me if this has been explained, but I cannot find specific directions on how to do this. I simply want to transfer all host information and images from an old box running FOG 1.2.0 on Ubuntu 12 to a newer box running FOG 1.2.0 on Ubuntu 14. Can someone please reply with ‘clear’ instructions (or a link to ‘clear’ instructions) on how to do this? I am a FOG newbie, so I echo again the word ‘clear’.
The older export system (1.2.0 and earlier back to 1.0.0 when it was introduced) didn’t take into account the tables existing.
@Moderators important tid-bit of info there.
The older export system (1.2.0 and earlier back to 1.0.0 when it was introduced) didn’t take into account the tables existing. The way this would typically work, though, would be to simply clear out all of the tables in the fog database and apply what was being passed in.
For whatever reason, the exported backup file was not dropping the fog database when the import was being kicked off.
The fix, as we already had the original exported db, was to drop the fog database, recreate it, and let the sql file import the rest back in.
We did this via command line just to ensure all was well.
mysql -u root fog < fogdb.sql
For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
@Tom-Elliott Thanks for all of your help! Can you reply to this thread with how we (you) fixed this issue? I think it may be very helpful to anyone having this or a similar issue. Again, thanks much!!
Trying to hit you on chat.
@Tom-Elliott Correct. I’ve copied the fogdb.sql from the old server to the new one. Then I import via (FOG Configuration Page->FOG Settings->Configuration Save->Import). It says successfully completed, but nothing gets imported. The fogdb.sql is not empty; it seems full of the correct info. So I followed the instructions to manually import it and got the same results: Nothing gets imported even though no errors are returned.
@dcorpening Try importing the sql file from the GUI? (FOG Configuration Page->FOG Settings->Configuration Save->Import) You will have to download the db file you need to the system so you can import it.
@Tom-Elliott It worked! I can now log in. Thank you SO MUCH! I notice that no hosts, tftp/storage passwords, etc. are listed; Even though I’ve manually imported the fogdb.sql from the old server using “…mysql < fogdb.sql” : (Which is why I could log into the WebUI). Whether the import is done manually or via the WebUI, it seems that nothing is getting imported. The images are transferring now. So I think getting the fogdb.sql properly imported should be the last hurdle in setting up this new server. Please advise.
And for reference:
@dcorpening I see what’s happening.
Please run in mysql:
UPDATE `users` SET `uPass`=MD5('password') where `uName`='fog';
The blowfish store was only added in 1.3.x series. As you’re running on 1.2.0 to 1.2.0, the password field is stored in md5.
@Wayne-Workman Notice here that I truncate the table, verify with SELECT, and try to create the fog user with INSERT. Same results with 1 warning and not being able to log in. I hope this issue is not becoming a pain to you; however, it is certainly painful on my end after several reinstalls and many hours researching this. Any other suggestions would be greatly appreciated. Hopefully this fiasco will be a big help to others in the end once we find a fix.
@dcorpening That there are two fog accounts. I’d truncate the table and then insert a single fresh one using the previously mentioned command in the wiki. The password for it as the wiki states is
password. And this is for the web interface - just to clairify.
@Wayne-Workman What do you glean from this pic?
Wayne Workman last edited by Wayne Workman
@dcorpening the web interface doesn’t use local accounts, it’s entirely based on what’s in the DB. Select the entire table and take a look through it. These two queries should help:
SELECT * FROM users; DESCRIBE users;
@Wayne-Workman The first option of UPDATE
users… returns “Query OK, 0 rows affected (0.00 sec)”. I still cannot log in so I assume the fog user does not exist; so I try to create it with the second option command of INSERT INTO
users… This returns “Query OK, 1 row affected, 1 warning (0.00 sec)”. I still cannot log in, so I assume that the fog user was not properly created. I have triple checked all syntax and am not getting any syntax errors. How can I view the 1 warning returned by the INSERT command? Should I create the fog user at the old server CLI and transfer the fogdb.sql again?
@dcorpening You can reset the fog web user’s password with steps here:
dcorpening last edited by dcorpening
@Wayne-Workman mysql -D fog < fogdb.sql ‘seemed’ to work. The cursor was returned after about 10 seconds with no errors. When I go to the FOG WebUI to log in, I now get “Database Schema Installer/Updater”. See the uploaded pic. I rebooted the server, restarted the mysql service, etc. but still get “Database Schema Installer/Updater”. I click the <Install/Upgrade now> and it updates successfully and now correctly displays the WebUI login page. Problem is I cannot log in with any fog or root user password that I can think of; including the password that works on the server that the fogdb.sql came from. The /home/fog/fogsettings file show null for snmysqluser and snmysqlpass. There is no config.php located at /var/www/html/fog/commons/ …or in… /var/www/fog/commons/
Wayne Workman last edited by Wayne Workman
This is just a guess but, on the new server, instead of using
mysql < fogdb.sqltry to use this:
mysql -D fog < fogdb.sql
@Wayne-Workman Finally back from holiday break. Happy 2017 to everyone! Wayne, with one exception; everything, including transferring the images from the old to the new server, worked. The one issue is still importing the fogdb.sql. The last step of manually importing the fogdb.sql returns the error “ERROR 1046 (3D000) at line 22: No database selected”.
Getting me past this error should finish this project. Any help here would be greatly appreciated.