[prev in list] [next in list] [prev in thread] [next in thread] 

List:       osiris
Subject:    Re: [osiris] Scheduled scans stop unexpectedly?
From:       "Alexei Roudnev" <Alexei_Roudnev () exigengroup ! com>
Date:       2004-05-04 19:41:41
Message-ID: 01fe01c4320f$d2d725b0$980ea8c0 () exigengroup ! com
[Download RAW message or body]

Btw - when I configured our environment, I predicted such possibility and
set up 1 host to send logs ALWAYS (even on the good scan);
as a result, we have an easy sanity check - if I do not see daily message
about this host, something is wrong.

(But I never saw such problem in Osiris 2.4.2, except I have strange delays
in some reports - looks as scheduler do not start scan
every day on a few /very few/ hosts).



>
> On May 4, 2004, at 4:19 AM, Laurie Voss wrote:
>
> > Hi all -
> >
> > We've been running Osiris for a few weeks now, monitoring about 26
> > mixed-OS
> > machines (Solaris/Red Hat/Win2k) and have generally had no problems.
> > Over
> > this weekend however, scanning stopped across all our machines (we had
> > disabled "notify on scan failure" unfortunately...). There was no
> > notification in the logs of any failure of osirismd (we've since turned
> > logging up to debug level in case it happens again) and the osirismd
> > process
> > was still running when we got in this morning, and started manual
> > scanning
> > without any kind of complaint -- it just seems the automatic scans
> > didn't
> > happen, without any explanation as to why.
>
> Is the scheduler process still running?  There should always be at
> least two osirismd processes running.
>
> > We're running 4.0.0-beta across the board (-release wasn't available
> > when we
> > started), is this just a bug in the beta or some other kind of
> > problem? (I'd
> > rather not upgrade 26 machines for no reason!) Since scans stopped
> > across
> > all the machines at roughly the same time, I assume the problem lies in
> > orisismd itself, but any suggestions as to what might have happened are
> > gratefully appreciated...
>
> It is highly unlikely that you will need to update your 26 agents.  The
> first thing I would do is verify you have at least two osirismd
> processes running.  Then, restart the management console.  In this
> case, I would stop, then start, making sure both processes are gone
> before starting again.
>
> It seems like the scheduler module needs some better logging.
>
> --
>      Brian Wotring ( brian@shmoo.com )
>      PGP KeyID: 0x9674763D
>
> _______________________________________________
> osiris mailing list
> osiris@lists.shmoo.com
> https://lists.shmoo.com/mailman/listinfo/osiris
>


[prev in list] [next in list] [prev in thread] [next in thread]