[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SIGSEGV
From: |
Christian Hopp |
Subject: |
Re: SIGSEGV |
Date: |
Mon, 17 Feb 2003 19:10:00 +0100 (CET) |
On Mon, 17 Feb 2003, Jan-Henrik Haukeland wrote:
> Christian Hopp <address@hidden> writes:
>
> > On Mon, 17 Feb 2003, Jan-Henrik Haukeland wrote:
> >
> > >
> > > Ahh, I got a SIGSEGV when testing monit now in association with monit
> > > reload. I'll have to nail this down before any release.
> >
> > Strange I dont have a problem... only if I bombard it with too many
> > SIGHUPs at a time. Then I had a SIGSEGV and I get some "monit: No daemon
> > process found" from time to time.
>
> That's the same stuff I experienced only it happened when I did *one*
> reload (maybe you start monit from init, so it respawns before the
> problem manifests itself from userland). Anyway the problem is fixed
> (I hope) and described in the latest cvs check in. (On a side note, if
> a monit daemon dies without any log messages it's almost certainly
> because off a SIGSEGV or another crash signal)
I usually run a test monit with "./monit -v -I -c whatever-test-rc".
Christian
--
Christian Hopp email: address@hidden
Institut für Elektrische Informationstechnik fon: +49-5323-72-2113
TU Clausthal, Leibnizstr. 28, 38678 Clausthal-Zellerf. fax: +49-5323-72-3197
pgpkey: https://www.iei.tu-clausthal.de/pgp-keys/
- SIGSEGV, Jan-Henrik Haukeland, 2003/02/17
- Re: SIGSEGV,
Christian Hopp <=