@rsturm thanks for the info, I didn’t know the log. Maybe there was never a Need to know it. Because of our big infrastructure and its confiuration.
@flaminggenius If you see log entries after sending it manually (i guess with the root-user/permissions) and not if icinga is sending it, i would say the icinga user misses some permissions for that (file permisisons, SELinux etc.).
Hey Stevie,
When I say that I am sending it manually I mean I go to a service and hit send notification.
Also I do have selinux disabled
If there was a permissions issue then it wouldnt allow me to send it manually would it? Even manually it still within icinga so I know that icinga is capable of sending them but its not sending them automatically when a service enters a critical or warning state.
Thanks Joseph
hmm. ok if from the side of your OS is no permission problem and you can send it from the GUI than there must something wrong in your notification rule. But I don’t see an error.
Sorry, in this case I’ve run out of ideas. I hope other community members have more ideas for you.
Thank you for trying to help hopefully someone else can provide some more clarity.
Thanks Joseph
Have you checked your service via the API for these variables? You can query the API with the URL via the browser or using curl.
That would make no difference from what i can icinga is not being triggered to send a notification
This would make a difference, as you get information that is not available in the DB (afaik) and thus can maybe see why the notification is not triggered at all.