-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experiencing Issues in Nagios3 #2
Comments
Looks like the definition above Line 10 is broken, does it have a closing curly bracket? |
No, when it threw the error, I moved the "define command" statement to the beginning of the nagios.cfg file, and it still gives the error. If I comment the two "define command" statements out, it works fine. I was thinking that maybe the syntax has changed.
I would appreciate any guidance you can give. Thanks! |
Hm... Just as a note, the webhook address shouldn't include the URL: https://hooks.slack.com/services/ Also, can you run If you don't mind, post the output here and I'll take a look (feel free to comment out anything confidential). This script is currently working in production elsewhere on Nagios3 so hopefully we can work it out. |
As an aside, if you want to test the script without Nagios you can run |
Thanks for the above test. I was able to run it and alert Slack. However, the following syntax:
still results in an error. I'm on Devuan, which is Debian minus systemd. I ran:
which resulted in:
Line 1306 is the |
So it turns out this was a misunderstanding on my part. The |
Ah of course, I didn't have a Nagios setup to look at anymore these days (this tool was written for an old client) and I was trying to remember the way it's configured. You're right, nagios.cfg is a different syntax than the command / host / service definitions. Not a waste of time at all, your feedback has made it clear I need to improve the documentation so thank you for that. |
Should this work with nagios3? I continuously get the following error:
However, line 10 is just
define command {
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: