Search found 33 matches
- Wed Apr 03, 2019 10:17 am
- Forum: Nagios XI
- Topic: Error: Request packet type/version was invalid!
- Replies: 1
- Views: 962
Error: Request packet type/version was invalid!
We see the following errors in our Nagios agents. These alerts happen on all of our clients and occur several times every second which is very annoying. how can we get rid of them? Thanks! Apr 3 11:06:29 xxxxxx nrpe[9801]: Client request was invalid, bailing out... Apr 3 11:06:59 xxxxxx nrpe[9854]: ...
- Wed Dec 19, 2018 9:52 am
- Forum: Nagios XI
- Topic: Upgrade to 5.5.8 failed
- Replies: 7
- Views: 530
Re: Upgrade to 5.5.8 failed
Now that you checked the log and confirmed the upgrade finished successfully, yes you can close out this ticket. Thanks a lot for your prompt help!
- Wed Dec 19, 2018 8:24 am
- Forum: Nagios XI
- Topic: Upgrade to 5.5.8 failed
- Replies: 7
- Views: 530
Re: Upgrade to 5.5.8 failed
You are right! It turned out epel repo was disabled. I enabled it and installed snmptt, net-snmp, and net-snmp-perl. Then I ran "./upgrade -f". This time, the upgrade seems to be complete. I attached the upgrade log. Could you please double-check to see if it is actually complete? Thanks m...
- Tue Dec 18, 2018 3:53 pm
- Forum: Nagios XI
- Topic: Upgrade to 5.5.8 failed
- Replies: 7
- Views: 530
Re: Upgrade to 5.5.8 failed
This issue is fixed after I commented out both "# Uninstall ajaxterminal to install shellinabox" and "# Install new sshterminal if it needs to install it" Yet, the upgrade stopped with the messages below. Does it look complete? From the web GUI, it look like it has been upgraded ...
- Tue Dec 18, 2018 8:23 am
- Forum: Nagios XI
- Topic: Upgrade to 5.5.8 failed
- Replies: 7
- Views: 530
Upgrade to 5.5.8 failed
We are at Nagios XI 5.4.11 and I was trying to upgrade it to the latest version 5.5.8 last night but failed. I did it from the GUI, Quick upgrade and Manual upgrade following your instructions but all failed at the same place. The Nagios server has no problem connecting to Internet, including https:...
- Thu Mar 30, 2017 2:24 pm
- Forum: Nagios XI
- Topic: HTTP URL monitor not working
- Replies: 11
- Views: 2850
Re: HTTP URL monitor not working
We use CloudFlare to protect our website including from robots, but how come it works with manual checking from browsers? Is there a different way Nagios can check on the health of URLs?
- Thu Mar 30, 2017 9:24 am
- Forum: Nagios XI
- Topic: HTTP URL monitor not working
- Replies: 11
- Views: 2850
Re: HTTP URL monitor not working
Here's what I tested with the same failure.
COMMAND: /usr/local/nagios/libexec/check_http -H images.nga.gov -f ok -I 104.16.92.31 -u '/' -S -p 443
OUTPUT: HTTP CRITICAL: HTTP/1.1 503 Service Temporarily Unavailable - 5072 bytes in 0.035 second response time |time=0.034862s;;;0.000000 size=5072B;;;0
COMMAND: /usr/local/nagios/libexec/check_http -H images.nga.gov -f ok -I 104.16.92.31 -u '/' -S -p 443
OUTPUT: HTTP CRITICAL: HTTP/1.1 503 Service Temporarily Unavailable - 5072 bytes in 0.035 second response time |time=0.034862s;;;0.000000 size=5072B;;;0
- Tue Mar 28, 2017 3:17 pm
- Forum: Nagios XI
- Topic: HTTP URL monitor not working
- Replies: 11
- Views: 2850
Re: HTTP URL monitor not working
Sorry for '-H <HOSTNAME>', <HOSTNAME> would be the Nagios server name?
- Tue Mar 28, 2017 9:45 am
- Forum: Nagios XI
- Topic: HTTP URL monitor not working
- Replies: 11
- Views: 2850
Re: HTTP URL monitor not working
I use the Configuration Wizards -> Website URL monitor -> URL Status and URL Content
For URL Status, it is check_xi_service_http -f ok -I 104.16.92.31 -u '/' -S -p 443
For URL Content, it is check_xi_service_http -s "contentxxx" -f ok -I xxx.xxx.xxx.xxx -u '/' -S -p 443
For URL Status, it is check_xi_service_http -f ok -I 104.16.92.31 -u '/' -S -p 443
For URL Content, it is check_xi_service_http -s "contentxxx" -f ok -I xxx.xxx.xxx.xxx -u '/' -S -p 443
- Mon Mar 27, 2017 3:28 pm
- Forum: Nagios XI
- Topic: HTTP URL monitor not working
- Replies: 11
- Views: 2850
HTTP URL monitor not working
Trying to deploy a Website URL monitor but got "HTTP CRITICAL: HTTP/1.1 503 Service Temporarily Unavailable" error. This website works fine when manually testing but it is protected by a 3rd party front-end called CloudFlare. I need to configure the HTTP monitor to work this front end.