Multiple errors when updating ubuntu 16.04


#1

I just updated and received a whole bunch of errors i’ve never seen before? Any idea what the problem is? Now I’m scared to updated ubuntu again to see my website down with no idea how to fix it… :sweat:

Reading package lists… Done W: GPG error: http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY F1656F24C74CD1D8 W: The repository ‘http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial InRelease’ is not signed. N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://download.opensuse.org/repositories/home:/rtCamp:/EasyEngine/xUbuntu_16.04 Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 3050AC3CD2AE6F03 W: The repository ‘http://download.opensuse.org/repositories/home:/rtCamp:/EasyEngine/xUbuntu_16.04 Release’ is not signed. N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.

I went ahead and upgraded anyway. Following errors at the end:

Setting up libmysqlclient18 (10.1.25+maria-1~xenial) … Setting up python3-update-manager (1:16.04.7) … Setting up liblxc1 (2.0.8-0ubuntu1~16.04.2) … Setting up lxc-common (2.0.8-0ubuntu1~16.04.2) … Setting up lxd (2.0.10-0ubuntu1~16.04.1) … Setting up libmariadbclient18 (10.1.25+maria-1~xenial) … Setting up mariadb-client-core-10.1 (10.1.25+maria-1~xenial) … Setting up mariadb-client-10.1 (10.1.25+maria-1~xenial) … Setting up mariadb-server-core-10.1 (10.1.25+maria-1~xenial) … Setting up mariadb-server-10.1 (10.1.25+maria-1~xenial) … Job for mariadb.service failed because the control process exited with error code. See “systemctl status mariadb.service” and “journalctl -xe” for details. invoke-rc.d: initscript mysql, action “start” failed. ● mariadb.service - MariaDB database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/mariadb.service.d └─migrated-from-my.cnf-settings.conf Active: failed (Result: exit-code) since Tue 2017-08-01 08:38:41 UTC; 4ms ago Process: 10935 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 10778 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=/usr/bin/galera_recovery; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) Process: 10770 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 10766 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 10935 (code=exited, status=1/FAILURE) Status: “MariaDB server is down”

Aug 01 08:38:38 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:38 140174038210816 [Note] InnoDB: Initializing buffer pool, size = 256.0M Aug 01 08:38:38 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:38 140174038210816 [Note] InnoDB: Completed initialization of buffer pool Aug 01 08:38:38 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:38 140174038210816 [Note] InnoDB: Highest supported file format is Barracuda. Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140174038210816 [Note] InnoDB: 128 rollback segment(s) are active. Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140174038210816 [Note] InnoDB: Waiting for purge to start Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140174038210816 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5…13307467 Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140174038210816 [Note] Plugin ‘FEEDBACK’ is disabled. Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140173106964224 [Note] InnoDB: Dumping buffer pool(s) not yet started Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140174038210816 [ERROR] Can’t create IP socket: Name or service not known Aug 01 08:38:39 ip-10-0-0-5 mysqld[10935]: 2017-08-01 8:38:39 140174038210816 [ERROR] Aborting Aug 01 08:38:41 ip-10-0-0-5 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Aug 01 08:38:41 ip-10-0-0-5 systemd[1]: Failed to start MariaDB database server. Aug 01 08:38:41 ip-10-0-0-5 systemd[1]: mariadb.service: Unit entered failed state. Aug 01 08:38:41 ip-10-0-0-5 systemd[1]: mariadb.service: Failed with result ‘exit-code’. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package mariadb-server-10.1 (–configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mariadb-server: mariadb-server depends on mariadb-server-10.1 (= 10.1.25+maria-1~xenial); however: Package mariadb-server-10.1 is not configured yet.

dpkg: error processing package mariadb-server (–configure): dependency problems - leaving unconfigured Setting up python3-distupgrade (1:16.04.22) … No apport report written because the error message indicates its a followup error from a previous failure. Setting up ubuntu-release-upgrader-core (1:16.04.22) … Setting up update-manager-core (1:16.04.7) … Processing triggers for libc-bin (2.23-0ubuntu9) … Processing triggers for initramfs-tools (0.122ubuntu8.8) … update-initramfs: Generating /boot/initrd.img-4.4.0-1026-aws W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Errors were encountered while processing: mariadb-server-10.1 mariadb-server E: Sub-process /usr/bin/dpkg returned an error code (1)

I’am using an AWS vpc with EC2, ElastiCache redis, cloudfront, and Amazon Aurora database.


#2

You should never update a running server to Ubuntu 16.04.

Instead, configure a new server from zero and migrate your sites to it.


#3

Looks like it is related to Repo Key Expired Error for EasyEngine on Ubuntu 16.04

EasyEngine needs to update a key on their end.


#4

If you absolutely must you can use sudo apt-get --allow-unauthenticated upgrade


#5

Despite the outdated key, it is never advised to upgrade from 14.04 to 16.04 on a live system.


#6