Weird check timing

Post by **BanditBBS** » Fri Mar 07, 2014 1:25 pm

So, not only do I have weird fwding of information from one server to another(different thread) I have some weird timing of checks.

I have a service check scheduled as so:

Settings.JPG

But look at the timing here after a critical:

Capture.JPG

Any ideas why this would be doing it this quick instead of 5 minutes in the future like it should? I've noticed this on other checks as well and am just now deciding to investigate.

tmcdonald · Post by **tmcdonald** » Fri Mar 07, 2014 3:07 pm

Let's check all the logs. The number of logs we need to check is: all of them. All is, among other things, how many logs we need.

More specifically we think gearman might have something to do with this. We'll need those logs. nagios.log would be useful for both servers as well. NRDP would be nice. NCPA logs if you have them.

Also, are you using both the NRDP protocol with the NCPA agent? Is this a single gearman box reporting directly to an XI system? Or is this NCPA relaying through a central NCPA system?

And since you seem to prefer Vizio over my hand-drawn diagrams, us support-folk wouldn't mind a diagram of this.

And from Ethan himself: Do you have two core processes running at once anywhere?

Post by **BanditBBS** » Fri Mar 07, 2014 3:20 pm

Let me give more information here as you are confusing my two open threads right now....

I agree, it is probably related to my other issue, but that then rules out NRDP as part of the cause. This service check I am referring to is not one that is being fwd from another server or anything, it is just on this server and that is it. Also, this server is the only one that uses gearman and this server is the one that was sending to the other server, so it could all be this server/gearman, so lets investigate from that.

While I gather the gearman logs and nagios log, umm, what am I searching for to verify that I only have one core process running at once?

Post by **BanditBBS** » Fri Mar 07, 2014 3:31 pm

The logs zipped up are 3.5 MB, too large for the forums, email them to support?

tmcdonald · Post by **tmcdonald** » Mon Mar 10, 2014 9:10 am

Yea, that'll work. It will probably try and open a ticket, but obviously we aren't going to count that.

Post by **BanditBBS** » Mon Mar 10, 2014 9:45 am

Logs have been sent.

I'm having trouble wrapping my head around this issue. Yes I am using gearman on the source server that is sending results to the destination server. I don't see how that can be gearman though as the source only receives one result and should only be fwd that one result to the destination. Then there is the second example I listed above that is all on the source server, it is not something that is being fwd to another. So that does make it seem like it is the source server causing the issue. To early on a Monday to think about this stuff! LOL

Post by **lmiltchev** » Mon Mar 10, 2014 1:19 pm

Logs have been sent.

BanditBBS, neither Sam or Trever has received your email, yet.

Post by **BanditBBS** » Mon Mar 10, 2014 2:02 pm

Just sent to them directly.

Sorry for the delay...haven't had water at home for 25 days and water dept was outside trying to resolve...I don't wish this on my worst enemy!

Post by **lmiltchev** » Mon Mar 10, 2014 2:41 pm

haven't had water at home for 25 days

Oh my! This is not good at all. I'm sorry to hear that! Let's hope they are going to fix this soon.
BTW, Trever got your email, so I am locking this topic. We will continue communicating via email.

tmcdonald · Post by **tmcdonald** » Wed Mar 12, 2014 11:56 am

Trevor got your email and is unlocking this thread so we can continue discussion here.

Nagios Support Forum

Weird check timing

Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing

Re: Weird check timing