Failed upgrade to latest 1.5.7.xxx
-
Sorry I needed the server and rolled back to a snapshot so I don’t have the log. Ill take another snapshot in a little while and run the install again.
-
@astrugatch The
masterbranch being on 1.5.8 was kind of an issue which we have pulled back now. Sorry for that. For upgrading to the next release you need to wait a little more. -
No worries. Let me know if you need someone to test. I can clone / snapshot my setup pretty quickly.
-
@astrugatch I just did a test installing 1.5.7 on Ubuntu 18.04 and then trying to pre-1.5.8 (pretty much exactly what you had before). I don’t seem to get the same issue than what you posted.
* Installing package: curl....................................Failed! (Will try later) ... * Installing package: mariadb-client..........................Failed! (Will try later) * Installing package: mariadb-server..........................Failed! (Will try later)I have a feeling that there is something really awkward with your install. Please run the following commands and post output here (take a snapshot before you run these):
dpkg -l | grep -e mariadb -e mysql -e curl dpkg -l apache2 | grep '^ii' dpkg --configure -a apt-get install -f -
I’ll check this tomorrow. There may be idiosyncrasies with my system. I’ve been upgrading in place from 1.5.0RC2 and 16.04 to the present.
-
fogadmin@fogimaging:~$ sudo dpkg -l | grep -e mariadb -e mysql -e curl [sudo] password for fogadmin: ii libcurl3:amd64 7.58.0-2ubuntu2 amd64 easy-to-use client-side URL transfer library (OpenSSL flavour) ii libcurl3-gnutls:amd64 7.58.0-2ubuntu3.8 amd64 easy-to-use client-side URL transfer library (GnuTLS flavour) ii mysql-client 5.7.29-0ubuntu0.18.04.1 all MySQL database client (metapackage depending on the latest version) ii mysql-client-5.7 5.7.29-0ubuntu0.18.04.1 amd64 MySQL database client binaries ii mysql-client-core-5.7 5.7.29-0ubuntu0.18.04.1 amd64 MySQL database core client binaries ii mysql-common 5.8+1.0.4 all MySQL database common files, e.g. /etc/mysql/my.cnf ii mysql-server 5.7.29-0ubuntu0.18.04.1 all MySQL database server (metapackage depending on the latest version) ii mysql-server-5.7 5.7.29-0ubuntu0.18.04.1 amd64 MySQL database server binaries and system database setup ii mysql-server-core-5.7 5.7.29-0ubuntu0.18.04.1 amd64 MySQL database server binaries ii php7.1-curl 7.1.30-1+ubuntu16.04.1+deb.sury.org+1 amd64 CURL module for PHP ii php7.1-mysql 7.1.30-1+ubuntu16.04.1+deb.sury.org+1 amd64 MySQL module for PHP ii python-pycurl 7.43.0.1-0.2 amd64 Python bindings to libcurl ii python3-pycurl 7.43.0.1-0.2 amd64 Python bindings to libcurl (Python 3) fogadmin@fogimaging:~$ sudo dpkg -l apache2 | grep '^ii' ii apache2 2.4.39-1+ubuntu16.04.1+deb.sury.org+1 amd64 Apache HTTP Server fogadmin@fogimaging:~$ sudo dpkg --configure -a fogadmin@fogimaging:~$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. fogadmin@fogimaging:~$ -
@astrugatch Ok, thanks for the details. I need to do more testing as your initial post definitely caught my attention. We did have some ugly issue with the 1.5.7 installer on Ubuntu and I want to make sure this is not happening again. Please be patient.
Can you please run
apt-cache policy | grep http | awk '{print $2 $3}' | sort -uand post result here as well? -
@Sebastian-Roth
No worries. I’m not in a rush to have a newer version and our windows footprint is fairly small so even if our fog install crashes and burns its not the end of the world.Here you go.
fogadmin@fogimaging:~$ apt-cache policy | grep http | awk '{print $2 $3}' | sort -u http://security.ubuntu.com/ubuntubionic-security/main http://security.ubuntu.com/ubuntubionic-security/multiverse http://security.ubuntu.com/ubuntubionic-security/restricted http://security.ubuntu.com/ubuntubionic-security/universe http://us.archive.ubuntu.com/ubuntubionic-backports/main http://us.archive.ubuntu.com/ubuntubionic-backports/universe http://us.archive.ubuntu.com/ubuntubionic/main http://us.archive.ubuntu.com/ubuntubionic/multiverse http://us.archive.ubuntu.com/ubuntubionic/restricted http://us.archive.ubuntu.com/ubuntubionic/universe http://us.archive.ubuntu.com/ubuntubionic-updates/main http://us.archive.ubuntu.com/ubuntubionic-updates/multiverse http://us.archive.ubuntu.com/ubuntubionic-updates/restricted http://us.archive.ubuntu.com/ubuntubionic-updates/universe -
@astrugatch Thanks again for the details and helping us on this. I think I’ve figured it out and pushed changes to
dev-branch. This should prevent from the issue as I see it.Would be great if you could invest 30 minutes time and do a quick upgrade test with the latest from
dev-branchin your setup. Just to make sure there isn’t something else I have missed. -
Tried dev-branch but still no dice. I think the issue is related to my current system. I’m going to spin up a new instance and migrate to that with a clean install of 18.04 and 1.5.7 and see how it behaves after that.
-
I am looking at the migration instructions in the wiki and see a mention of SSL at the top by don’t see it mentioned in the instructions (except for migrating from 1.3)
-
deb-branch works when i migrated to a clean 18.04 install. I have a feeling my upgrade from 16.04 to 18.04 left something behind that I’m not finding.
-
@astrugatch said in Failed upgrade to 1.5.8:
Tried dev-branch but still no dice.
Can you post more details like the last error logs? It might be help us to help other.
-
I still have that VM in my backups so I can take a look. Hopefully I didn’t revert it before I migrated. Do you have a particular log you would want to see? I can pull any file out of the backups.
-
@astrugatch In the directory where you run the fog installer script you have the
error_logssubdir. Please grab the files from there and post here. There might be quite a few. Grab the two with the latest time stamps. One should have a FOG version number in it’s name (that’s the one with the debug background output) and one does not have any version in the filename (plain installer output that you see on screen as well.Best if you can upload those to a fileshare and post links here.
-
I just checked and unfortunately I don’t have a snapshot post install. I had rolled back to have a working version for when I did the migration to the clean install on 18.04. If i can capture the machine and put it in a sandbox at some point I can start it back up and run the installer again. That might be a while though.
-
@astrugatch Thanks for checking. Unfortunately we are on the doorstep for a new release and it would help us immensely if we can figure this out. It might be just your install but it could also be dozens more. Though I can understand if you cannot afford the time to do this now.
-
Link sent in PM
-
@astrugatch Thanks heaps! While it’s not that simple to test I would hope that I’ve got it fixed after all.
Give it a try if you like or wait a few more days for 1.5.8 to be released.
-
Ok, turned out I had missed an important thing. So latest version in
dev-branch(1.5.7.110 as of now) should fix this.