ndo2db Hogging ALL the CPU
Re: ndo2db Hogging ALL the CPU
This could still be due to ndomod instead of ndo2db . . . .
What process is to blame for the spike?
What process is to blame for the spike?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: ndo2db Hogging ALL the CPU
Nothing that I can see. There is no difference as to when the spike isn't happening(when watching top).abrist wrote:This could still be due to ndomod instead of ndo2db . . . .
What process is to blame for the spike?
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: ndo2db Hogging ALL the CPU
James,
Can you PM me your nagios.cfg and also, can you confirm/deny if you have checks that have specific timeperiods.
e.g. A "work hours" time period that kicks off at 9am and a whole bunch of additional checks are scheduled...
thanks
Can you PM me your nagios.cfg and also, can you confirm/deny if you have checks that have specific timeperiods.
e.g. A "work hours" time period that kicks off at 9am and a whole bunch of additional checks are scheduled...
thanks
Re: ndo2db Hogging ALL the CPU
Getting called James on the forums is like being called to the principal's office, lol.
I sent the PM. As for special time periods for checks, yes there are some, but I can count them on less then one hand, for sure less than 2.
I sent the PM. As for special time periods for checks, yes there are some, but I can count them on less then one hand, for sure less than 2.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: ndo2db Hogging ALL the CPU
I looked at the file, and nothing out of the ordinary there...
I know this is a shot in the dark, but trying to figure out what the heck could be running causing the spike all at the same time.
It would be interesting to see the processes that are running right when the load spiked. Maybe you could setup an event handler that runs when load on localhost goes above a certain threshold that would write some process information to a text time?
Less than 2 timeperiods, or less than 2 hosts/services that use the time periods?BanditBBS wrote: As for special time periods for checks, yes there are some, but I can count them on less then one hand, for sure less than 2.
I know this is a shot in the dark, but trying to figure out what the heck could be running causing the spike all at the same time.
It would be interesting to see the processes that are running right when the load spiked. Maybe you could setup an event handler that runs when load on localhost goes above a certain threshold that would write some process information to a text time?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: ndo2db Hogging ALL the CPU
We just came to another possible conclusion...
Do you have scheduled reports setup on this system?
I ask because the default "time" for scheduled reports is in fact 9:00am and if you have many that you have not changed the run time of, they could be all kicking off at the exact same time...
Do you have scheduled reports setup on this system?
I ask because the default "time" for scheduled reports is in fact 9:00am and if you have many that you have not changed the run time of, they could be all kicking off at the exact same time...
Re: ndo2db Hogging ALL the CPU
Is there a way to qeury the DB for a list....I have many users that may have done that. However, the CPU load spike may last for 10 hours or more, so is that a real possibility?
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: ndo2db Hogging ALL the CPU
Code: Select all
crontab -u apache -lRe: ndo2db Hogging ALL the CPU
Nah, it can last all day. 12 hours 20-200 load, next 12 hours 2-4 load, doing the exact same stuff. However, if it is fine around 9am, it more often then not will start the spike then.
Apparently only 3 scheduled reports so far, actually surprised me a little.
Apparently only 3 scheduled reports so far, actually surprised me a little.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Re: ndo2db Hogging ALL the CPU
Which reports? (if you have a db or logfile problem, certain reports could be to blame for load problems).BanditBBS wrote:Apparently only 3 scheduled reports so far, actually surprised me a little.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.