Changes between Version 60 and Version 61 of wheezy-jessie-upgrade

Timestamp:

Mar 5, 2016, 11:36:30 PM (10 years ago)

Author:

Steve Revilak

Comment:

--

wheezy-jessie-upgrade

@@ -36 +36 @@
 
 Here's my list of servers to upgrade:
-
-== Exceptional Cases ==
-
-'''Zimmerman'''.  apt-get dist-upgrade proceeded to
-{{{
-Selecting previously unselected package dmeventd.
-Preparing to unpack .../dmeventd_2%3a1.02.90-2.2_amd64.deb ...
-Unpacking dmeventd (2:1.02.90-2.2) ...
-Setting up init-system-helpers (1.22) ...
-Setting up dmeventd (2:1.02.90-2.2) ...
-Failed to parse message: No such device or address
-}}}
-and then hung.  Unresponsive from ssh session I used for the upgrade; wouldn't accept new ssh connections.  We ended up killing zimmermann's kvm process, restarting, and continuing the upgrade from the console.
-
-Later error:
-{{{
-Setting up sks (1.1.5-3) ...
-debian-sks uid check: ok
-debian-sks homedir check: ok
-db5.3_upgrade: BDB0671 /var/lib/sks/DB/DB_CONFIG~: unrecognized file type
-db5.3_upgrade: DB->upgrade: /var/lib/sks/DB/DB_CONFIG~: Invalid argument
-dpkg: error processing package sks (--configure):
- subprocess installed post-installation script returned error exit status 1
-Setting up ca-certificates (20141019+deb8u1) ...
-}}}
-Removed the emacs backup file, then {{{dpkg --configure -a}}}.  Next error
-
-{{{
-0 zimmermann:~# dpkg --configure -a
-Setting up sks (1.1.5-3) ...
-debian-sks uid check: ok
-debian-sks homedir check: ok
-cp: error writing '/var/backups/sks/20160305-143824/DB/key': No space left on device
-cp: failed to extend '/var/backups/sks/20160305-143824/DB/key': No space left on device
-dpkg: error processing package sks (--configure):
- subprocess installed post-installation script returned error exit status 1
-Errors were encountered while processing:
- sks
-}}}
-
-This was harder to sort out
-{{{
-cd /var/lib/sks/DB
-db5.1_recover -v complained about an unrecognized file format
-db5.3_recover -v ran recovery successfully
-}}}
-/var/lib/sks/berkeley_db.active contained "5.1".  I changed this to
-"5.3", since the files seem to be readable by 5.3 rather than 5.1.
-
-After that, dpkg --configure -a succeeded.
-
-
-'''Stallman'''.  Convert postgres 9.1 -> 9.4
-{{{
-pg_dumpall --verbose > pg91.out
-
-# Verify roundcube databases not in 9.4
-psql -p 5433 --list
-
-# load dump into 9.4
-psql -p 5433 < pg91.out
-
-# check
-psql -p 5433 --list
-}}}
-
-Next, stop all postgres instances, and switch 9.4 from the alternate
-port to the main port.
-
-{{{
-systemctl stop postgresql@9.1-main.service
-systemctl stop postgresql@9.4-main.service
-}}}
-
-Set {{{port = 5432}}} in /etc/postgresql/9.4/main/postgresql.conf
-
-{{{
-systemctl start postgresql@9.4-main.service
-systemctl disable postgresql@9.1-main.service
-
-0 roundcube@stallman:~$ psql -U roundcube roundcube
-psql (9.4.6)
-}}}
 
 
@@ -224 +141 @@
 negri:wheezy
 }}}
+
+
+== Exceptional Cases ==
+
+'''Zimmerman'''.  apt-get dist-upgrade proceeded to
+{{{
+Selecting previously unselected package dmeventd.
+Preparing to unpack .../dmeventd_2%3a1.02.90-2.2_amd64.deb ...
+Unpacking dmeventd (2:1.02.90-2.2) ...
+Setting up init-system-helpers (1.22) ...
+Setting up dmeventd (2:1.02.90-2.2) ...
+Failed to parse message: No such device or address
+}}}
+and then hung.  Unresponsive from ssh session I used for the upgrade; wouldn't accept new ssh connections.  We ended up killing zimmermann's kvm process, restarting, and continuing the upgrade from the console.
+
+Later error:
+{{{
+Setting up sks (1.1.5-3) ...
+debian-sks uid check: ok
+debian-sks homedir check: ok
+db5.3_upgrade: BDB0671 /var/lib/sks/DB/DB_CONFIG~: unrecognized file type
+db5.3_upgrade: DB->upgrade: /var/lib/sks/DB/DB_CONFIG~: Invalid argument
+dpkg: error processing package sks (--configure):
+ subprocess installed post-installation script returned error exit status 1
+Setting up ca-certificates (20141019+deb8u1) ...
+}}}
+Removed the emacs backup file, then {{{dpkg --configure -a}}}.  Next error
+
+{{{
+0 zimmermann:~# dpkg --configure -a
+Setting up sks (1.1.5-3) ...
+debian-sks uid check: ok
+debian-sks homedir check: ok
+cp: error writing '/var/backups/sks/20160305-143824/DB/key': No space left on device
+cp: failed to extend '/var/backups/sks/20160305-143824/DB/key': No space left on device
+dpkg: error processing package sks (--configure):
+ subprocess installed post-installation script returned error exit status 1
+Errors were encountered while processing:
+ sks
+}}}
+
+This was harder to sort out
+{{{
+cd /var/lib/sks/DB
+db5.1_recover -v complained about an unrecognized file format
+db5.3_recover -v ran recovery successfully
+}}}
+/var/lib/sks/berkeley_db.active contained "5.1".  I changed this to
+"5.3", since the files seem to be readable by 5.3 rather than 5.1.
+
+After that, dpkg --configure -a succeeded.
+
+
+'''Stallman'''.  Convert postgres 9.1 -> 9.4
+{{{
+pg_dumpall --verbose > pg91.out
+
+# Verify roundcube databases not in 9.4
+psql -p 5433 --list
+
+# load dump into 9.4
+psql -p 5433 < pg91.out
+
+# check
+psql -p 5433 --list
+}}}
+
+Next, stop all postgres instances, and switch 9.4 from the alternate
+port to the main port.
+
+{{{
+systemctl stop postgresql@9.1-main.service
+systemctl stop postgresql@9.4-main.service
+}}}
+
+Set {{{port = 5432}}} in /etc/postgresql/9.4/main/postgresql.conf
+
+{{{
+systemctl start postgresql@9.4-main.service
+systemctl disable postgresql@9.1-main.service
+
+0 roundcube@stallman:~$ psql -U roundcube roundcube
+psql (9.4.6)
+}}}
+