Hi,

that works perfectly to me. :) Thanks for the fast fix, that speed was
really amazing! The scheduling of the checks is now saved even during
the restart of the arbiter.

But now I encountered another error, which did not happen with the
version I used before:

When I start or stop the arbiter it works fine, but when I do a restart
(/etc/init.d/shinken-arbiter restart) the arbiter is searching for the
arbiterd.pid in my current working directory. Because of that he can't
find this file. When I run the script (/etc/init.d/shinken-arbiter
restart) while I'm in the directory /var/lib/shinken/ (where the
arbiterd.pid is placed) it works.


Here you can see it:

/home/m.elger # /etc/init.d/shinken-arbiter restart
Restarting arbiter
Doing config check
.
FAILED: shinken.daemon.InvalidPidFile: [Errno 13] Permission denied:
'/home/m.elger/arbiterd.pid' (full output is
in /tmp/bad_start_for_arbiter) ... failed!
failed!


When I do the same thing in the directory /var/lib/shinken/ it works:

/var/lib/shinken # /etc/init.d/shinken-arbiter restart
Restarting arbiter
Doing config check
.
.


We are planning to use shinken in our company as main monitoring tool
instead of nagios. My colleague reported another bug (Ticket #250), when
it's fixed we will roll out a first testconfig on all our servers.

When it's successfull we will be happy to monitor our 574 hosts und 7500
services with your great shinken ;)


markus



Am Dienstag, den 17.05.2011, 15:31 +0200 schrieb nap:
> 
> 
> On Tue, May 17, 2011 at 2:27 PM, nap <napar...@gmail.com> wrote:
>         
>         
>         On Tue, May 17, 2011 at 1:52 PM, Markus Elger
>         <markus.el...@unister.de> wrote:
>         
>         [..] 
>                 
>                 Does anyone have a solution for that?
>                 
>         I think from now it's not managed, when status data are kept;
>         the schedule data are not, so the reschedule is done on each
>         restart. I'll add this so when we restart, we keep the already
>         compute check date. I open a ticket about it
>         (https://sourceforge.net/apps/trac/shinken/ticket/259). It
>         should not be so hard, so it should be available soon :)
>         
>         
> Hi,
> 
> It's done in the lastest git source. It will use the retention data if
> the value is available and in the future. Can you try with this
> version? (you can get it at https://github.com/naparuba/shinken or by
> pulling your git repo if you use git).
> 
> Thanks, and welcome on the THANKS file by the way :)
> 
> 
> Jean
>  
>         
>         
>                 
>                 Best Regards
>                 markus 
> 
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________ Shinken-devel mailing list 
> Shinken-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/shinken-devel



------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to