Nagios Support Forum

Wish I could; dont believe the org paid for support features....just the standard license for our nodes.

Its all good. I will just add a scheduled task to my workflow to login and check for updates manually

I appreciate you looking into this and seeing if anything showed up

So I also went in to ensure my nagios.cfg file had both the passive and plugin timeouts to something like 110 so I am just stuck. I am going to just try the service again and go through everything and see if anything yields. I wonder if it will work and the output just isnt showing... **EDIT**Well t...

I was able to circumvent one check (my URL one) by having it examine for a text string in the URL that was a few layers less. Weird that it wont report the full URL (which took 31-34 seconds to respond) but reports a URL a few layers shorter (10 seconds or so for response) even though I have the tim...

igute Can you give us a little more information? What version of XI are you running and what OS/version? Running latest R1.1.1 on Ubuntu 22 You can manually run the check in XI to see how long it takes to run. Unfortunately thats not the case for these 2 checks. When I run them in Terminal....they ...

I appreciate it! let me know if you need anything additional from me as I will gladly check and give what information i can.

Does anyone know if the GUI has its own built-in timeout that supersedes the timeouts that are placed in the command line? That is the only thing I can think of happening with these 2 servers is that the responses are a little slower for these 2 checks than others. Also, is there a log with the comm...

I have another command that is doing the same thing (but on a different server) ./check_http -t 50 -H <hostaddress_here> -u <url_here> -s <string_info_here> It does take 31seconds to render the OK via Terminal but in the GUI it just returns the command and no information. Does the GUI have its own s...

Hey gents! Another what i hope is a dumb one. I know this may not be the way something was intended to be used, old way, etc. (mostly because we cant get the actual configwizard to work correctly for this plugin so we manually just imported the command from our Core installation and got it all setup...

I went ahead and just ran the to install the upgrade and that worked great.

But updating from the UI still generates that failed update check

Yes my Nagios is licensed, still has 350 days on this current one and is presently only using 38% of the license.