Hi, * intrigeri <[EMAIL PROTECTED]> [2008-04-08 03:09-0400]:
> When I upgraded a lenny system from 0.30.214-6 to 0.30.215-2, all my > VServers were restarted without any warning. Yes, this is because of the postrm in 0.30.214-6 stopping the vservers. This actually has been fixed, but if you had 0.30.214-6 installed, any upgrade to a newer version would cause this behavior. That package's postrm is broken and when you upgrade to a new package, that broken postrm is executed. Sadly, I could not fix the package that you actually have installed, but instead must provide you with a new package that has the fix, but you will experience the problem when you transition to the fixed package. I can demonstrate as follows: 1. As you did, I have version 0.30.214-6 installed: # apt-cache policy util-vserver util-vserver: Installed: 0.30.214-6 Candidate: 0.30.215-2 2. I have a vserver running: # vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 44 3 8.6M 2.6M 0m00s56 0m00s44 0m02s63 etch 3. I install util-vserver version 0.30.215-1 (using snapshot.d.n), and it will stop my running vserver, just as you experienced: # apt-get install util-vserver=0.30.215-1 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: yum The following packages will be upgraded: util-vserver 1 upgraded, 0 newly installed, 0 to remove and 253 not upgraded. Need to get 513kB of archives. After this operation, 147kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! util-vserver Install these packages without verification [y/N]? y Get:1 http://snapshot.debian.net pool/util-vserver util-vserver 0.30.215-1 [513kB] Fetched 513kB in 3s (146kB/s) Preconfiguring packages ... (Reading database ... 265970 files and directories currently installed.) Preparing to replace util-vserver 0.30.214-6 (using .../util-vserver_0.30.215-1_i386.deb) ... Stopping vservers of type 'default'.... Stopping all running Linux-VServer guests... Stopping etch: done Unpacking replacement util-vserver ... Setting up util-vserver (0.30.215-1) ... Fixing visibility of /proc entries for Linux-VServer guests...done. Starting Linux-VServers in background # vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME (nothing here). 4. Now I start the vserver again so that I can demonstrate that it will not be stopped when I install 0.30.215-2: # vserver etch start Starting system log daemon: syslogd. Starting kernel log daemon: klogd. Not starting internet superserver: no services enabled. Starting OpenBSD Secure Shell server: sshd. Starting periodic command scheduler: crond. # 5. I install util-vserver=0.30.215-2, where you will see that the vserver is *not* stopped, thus the problem was actually fixed: # apt-get install util-vserver=0.30.215-2 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: yum The following packages will be upgraded: util-vserver 1 upgraded, 0 newly installed, 0 to remove and 253 not upgraded. Need to get 513kB of archives. After this operation, 0B of additional disk space will be used. Get:1 ftp://debian.csail.mit.edu sid/main util-vserver 0.30.215-2 [513kB] Fetched 513kB in 1s (407kB/s) Preconfiguring packages ... (Reading database ... 265996 files and directories currently installed.) Preparing to replace util-vserver 0.30.215-1 (using .../util-vserver_0.30.215-2_i386.deb) ... Unpacking replacement util-vserver ... Setting up util-vserver (0.30.215-2) ... Fixing visibility of /proc entries for Linux-VServer guests...done. Starting Linux-VServers in background 6. Et viola, the vserver is still running: # vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 44 3 8.6M 2.6M 0m00s10 0m00s36 2m32s36 etch Does that make sense? Micah
signature.asc
Description: Digital signature
