search

clarinsi / clarin-dspace

LINDAT/CLARIN digital repository based on DSpace
http://lindat.cz
BSD 3-Clause "New" or "Revised" License
0 stars 2 forks source link

Upgrade Ubuntu to 16.04 #17

Closed cyplas closed 6 years ago

cyplas commented 6 years ago

I've now upgraded on our development server from 14.04 to 16.04 and, at first glance, it has gone remarkably smoothly. Just a couple of particular notes:

  1. There were several packages where I got asked to pick between our version of a config file and the new package update one (e.g., default-ssl.conf (apache), auto.master, server.xml (tomcat)); after looking at the diff, I chose ours in each case. This and more can be found in the (automatic upgrade) log under /var/log/dist-upgrade/.

  2. For postgresql, there was a particular warning message:

    Obsolete major version 9.3
The PostgreSQL version 9.3 is obsolete, but the server or client packages are still installed. Please install the latest packages (postgresql-9.5 and postgresql-client-9.5) and upgrade the existing  clusters with pg_upgradecl\
uster (see manpage).
Please be aware that the installation of postgresql-9.5 will automatically create a default cluster 9.5/main. If you want to upgrade the 9.3/main cluster, you need to remove the already existing 9.5 cluster (pg_dropcluster --\
stop 9.5 main, see manpage for details).
The old server and client packages are no longer supported. After the existing clusters are upgraded, the postgresql-9.3 and postgresql-client-9.3 packages should be removed.
Please see /usr/share/doc/postgresql-common/README.Debian.gz for details.

    The repository seemed to work fine even before I addressed this, but I addressed it anyway, following https://gist.github.com/johanndt/6436bfad28c86b28f794 with no problems.

  3. Although I didn't notice any warning, some PHP packages were removed (this was irrelevant for clarin-dspace, but broke our wordpress installation). It seems that this is a known problem with known solution (https://mgw.dumatics.com/fix-for-php-issues-after-upgrade-to-ubuntu-16-04-1-xenial/). I followed the steps there with no problems.

The repository (and wordpress) seems to be working fine, including make deploy and make restart. However, we can't fully test shibboleth or the handle server until I repeat on the production server.

cyplas commented 6 years ago

Forgot to mention:

  1. After the upgrade, apt-get would't work: "debtags: error: unrecognized arguments: --local". Fixed this with "cd /etc/apt/apt.conf.d; mv 80debtags.dpkg-new 80debtags".
cyplas commented 6 years ago

Now successfully did the upgrade also on our production server, where there was one additional problem:

  1. There were a couple of issues with shibboleth, which prevented discojuice from working properly. One issue was with the metadata cache, where it got stuck, until we did a couple of config tweaks and restarts. A second issue was with glibc:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/shib2.load: Cannot load /usr/lib/apache2/modules/mod_shib2.so into server: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/lib/apache2/modules/mod_shib2.so)