True answer - Noabrist wrote:You available now?
But I can't bring myself to say it, so sure.
Respond URL - Bad Ticket
Re: Respond URL - Bad Ticket
But I can't bring myself to say it, so sure.
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: Respond URL - Bad Ticket
Now I am genuinely confused.
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: Respond URL - Bad Ticket
LOL, send me the link, we can do it now.abrist wrote:Now I am genuinely confused.
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: Respond URL - Bad Ticket
Incoming PM.
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: Respond URL - Bad Ticket
For reference:
Think we figured it out. Traced the rr.php file's function calls deep into some utilities that deal with the databases, and get_nagios_object_id can return -1 in some cases where the query fails. Could be a number of things, network connectivity being somewhat high on the list. How loaded is your (I am assuming offloaded) db?
Think we figured it out. Traced the rr.php file's function calls deep into some utilities that deal with the databases, and get_nagios_object_id can return -1 in some cases where the query fails. Could be a number of things, network connectivity being somewhat high on the list. How loaded is your (I am assuming offloaded) db?
Former Nagios employee
Re: Respond URL - Bad Ticket
Not an offloaded dbtmcdonald wrote:For reference:
Think we figured it out. Traced the rr.php file's function calls deep into some utilities that deal with the databases, and get_nagios_object_id can return -1 in some cases where the query fails. Could be a number of things, network connectivity being somewhat high on the list. How loaded is your (I am assuming offloaded) db?
I'm doing some investigating on my end and also informing the user that uses the rr very often to immediately alert me when if doesn't work next time.
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: Respond URL - Bad Ticket
Check this out.
That spike in CPU load started at the very moment the batch of rr urls were all wrong.
p.s. I really hope you guys release the fix for not being able to save graphs when forcing https in the next XI release, grrrrrr
p.s. I really hope you guys release the fix for not being able to save graphs when forcing https in the next XI release, grrrrrr
You do not have the required permissions to view the files attached to this post.
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: Respond URL - Bad Ticket
Interesting. Do have any idea what caused the load spike?
Spenser has filed a bug report for the graphs export . . . No word yet. You know what I am going to say . . . After the conference?
Spenser has filed a bug report for the graphs export . . . No word yet. You know what I am going to say . . . After the conference?
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: Respond URL - Bad Ticket
Nah, no clue. I'm going to assume something with MySQL since the look ups were failing, lol. They have been informed to let me know ASAP next time so i can better investigate. So I guess this issue can be ignored until I am able to investigate more.abrist wrote:Interesting. Do have any idea what caused the load spike?
Spenser has filed a bug report for the graphs export . . . No word yet. You know what I am going to say . . . After the conference?
I filed a bug report months ago...hurry
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: Respond URL - Bad Ticket
I think it requires begging highcharts for some code, but I am not sure. When we sit down for the maintenance pass post conference I will add this to the list.
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.