| | 39 | == Exceptional Cases == |
| | 40 | |
| | 41 | '''Zimmerman'''. apt-get dist-upgrade proceeded to |
| | 42 | {{{ |
| | 43 | Selecting previously unselected package dmeventd. |
| | 44 | Preparing to unpack .../dmeventd_2%3a1.02.90-2.2_amd64.deb ... |
| | 45 | Unpacking dmeventd (2:1.02.90-2.2) ... |
| | 46 | Setting up init-system-helpers (1.22) ... |
| | 47 | Setting up dmeventd (2:1.02.90-2.2) ... |
| | 48 | Failed to parse message: No such device or address |
| | 49 | }}} |
| | 50 | 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. |
| | 51 | |
| | 52 | Later error: |
| | 53 | {{{ |
| | 54 | Setting up sks (1.1.5-3) ... |
| | 55 | debian-sks uid check: ok |
| | 56 | debian-sks homedir check: ok |
| | 57 | db5.3_upgrade: BDB0671 /var/lib/sks/DB/DB_CONFIG~: unrecognized file type |
| | 58 | db5.3_upgrade: DB->upgrade: /var/lib/sks/DB/DB_CONFIG~: Invalid argument |
| | 59 | dpkg: error processing package sks (--configure): |
| | 60 | subprocess installed post-installation script returned error exit status 1 |
| | 61 | Setting up ca-certificates (20141019+deb8u1) ... |
| | 62 | }}} |
| | 63 | Removed the emacs backup file, then {{{dpkg --configure -a}}}. Next error |
| | 64 | |
| | 65 | {{{ |
| | 66 | 0 zimmermann:~# dpkg --configure -a |
| | 67 | Setting up sks (1.1.5-3) ... |
| | 68 | debian-sks uid check: ok |
| | 69 | debian-sks homedir check: ok |
| | 70 | cp: error writing '/var/backups/sks/20160305-143824/DB/key': No space left on device |
| | 71 | cp: failed to extend '/var/backups/sks/20160305-143824/DB/key': No space left on device |
| | 72 | dpkg: error processing package sks (--configure): |
| | 73 | subprocess installed post-installation script returned error exit status 1 |
| | 74 | Errors were encountered while processing: |
| | 75 | sks |
| | 76 | }}} |
| | 77 | |
| | 78 | This was harder to sort out |
| | 79 | {{{ |
| | 80 | cd /var/lib/sks/DB |
| | 81 | db5.1_recover -v complained about an unrecognized file format |
| | 82 | db5.3_recover -v ran recovery successfully |
| | 83 | }}} |
| | 84 | /var/lib/sks/berkeley_db.active contained "5.1". I changed this to |
| | 85 | "5.3", since the files seem to be readable by 5.3 rather than 5.1. |
| | 86 | |
| | 87 | After that, dpkg --configure -a succeeded. |
| | 88 | |
| | 89 | |
| | 90 | '''Stallman'''. Convert postgres 9.1 -> 9.4 |
| | 91 | {{{ |
| | 92 | pg_dumpall --verbose > pg91.out |
| | 93 | |
| | 94 | # Verify roundcube databases not in 9.4 |
| | 95 | psql -p 5433 --list |
| | 96 | |
| | 97 | # load dump into 9.4 |
| | 98 | psql -p 5433 < pg91.out |
| | 99 | |
| | 100 | # check |
| | 101 | psql -p 5433 --list |
| | 102 | }}} |
| | 103 | |
| | 104 | Next, stop all postgres instances, and switch 9.4 from the alternate |
| | 105 | port to the main port. |
| | 106 | |
| | 107 | {{{ |
| | 108 | systemctl stop postgresql@9.1-main.service |
| | 109 | systemctl stop postgresql@9.4-main.service |
| | 110 | }}} |
| | 111 | |
| | 112 | Set {{{port = 5432}}} in /etc/postgresql/9.4/main/postgresql.conf |
| | 113 | |
| | 114 | {{{ |
| | 115 | systemctl start postgresql@9.4-main.service |
| | 116 | systemctl disable postgresql@9.1-main.service |
| | 117 | |
| | 118 | 0 roundcube@stallman:~$ psql -U roundcube roundcube |
| | 119 | psql (9.4.6) |
| | 120 | }}} |
| | 121 | |
| | 122 | |
| 142 | | |
| 143 | | |
| 144 | | |
| 145 | | == Exceptional Cases (aka `surprises') == |
| 146 | | |
| 147 | | '''Zimmerman'''. apt-get dist-upgrade proceeded to |
| 148 | | {{{ |
| 149 | | Selecting previously unselected package dmeventd. |
| 150 | | Preparing to unpack .../dmeventd_2%3a1.02.90-2.2_amd64.deb ... |
| 151 | | Unpacking dmeventd (2:1.02.90-2.2) ... |
| 152 | | Setting up init-system-helpers (1.22) ... |
| 153 | | Setting up dmeventd (2:1.02.90-2.2) ... |
| 154 | | Failed to parse message: No such device or address |
| 155 | | }}} |
| 156 | | 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. |
| 157 | | |
| 158 | | Later error: |
| 159 | | {{{ |
| 160 | | Setting up sks (1.1.5-3) ... |
| 161 | | debian-sks uid check: ok |
| 162 | | debian-sks homedir check: ok |
| 163 | | db5.3_upgrade: BDB0671 /var/lib/sks/DB/DB_CONFIG~: unrecognized file type |
| 164 | | db5.3_upgrade: DB->upgrade: /var/lib/sks/DB/DB_CONFIG~: Invalid argument |
| 165 | | dpkg: error processing package sks (--configure): |
| 166 | | subprocess installed post-installation script returned error exit status 1 |
| 167 | | Setting up ca-certificates (20141019+deb8u1) ... |
| 168 | | }}} |
| 169 | | Removed the emacs backup file, then {{{dpkg --configure -a}}}. Next error |
| 170 | | |
| 171 | | {{{ |
| 172 | | 0 zimmermann:~# dpkg --configure -a |
| 173 | | Setting up sks (1.1.5-3) ... |
| 174 | | debian-sks uid check: ok |
| 175 | | debian-sks homedir check: ok |
| 176 | | cp: error writing '/var/backups/sks/20160305-143824/DB/key': No space left on device |
| 177 | | cp: failed to extend '/var/backups/sks/20160305-143824/DB/key': No space left on device |
| 178 | | dpkg: error processing package sks (--configure): |
| 179 | | subprocess installed post-installation script returned error exit status 1 |
| 180 | | Errors were encountered while processing: |
| 181 | | sks |
| 182 | | }}} |
| 183 | | |
| 184 | | This was harder to sort out |
| 185 | | {{{ |
| 186 | | cd /var/lib/sks/DB |
| 187 | | db5.1_recover -v complained about an unrecognized file format |
| 188 | | db5.3_recover -v ran recovery successfully |
| 189 | | }}} |
| 190 | | /var/lib/sks/berkeley_db.active contained "5.1". I changed this to |
| 191 | | "5.3", since the files seem to be readable by 5.3 rather than 5.1. |
| 192 | | |
| 193 | | After that, dpkg --configure -a succeeded. |
| 194 | | |
| 195 | | |
| 196 | | '''Stallman'''. Convert postgres 9.1 -> 9.4 |
| 197 | | {{{ |
| 198 | | pg_dumpall --verbose > pg91.out |
| 199 | | |
| 200 | | # Verify roundcube databases not in 9.4 |
| 201 | | psql -p 5433 --list |
| 202 | | |
| 203 | | # load dump into 9.4 |
| 204 | | psql -p 5433 < pg91.out |
| 205 | | |
| 206 | | # check |
| 207 | | psql -p 5433 --list |
| 208 | | }}} |
| 209 | | |
| 210 | | Next, stop all postgres instances, and switch 9.4 from the alternate |
| 211 | | port to the main port. |
| 212 | | |
| 213 | | {{{ |
| 214 | | systemctl stop postgresql@9.1-main.service |
| 215 | | systemctl stop postgresql@9.4-main.service |
| 216 | | }}} |
| 217 | | |
| 218 | | Set {{{port = 5432}}} in /etc/postgresql/9.4/main/postgresql.conf |
| 219 | | |
| 220 | | {{{ |
| 221 | | systemctl start postgresql@9.4-main.service |
| 222 | | systemctl disable postgresql@9.1-main.service |
| 223 | | |
| 224 | | 0 roundcube@stallman:~$ psql -U roundcube roundcube |
| 225 | | psql (9.4.6) |
| 226 | | }}} |