2013-05-24 As I am already working on the server, I decided to upgrade to Debian wheezy in the same go. I've never known that there is an upgrade manual in the release notes. This time I read through it first. Using script -t 2>upgrade.time -a upgrade.script to recorde the shell session for further reference was a nice hint that I found there. Apart from that, the manual is very use- ful to read in advance. I've followed it quite closely. As always, the upgrade went 90-95% smoothly, but caused some problems. That's why you need enough time afterwards to solve them. I had the following problems: 1) sslh was changed internally. Now it wanted to bind to 0.0.0.0:443, but 127.0.0.1:443 was already used by the webserver. This made sslh fail. I've decided to remove sslh completely, as it wasn't as useful to me as I had expected. 2) db4.8-util couldn't be installed because it conflicted with libdb4.8 and the like. The Debian package changelog explained that the whole db4.8 stuff is obsolete now. I've removed all of it. 3) mysql-server could not be configured. There was a change from version 5.1 to 5.5. When installing the new package, the upgrade broke. This might have been caused by an unclean shutdown of the databases before the old package was removed. However, whenever I tried to install mysql-server, it wanted to *start* the server first, which was not possible and thus failed. Even when I wanted to *remove* the package, it tried to *start* the server. I came around this problem when I worked on the real package mysql- server-5.5, not on the virtual package mysql-server. To start the server sucessfully, however, I needed to replace my modified /etc/mysql/my.cnf with the distributed config (suffix `.dpkg- dist'). Somehow I wasn't questioned which config I want. Don't know why not. Solving the mysql issue was the most annoying one. Now everything seems to be running fine again. http://marmaro.de/lue/ markus schnalke