2015-04-27 Upgrading the homeserver to Ubuntu 12.042 years ago
And to get to a version of Ubuntu with support available I kept doing and did 'do-release-upgrade' again today on the homeserver greenblatt. Again the upgrade was running for a while. A big improvement is that the process now uses screen so I was able to attach to that running console from other sessions and answer questions. After the upgrade the reboot came, and after the reboot I noticed resolving was broken. This was traced back to the ppp0 interface for the connection to the outside world and the internal interface for services having started completely without IPv6 support. Doing an ifdown and ifup helped, but this should all start correct automatically. I noticed the new Postgresql 9.1 is already installed,
but Postgresql 8.4 is the default version available over port 5432, so I can do the pg_upgradecluster when I have time for that. Later I noticed some packages were held back. I traced this back to /etc/apt/preferences still being optimized for Ubuntu 8.04 hardy and hardy-backports. I emptied the preferences file and it all sorted itself out and now everything is up to date. This was probably the reason Postgresql 8.4 was left installed and active. After the updates above apt-get autoremove was going to delete Postgresql 8.4. And the processes that monitor for upgrades are awake, because right away the login information shows me:Welcome to Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-80-generic x86_64) * Documentation: https://help.ubuntu.com/ New release '14.04.2 LTS' available. Run 'do-release-upgrade' to upgrade to it.This time the pg_upgradecluster from 8.4 to 9.1 happened without any problems. Update:
And as usual when doing an upgrade amanda stops working. It took me a while to find out why but the username in /etc/xinetd.d/amanda was incorrect. Filed as Bug #1449228 “incorrect username in /etc/xinetd.d/amanda” : Bugs : amanda package : Ubuntu. Update 2015-04-28:
And I also had a problem with the NFS server failing. "Fixed" by modifying the /etc/init.d/nfs-kernel-server script removing:$PREFIX/bin/rpcinfo -u localhost nfs 3 >/dev/null 2>&1 || RPCMOUNTDOPTS="$RPCMOUNTDOPTS --no-nfs-version 3"Update 2015-04-29:
I enabled apt-listchanges with the option to mail the reports (and not hold apt-get dist-upgrade for me to read them) with in /etc/apt/listchanges.conf:[apt] frontend=mail email_address=root confirm=0 save_seen=/var/lib/apt/listchanges.db which=newsWhich gave me a possible answer to the nfs version problem above when I tested it:Get:1 Changelog for nfs-kernel-server (http://changelogs.ubuntu.com/changelogs/p ool/main/n/nfs-utils/nfs-utils_1.2.5-3ubuntu3.2/changelog) [107 kB] nfs-utils (1:1.2.5-3ubuntu3.2) precise; urgency=medium * Fix mount.nfs so that it falls back to v3 when ipv4 and ipv6 name resolution is present, but nfsv4 is not. present. LP: #1391662 -- Dave Chiluk ... Tue, 18 Nov 2014 10:55:28 -0600But it's also bug Bug #945651 “Wrong path to rpcinfo in NFS start script” : Bugs : nfs-utils package : Ubuntu. And maybe the portmapper package which I also changed to rpcbind.