Fog Trunk Git 7645 update fails at SQL

[Tom Elliott]

@fry_p The sudo yes | installfog.sh isn’t necessary. You can just pass it the -y option now. So it could be ${PWD}/installfog.sh -y

I don’t understand why all the work though.

The files look like they should be updated, but if your cloud is still showing 7645 while the actual version is now 7671, it would seem something somewhere isn’t working. Maybe you edited one of the files and the svn checkout isn’t completing updating because of that issue?

[fry_p]

@Tom-Elliott Thanks for the tip. I only have a script so it can run automatically at 3 am every morning to stay up to date. Even without using the script I am failing at the same point. Would apache logs help? I don’t touch anything outside the script when it comes to updating.

[fry_p]

@Tom-Elliott This is what I’m getting when I manually try to update mysql-server:

Fogadmin@FOGTEST:~$ sudo apt-get install mysql-server
[sudo] password for fogadmin: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mysql-server : Depends: mysql-server-5.5 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

This may be an Ubuntu issue and not Fog I’m thinking?

[Tom Elliott]

@fry_p I’d agree but what happens if you run sudo apt-get dist-upgrade --force

[fry_p]

@Tom-Elliott This is what I get, syntax I think

fogadmin@FOGTEST:~$ sudo apt-get dist-upgrade --force
E: Command line option --force is not understood
fogadmin@FOGTEST:~$ 

Without --force

The following packages were automatically installed and are no longer required:
  liblua5.1-0 libntdb1 linux-headers-4.2.0-27 linux-headers-4.2.0-27-generic
  linux-image-4.2.0-27-generic linux-image-extra-4.2.0-27-generic python-ntdb
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[Sebastian Roth]

@fry_p said:

mysql-server : Depends: mysql-server-5.5 but it is not going to be installed

Guess you somehow managed to install a later version of the mysql client package which is blocking the mysql server version 5.5 now. Please try this:

sudo apt-get purge mysql-client-core-5.6
sudo apt-get autoremove
sudo apt-get autoclean
sudo apt-get install mysql-client-core-5.5
sudo apt-get install mysql-server

[fry_p]

@Sebastian-Roth I got this after entering the 1st command (purge):

fogadmin@FOGTEST:~$ sudo apt-get purge mysql-client-core-5.6
[sudo] password for fogadmin: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'mysql-client-core-5.6' is not installed, so not removed

I tried the rest of the commands and they seemed to go through.
I somehow really borked this but I didn’t do anything out of the ordinary. I just ran the script and it failed at SQL again.

[Tom Elliott]

@fry_p Can you try:

sudo apt-get purge mysql-server* mysql-client*

It will remove all database application software, but the db should remain under /var/lib/mysql.

[Sebastian Roth]

dpkg -l | grep -e mysql -e maria …?

[fry_p]

@Sebastian-Roth I ran

sudo apt-get purge mysql-server* mysql-client*

at Tom’s suggestion then ran

sudo apt-get autoremove

Ran my script once again and it worked, I’m now on 7695.

Thanks guys!
(P.S. If anyone is interested in my script, I just took a script I found and modified it to my liking and use cron to run it every night)

[Sebastian Roth]

@fry_p Great to hear that you got things fixed and are back up running!

Personally I am not that fond of the idea of automatically upgrading every night. FOG trunk is under development and quite often we break things. It’s great for us as you will always be the first to find an issue and post in the forums. But you might find yourself being annoyed by this as well. Don’t get me wrong. You are more than welcome and we really appreciate people testing the very latest!!! I just hope you don’t get frustrated.

You’ll get to know FOG and how to debug and fix things very fast if you are going this way - that’s for sure. So there is a great opportunity in keeping up with the latest version as well. As I said most welcome!

[fry_p]

@Sebastian-Roth For the sake of downtime, I am probably going to slow down the update rate, but I do enjoy helping the evolution of FOG. I was properly warned of the risks before I moved to Trunk, but being on the forefront is pretty cool. I guess I could be considered a tester of sorts. The performance jump from 1.2 to Trunk is also astounding. I am getting insane upload and download speeds without having changed any network equipment! Plus, my knowledge of Linux prior to being in charge of my FOG installation was 0. Now I can cruise through basic terminal work and scripting. Good Stuff!

[Sebastian Roth]

@fry_p said:

I guess I could be considered a tester of sorts.

You definitely are. @Moderators Can anyone please tag him as a tester!

The performance jump from 1.2 to Trunk is also astounding. I am getting insane upload and download speeds without having changed any network equipment!

That’s kind of odd from my point of view as the tools used to do the actual up- and download (udp-sender for multicast download and NFS for upload and unicast download) haven’t changed much in a while!

Plus, my knowledge of Linux prior to being in charge of my FOG installation was 0. Now I can cruise through basic terminal work and scripting. Good Stuff!

Absolutely great. I think FOG has pushed quite a few people to look into linux and get their hands dirty. That’s amazing and I love to see it!

[Tom Elliott]

@Sebastian-Roth Added to testers.

[Junkhacker]

@Sebastian-Roth

That’s kind of odd from my point of view as the tools used to do the actual up- and download (udp-sender for multicast download and NFS for upload and unicast download) haven’t changed much in a while!

we’ve made changes to how compression/decompression is handled to better utilize the processing power available