Server

• FOG Version: 1.2.0
• OS: Ubuntu 14.04

Client

• Service Version:
• OS:

Description

I am testing the 1.3.0 upgrade on a test FOG server before upgrading the production FOG server. i have a clean test FOG 1.2.0 installation on Ubuntu 14.04. This test 1.2.0 installation works as expected. i am following the instructions on https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk to upgrade. The first command “sudo apt-get…” works fine but I am getting the error “fatal: unable to access…” on the “git clone https://github.com…” command. See the attached png files for details. Please advise.

@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!!

@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.

@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.

@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.

@Wayne-Workman What do you glean from this pic?

@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?

@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 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.

@Wayne-Workman the export file is not empty. It appears to have all of the necessary information in it. I see the old server ip address, tftpd password, etc. in the file. BTW, I don’t think this matters, but the old server is running on Ubuntu 14 (not version 12 as I previously reported). So both boxes are running Ubuntu 14.