Nagios Support Forum

Hello,

If we attempt to download the PDF or JPEG of a Service State History, we get "No matching results found. Try expanding your search criteria." However, if we view the Host State History, we can download the Service State History. However, if we attempt to filter to a specific service, we receive the same error.

Service State History Download Preview Host State History Download Preview We are running 5.11.2. We are running 5.11.3 in our test environment and it has the same problem.

Thanks in advance.

John

Hi @shoreypu,

Could you provide the exact search parameters you are using in both instances? And do you get "No matching results found." when you run the report or only when you attempt to download it?

Just from looking at the screenshot, it might be worth trying to change the names of the services that aren't showing accurate results to a standard string of alphanumeric characters (note the colon escape characters in Service State History Download Preview) and/or run the report on another service to see if that is indeed the issue.

Let us know what you find.

And as a follow-up to that, does the report as shown in the browser before you export it to a jpeg or pdf file show correct results?

For Host State History, I'm looking at [All Services] for a specific host, Type and State Type are looking for Both, and State is Any.

I'm getting no matching results found in the PDF preview and download, and the JPEG download. I am getting results if I download the CSV.

All of our services have : in the name, making renaming every check (as a solution) extremely difficult to do.

John

I renamed a check in our QA system and it does look as though the colons: are causing the problem. Trouble is that all of our checks use colons, and if we rename the checks, were also going to have to rename the RRD files or we're going to lose the entire history.

Two questions...
Is there anyway around having to rename all of our checks?
Are there other punctuations that need to be avoided or are there best practice recommendations that should be used instead?

Thanks

Hi again @shoreypu,

When testing on a live XI system, we named a service check using a colon and were not able to replicate your issue. To help troubleshoot this, we suggest opening a case via Answer Hub.

Sorry I couldn't find your solution here.

Opened a case in the AnswerHub...Thanks!

Thank you! Hope you get your issue resolved!

For everyone else's benefit, I contacted support and the answer is to update /usr/local/nagiosxi/html/config.inc.php, change the following from false to true.

$cfg['use_https'] = true;

Hope this helps someone else in the future.

We are glad the issue was able to be resolved, and thank you for sharing the results that fixed the issue.