Your message dated Wed, 1 May 2013 19:53:45 +0200 with message-id <20130501175345.GE12846@radis.cristau.org> and subject line Re: Bug#613235: release-notes: Watchdog during upgrade has caused the Debian Bug report #613235, regarding release-notes: Watchdog during upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 613235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613235 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: release-notes: Watchdog during upgrade
- From: Anders Montonen <Anders.Montonen@iki.fi>
- Date: Sun, 13 Feb 2011 18:51:58 +0200
- Message-id: <20110213165158.11142.90930.reportbug@kaiser.example.org>
Package: release-notes Severity: normal The upgrade instructions should include a section on system watchdog daemons (eg. micro-evtd). Following the current instructions means the daemon will be stopped in the middle of the upgrade when its replacement is unpacked, meaning the watchdog will be tripped a short while after. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-5-orion5x Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: Ryan Tandy <ryan@nardis.ca>, 613235-done@bugs.debian.org
- Cc: Anders Montonen <Anders.Montonen@iki.fi>
- Subject: Re: Bug#613235: release-notes: Watchdog during upgrade
- From: Julien Cristau <jcristau@debian.org>
- Date: Wed, 1 May 2013 19:53:45 +0200
- Message-id: <20130501175345.GE12846@radis.cristau.org>
- In-reply-to: <5157514A.6060107@nardis.ca>
- References: <20110213165158.11142.90930.reportbug@kaiser.example.org> <20130330185101.GA9553@mikado.tilapin.org> <CCB7310E-ECE2-46C2-9073-2B0AC4BDA429@iki.fi> <5157514A.6060107@nardis.ca>
On Sat, Mar 30, 2013 at 13:55:38 -0700, Ryan Tandy wrote: > On 13-03-30 12:15 PM, Anders Montonen wrote: > >Going by this <http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=26909> there may still be some problems with the watchdog daemon, but I don't know if it is the same problem I had (ie. the new daemon not being started right away). I have not tried upgrading to Wheezy myself yet. > > Thank you for bringing my attention to this bug. > > In micro-evtd in wheezy, the init script's "stop" action disables > the watchdog, so the box won't be killed. I had forgotten that the > version in squeeze doesn't have that behaviour. > > I guess it's too late to make that change in squeeze. I think adding > a note in the release-notes would be useful, to the effect that > users should run before upgrading: > > # stop the daemon from resetting the watchdog timer > /etc/init.d/micro-evtd stop > # disable the watchdog timer > /usr/sbin/microapl -a system_set_watchdog off > I've added the following to the "Prepare a safe environment for the upgrade" section of the wheezy release notes: +<para arch="armel"> + Users of the watchdog daemon provided by the <systemitem + role="package">micro-evtd</systemitem> package should stop the daemon and + disable the watchdog timer before the upgrade, to avoid a spurious reboot in + the middle of the upgrade process: + <screen> +# service micro-evtd stop +# /usr/sbin/microapl -a system_set_watchdog off</screen> +</para> + Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---