Page 2 of 2
Re: Can Not Connect to NRDP Server
Posted: Fri Apr 04, 2014 11:31 am
by mikew
Using that command it connects fine....tried it as nagios user and root both work.
However I see this in the page that it has a 301 is that an issue?
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
Re: Can Not Connect to NRDP Server
Posted: Fri Apr 04, 2014 2:00 pm
by tmcdonald
Can you try running check_http with the "-f follow" switch and see where that ends up? Almost sounds like an apache issue.
Re: Can Not Connect to NRDP Server
Posted: Mon Apr 07, 2014 8:32 am
by mikew
Solved:
I guess this ends up being a lesson on when you have multiple admins working on the same project. One of the admins edited the send_nrdp.sh script on the Nagios server and saved the original but everyone in the process did not realize the edit which commented out the curl line with --insecure. What that meant was that all connections did not allow for the self-signed certificate causing the error. So ultimately NRDS was working fine but the AIX issue with self-signed certificates caused the edit without it being fixed.
So it may be a good idea when you have multiple admins doing edits is to create a doc on all edits that everyone can see all edits in one place...may save a lot of pain.
To all of the Nagios staff that posted on this issue thanks again...
Re: Can Not Connect to NRDP Server
Posted: Mon Apr 07, 2014 9:23 am
by tmcdonald
mikew wrote:So it may be a good idea when you have multiple admins doing edits is to create a doc on all edits that everyone can see all edits in one place...may save a lot of pain.
I usually suggest using a github-like process wherein one person is in charge of making changes and can accept "pull requests" from other people who need those changes made. That way at least one person knows all the changes and can tell if a particular change will cause waves. Might not work in all environments, but it has worked for me in the past.
Glad to see it working at any rate though. I'll be closing this up now.