I have 8 - 10 Clients and every time I run my MIDASd on
my monitor server it works for nearly 20 Min and after
that all checks turn blue inclusive the checks on the
localhost. It seems that MIDASd consumes very much of
the cpu time or it crashes due to much data.
Logged In: YES
user_id=685640
Sorry I forgot, I use MIDAS 2.3 Beta3
Logged In: YES
user_id=272241
Assigned bug to tcashmore.
NOTE: For your events to be turning blue indicates MIDASd is
still partially running since it is MIDASd that causes the
check status to change. I'd verify your MIDASc check
interval in MIDASc.cfg is less than your MIDASd blue status
interval in MIDASd.cfg.
If the blue status interval is less than, or very close to
the MIDASc interval, this could cause MIDASd to change the
statuses to blue before the checks get back to it.
Just a thought.
Logged In: NO
I don't think that's the problem. I've found out that every
time I start MIDASc on all clients it works as long as I
have not started MIDASn on the same clients as well. If I do
start MIDASn on this clients, on the most clients MIDASc
crashes. Couldn't figure out why up to now.