Project

General

Profile

Actions
Copy link

Feature #12281

open

Add support for Telegram/Pushover notifications

Added by Viktor Gurov over 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Nut
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:

Description

NUT doesn't send notifications to a Telegram/Pushover backend, even when the Telegram/Pushover configuration is set up in the System configuration.

see also #11972

Actions
Copy link
 #2

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
Actions
Copy link
 #3

Updated by Viktor Gurov over 2 years ago

  • Status changed from Pull Request Review to Feedback

Merged

Actions
Copy link
 #4

Updated by Jim Pingle over 2 years ago

  • Status changed from Feedback to New

NUT tries to send notifications from an unprivileged user and can't do so because of the permissions on /var/db/notifyqueue.messages. It works when they are sent as root.

For now we can at least suppress the error, but the underlying system in base will need a more substantial change to allow these kinds of messages from unprivileged users. Also, when it does work, the user will get two SMTP notifications as one is sent explicitly and the other from notify_all_remote().

https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/173

Actions
Copy link
 #5

Updated by Viktor Gurov about 2 years ago

  • Status changed from New to Feedback
Actions
Copy link
 #6

Updated by Jim Pingle about 2 years ago

  • Status changed from Feedback to New

That was just the workaround to suppress the error -- the longer term fix needs more thought on how NUT can send these messages as an unprivileged user.

Actions
Copy link

Also available in: Atom PDF