Re: error on logging and how to correctly implement svlogd?

From: Thomas Lau <tlau_at_tetrioncapital.com>
Date: Tue, 21 Jun 2016 09:01:49 +0800

Hi,

Thanks for replying. I don't use symlink, instead I put everything directly
on /etc/service/test, then sv start test

On Tue, Jun 21, 2016 at 8:52 AM, Guillermo <gdiazhartusch_at_gmail.com> wrote:

> 2016-06-20 7:51 GMT-03:00 Thomas Lau:
> >
> > runsv test: fatal: unable to lock supervise/lock: temporary failure
> > [...]
> > What exactly is wrong here?
>
> The runsv program sets a lock on the 'supervise/lock' file of the
> supervised process' service directory ('test' in this case). To make
> sure that no other runsv process is already running on that directory,
> I believe. That message means that runsv failed to set that lock (IIUC
> a non-blocking flock() / lockf() call failing with EAGAIN /
> EWOULDBLOCK). However, the information provided is not enough to tell
> why, unfortunately. You don't say how the 'test' service is launched;
> do you have a symlink to its servicedir in /etc/service?
>
> G.
>



-- 
Thomas Lau
Director of Infrastructure
Tetrion Capital Limited
Direct: +852-3976-8903
Mobile: +852-9323-9670
Address: Suite 2716, Two IFC, Central, Hong Kong
Received on Tue Jun 21 2016 - 01:01:49 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC