Respond URL - Bad Ticket

[lmiltchev]

I am not able to recreate the issue, however I sent a note to our devs so that they can take a look at this.

Or is rr just not used by that many people? Hmmmm

I am not sure how much the respond URL is used, but we don't have many "bad ticket" issues reported from other users. I've seen only 1 or 2.

[scottwilkerson]

When this happens, is it always when you getting the -- in the URL in the notification?

[BanditBBS]

When this happens, is it always when you getting the -- in the URL in the notification?

Yes, and I am 99% sure its always during an apply configuration or shortly after when the stuff is coming back up. I have my retries set to 12 now with a 5 second retry in the rr.php file. It's really lowered the number of bad ticket issues.

[scottwilkerson]

You are correct... I have found the cause, and placed a fix in the attached file. Place in

Code: Select all

/usr/local/nagiosxi/html/includes/utils-notifications.inc.php

utils-notifications.inc.zip

The solution was to retry getting the object_id 5 time separated by 1 second in case ndo was in the middle of resetting the object id's, (e.g. during an apply configuration) if the object ID is still -1, we will use the standard URL instead of the rapid response URL in the notification message. So you will actually still get a usable URL in the message.

This fix will be included in XI 5R1.0

[BanditBBS]

Cool Scott, thanks, I'll put this into production and test here.

Can you clarify what you meant by "standard url" in the cased when it still fails after the retries? Will it be a url directly to the problem host and/or service just without the ticket?

[ssax]

Yes, that is correct.

[BanditBBS]

Thanks! I think this can be closed for the second and hopefully final time

[abrist]

I just tested it here and it seems to work. PM me if this issue recurs and I will reopen the thread.