headers
Nicolas KOWALSKI | 19 Feb 2008 13:05
Picon

Re: mon forking problem

Nicolas KOWALSKI <niko <at> petole.dyndns.org> writes:

> For information, after modifying the scheduler as described above,
> our monitoring server did not have any fork problem anymore: last
> week it launched 2.5M forks (monitors and alerts) happily.

We tracked down the source of the problem. In our logfiles, we
sometimes see the following:

2008-02-19 03:56:56 err: call_alert: could not exec alert
/apps/Minotaure/lib/alert.d/wh-stat.alert: Argument list too long
2008-02-19 03:56:56 err: call_alert: could not exec alert
/apps/Minotaure/lib/alert.d/wh-sendtrap.alert: Argument list too long
2008-02-19 03:56:56 err: call_alert: could not exec alert
/apps/Minotaure/lib/alert.d/wh-kpi.alert: Argument list too long

This explains why we ended up with several mon processes. 

With our patch (exit if exec fails during call_alert), this does not
happen anymore.

--

-- 
Nicolas
Permalink | Reply | 0 comments |
headers
George Georgalis | 25 Feb 2008 21:20

managing config files

I'd like to use mon to manage configuration files, such
as .procmailrc, so that the file is result of regex A
for some periods of the day and regex B at other times.

Is anyone using mon for this or similar task? how?

// George

--

-- 
George Georgalis, information system scientist <IXOYE><
Permalink | Reply | 2 comments |
headers
Michael Alan Dorman | 26 Feb 2008 00:20
Favicon
Gravatar

Re: managing config files

On Mon, 25 Feb 2008 15:20:01 -0500
George Georgalis <george <at> galis.org> wrote:

> I'd like to use mon to manage configuration files, such
> as .procmailrc, so that the file is result of regex A
> for some periods of the day and regex B at other times.
> 
> Is anyone using mon for this or similar task? how?

mon is for monitoring, not managing.  You can certainly make it do what
you want, but it will be like driving a nail with a screwdriver---the
wrong tool for the job rarely produces a pretty result.

Consider looking at alternative tools like cfengine or puppet, which
are both designed for this very use.

Mike.
Permalink | Reply | 1 comment |
headers
George Georgalis | 26 Feb 2008 20:18

Re: managing config files

On Mon, Feb 25, 2008 at 06:20:58PM -0500, Michael Alan Dorman wrote:
>On Mon, 25 Feb 2008 15:20:01 -0500
>George Georgalis <george <at> galis.org> wrote:
>
>> I'd like to use mon to manage configuration files, such
>> as .procmailrc, so that the file is result of regex A
>> for some periods of the day and regex B at other times.
>> 
>> Is anyone using mon for this or similar task? how?
>
>mon is for monitoring, not managing.  You can certainly make it do what
>you want, but it will be like driving a nail with a screwdriver---the
>wrong tool for the job rarely produces a pretty result.

I understand. cron is pretty much what I need, with
a little atomic design in scripts, that has worked
fine. I was just wondering if anyone had made config
modifying scripts as a mon test and used the time module
/ scheduler to invoke. Or some other means with mon.

>Consider looking at alternative tools like cfengine or puppet, which
>are both designed for this very use.

dono about puppet, but what I recall about cfengine,
that is overkill for my procmailrc/muttrc files. Will
take another look at them -- indeed both too big a hammer.

I was just wondering if someone identified the best way
to use mon to run scheduled "tasks" vs tests, though I
think the best way is just as I noted above, run my
(Continue reading)

Permalink | Reply | 0 comments |

Gmane