From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/843 Path: news.gmane.org!not-for-mail From: Gerrit Pape Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Deciphering error message Date: Fri, 12 Aug 2005 17:15:33 +0000 Message-ID: <20050812171424.5611.qmail@3cfaf07dca23e2.315fe32.mid.smarden.org> References: <1123620273.13774.63.camel@localhost.localdomain> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1123867125 25706 80.91.229.2 (12 Aug 2005 17:18:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 12 Aug 2005 17:18:45 +0000 (UTC) Original-X-From: supervision-return-1079-gcsg-supervision=m.gmane.org@list.skarnet.org Fri Aug 12 19:18:45 2005 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1E3d9Y-0004ov-Pd for gcsg-supervision@gmane.org; Fri, 12 Aug 2005 19:17:08 +0200 Original-Received: (qmail 9268 invoked by uid 76); 12 Aug 2005 17:17:28 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 9238 invoked from network); 12 Aug 2005 17:15:47 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <1123620273.13774.63.camel@localhost.localdomain> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:843 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:843 On Wed, Aug 10, 2005 at 08:44:33AM +1200, Paul Dorman wrote: > I have a test machine (running inside a Xen VM) and have installed the > runit package for sarge to see how everything might look. I have > an /etc/runit directory, where a getty-5 example directory was created > with the following structure: > > sysadmin:/etc/runit# ls -l getty-5/ > total 8 > -rwxr-xr-x 1 root root 31 2005-03-26 08:47 finish > -rwxr-xr-x 1 root root 44 2005-03-26 08:47 run > lrwxrwxrwx 1 root root 16 2005-08-09 15:21 supervise > -> /var/run/getty-5 The symlink in /var/run/ is just for convenience in Debian, to have /etc/ possibly mount read-only. runsv creates the ./supervise/ directory automatically, also if it's a dangling symlink. > I created a symlink to the getty-5 directory in /var/service, and I can > see the following in /var/run/getty-5/: Yes, but it shouldn't interest you that much, this directory is meant to be used by the runit programs. > I copied the structure of the /etc/runit/getty-5 and modified it to > start apache2, and noted that there is an empty /var/run/apache2 > directory which I have linked to /etc/runit/apache2/supervise. > > Apache is running, and I note that it continues to run when I kill -9 > the Apache processes, so it looks like Apache is running under runit's > supervision. Great! > > The issue I now have is that I see this unhelpful line in my process > list (all on one line): > > root 11332 0.0 0.0 88 28 ? Ss 08:29 0:00 > runsvdir /var/service log: lock supervise/lock: temporary failure?runsv > apache2: fatal: unable to lock supervise/lock: temporary failure?runsv > getty-5: fatal: unable to lock supervise/lock: temporary failure?runsv > apache2: fatal: unable to lock supervise/lock: temporary failure?runsv > getty-5: fatal: unable to lock supervise/lock: temporary failure?runsv > apache2: fatal: unable to lock supervise/lock: temporary failure? > Could someone please tell me what this message means? Is there something > I need to do to make it go away? If it's not a real error, it sure looks > like one! It looks like there're already runsv processes running in /var/service/getty-5/ and /var/service/apache2/, and runsvdir tries to start up new ones; tell the currently running runsv processes to exit so that runsvdir can start up and monitor the supervisors, this may fix the problem the log shows. # runsvctrl exit /service/getty-5/ /service/apache2/ What you see in the process listing is the 'last resort' readproctitle log of runsvdir, it shows messages written to stderr by the ./run and ./finish scripts or service daemons. runsvdir will write a dot at the and of this log every 15 minutes. HTH, Gerrit.