I am using Shinken config with Adagios and it works nicely. No patching
needed, just set the configuration accordingly.
http://www.adagios.org/
Regards
PS: moderator I've replied with another e-mail address before, my apologies
On 26 March 2015 at 14:00, Smain Kahlouch wrote:
> Hi everyone,
>
Those timeout issues happened to me on a similar sized structure.
One of my realms was never getting stable and I discovered it wasn't
timeout but actually number of threads on Cherrypy due number of other
Shinken components.
Try allowing more threads on your scheduler (as it is the most central
c
; I've removed the extra schedulers and pollers I had added thinking it
> would help (now a total of 4 each plus a spare) and raised the thread pool
> size on all daemons to 50 and I'm still having issues with timeouts.
>
>
>
> On 5/12/15 2:34 AM, Felipe openglx wrot
system up with 0 hosts just to see if everyone is happy?
(Sorry that my e-mail is a bit confusing, it's bed time but felt the need
to assist on the troubleshooting tomorrow I will try to make it
clearer).
Regards
On 12 May 2015 at 22:26, David Good wrote:
>
> On 5/12/15 2:08 PM
I've noticed that Shinken 2 doesn't go easily with kill. I've always done
"pkill -9 -f shinken-" when needing to restart them.
Glad to hear you got something working, David. All hosts or just a fraction
of them?
Regards
On 13 May 2015 at 21:43, David Good wrote:
>
>
> OK, things seem to be sta
rds
On 13 May 2015 at 22:18, David Good wrote:
> It was all hosts, but I just reloaded with a new config, so we'll see if
> my luck holds :-)
>
>
> On 5/13/15 2:00 PM, Felipe openglx wrote:
>
> I've noticed that Shinken 2 doesn't go easily with kill. I'
ome new configs adding
> and removing hosts and services from monitoring. If it can't finish
> dispatching it makes it hard to test :-/
>
> On 5/14/15 2:49 PM, David Good wrote:
>
>
> I doubt that was the case -- I was careful to make sure everything was
> stopped befo
