UNSOLVED Upgrade from 1.2 (SVN 2868) to 1.3
- FOG Version: 1.2 (SVN 2868)
- OS: Linux Mint 13 (Ubuntu)
I’m trying to do an in place upgrade from 1.2 SVN 2868 to 1.3 stable release. So far all my attempts have failed on the “Backing up database” step. It looks like the web server portion of it is not starting up properly during the upgrade. I realize this is an old OS and SVN but I’m hoping to simplify the upgrade process as much as possible. I apologize for the lack of information, I’m the furthest thing from a Linux expert. I’ve attached log files so hopefully those will help.
@Wayne-Workman Will do. It’s been going relatively smoothly so far though so hopefully I won’t have to bug anyone. Thanks again!
Wayne Workman last edited by Wayne Workman
@Jacob-Gallant That’s the most sure path. If you need help with that, create a new thread on it and ping me in it.
Hi folks, I’m not going to waste anymore of your time. I’ve decided to build a new FOG environment and import the database into it. Lots of extra work for me but probably good to go fresh, newer OSs, etc. anyway. Thanks all for your help!
@Sebastian-Roth Hi Sebastien, there were no results for that grep. apt-get -f install ran through but didn’t seem to fix anything. I can still access the FOG web interface and login.
@Jacob-Gallant I am a bit puzzled from what you posted last. Where does this “mysterious” path come from? Maybe try one more grep:
grep -R "20090626" /etc/php5/*
Otherwise you could check if there are still some packages in an unconfigured or otherwise weird state:
apt-get -f install
Are you able to access the FOG webinterface and login?
@Wayne-Workman No problems with 1.2.0, I upgraded for 2 reasons: Windows 10 support and we had a hardware model that we couldn’t register with the kernel that had been installed with that version of FOG. I tried to manually update the kernel but I was getting “Failed to initialize disk” errors with the kernel I compiled. Rather than fight with that I thought I might as well perform the upgrade of the whole system.
What about this?
grep -R "extension_dir" /etc/php5/*
To me this seems like something was messed up while upgrading packages (see in the logs you posted first).
Wayne Workman last edited by
@Jacob-Gallant Why were you trying to update originally? Were you having problems with 1.2.0 ?
@Quazz Just getting an “Unknown instance” when I try to stop the service.
@Jacob-Gallant Can you try to manually stop the mysql service and see if that works?
@Wayne-Workman Hi Wayne,
Neither of those commands worked. However service mysql status returned that the mysql service was in a “stop/waiting” state. I tried to start it manually but it failed. Obviously the rest of those commands won’t work in the current state…
At the end of the apache error log I see:
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/mysql.so' - /usr/lib/php5/20090626/mysql.so: undefined symbol: mysqlnd_connect in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/mysqli.so' - /usr/lib/php5/20090626/mysqli.so: undefined symbol: mysqlnd_connect in Unknown on line 0 PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/pdo_mysql.so' - /usr/lib/php5/20090626/pdo_mysql.so: undefined symbol: mysqlnd_allocator in Unknown on line 0
Just a warning but well this does not sound good.
Please run the following command and let us know what you get:
grep -R "extension" /etc/php5/*
Wayne Workman last edited by
@Jacob-Gallant It can’t connect to the DB for some reason. Some troubleshooting is in order.
Check if mysql is running:
service mariadb statusor maybe
service mysqld statusNot sure with mint 13. If one doesn’t work try the other.
Try to manually get into MySQL. There’s some variations on how to do this. Try these in order:
mysql -D fog
mysql -D fog -h localhost
mysql -D fog -h 127.0.0.1
mysql -u root -D fog
If it’s password protected, try these:
mysql -D fog -u root -h localhost -p
mysql -D fog -u root -h 127.0.0.1 -p
Just see if you can manually get in somehow. And once you figure out what to use with that, we can plug those values into
/opt/fog/.fogsettingsand re-run the installer, then you’ll be in business hopefully.
I tried to upload that originally, must have missed it.
@Jacob-Gallant Please post the what you have in the apache error log on your server (/var/log/apache2/error.log)…