no notification from PBS

M

muekno

Member
Dec 15, 2023
266
23
23
my PBS 4.1.4 (newinstall) works fine notifiys me every time a backup runs
custumers PBS 4.1.4 (update from latest 3.x) does backups but no nnotification
comparing both settingd in GUI no difference but there are other differences
My PBS runs on its own hardware
Custumer as a VM under PVE 8.x cluster
Custumers PBS has a notifications.cfg mine not
custumers PBS stores toi external NAS, mine to its local HD

searching no since a week find no solution.
need help or hint
Thank you
 
sendmail: mail-to-root
comment Send mails to root@pams's email address
mailto-user root@pam

matcher: default-matcher
comment Route everything but successful prune job notifications to mail-to-root
invert-match true
match-field exact:type=prune
match-sevirity info
mode all
target mail-to-root

Here it is
 
There is a typo in the config at line 9, match-sevirity should be match-severity, try this one:

Code: 
sendmail: mail-to-root
    comment Send mails to root@pam's email address
    mailto-user root@pam

matcher: default-matcher
    comment Route everything but successful prune job notifications to mail-to-root
    invert-match true
    match-field exact:type=prune
    match-severity info
    mode all
    target mail-to-root
 
journalctl -u proxmox-backup -f should show configuration deserialization errors on your customer's machine, something along the lines of:
Code: 
Mar 13 14:06:19 pbs-dev proxmox-backup-api[1704]: could not read notification config: could not deserialize configuration: parsing "notifications.cfg" failed: line 9 - unknown property 'match-sivirity'
 
there is now typo in the real .cfg. Could not copy paste so I typed it and made the mistake

journalctl -u proxmox-backup -f shows me the error. PBS tries to connect with ipv6 but next mailserver accepts only ipv4

will try to fix that
 
  • Like
Reactions: a.bied-charreton
I thought it is solved when I got the test mail. but is is not, I got no mail when the backup runs this night.
 
What do the logs say? Did it fail because of using ipv6 again? Did PBS even attempt to send a notification (check the backup job's tasklog for "queued notification ...")? The Postfix logs may also be helpful here (journalctl -u postfix.service --since "Mar 14 02:00:00" --until "Mar 14 02:30:00", change the timestamps to the time where your backup ran).
 
Last edited:
I'm having the same issue, but using a webhook. I see my notifications queued in the logs, but nothing ever shows up.

2026-03-20T20:59:39-04:00: Summary: removed vanished: snapshots: 0, groups: 0, namespaces: 0
2026-03-20T20:59:39-04:00: sync job 'nas-pve:pvebackups:pbs-offline::s-1ca60f1f-445a' end
2026-03-20T20:59:39-04:00: queued notification (id=be5b3c87-25ed-44e4-8e70-ee49038f6f4e)

Here's my notifications.cfg

sendmail: mail-to-root
comment Send mails to root@pam's email address
mailto-user root@pam

smtp: mailrise.xyz
author $hostname
disable true
from-address pbs-offline@wapnet.wapnitsky.com
mailto nasupdates@mailrise.xyz
mode insecure
server mailrise.xyz

webhook: Healthchecks
disable true
method post
url http://10.150.33.33:8000/ping/ac13a15d-2b6c-4f71-805d-e33960afd142

webhook: apprise_server
body ewoidXJscyI6IFsibWF0cml4czovL25hc3VwZGF0ZXM6SWJDbXdZVVQ4ZlBnNDFAbWF0cml4LndhcG5pdHNreS5jb20vIW9YckpDT2RZWnFqcHV5cEFrYzptYXRyaXgud2Fwbml0c2t5LmNvbSJdLCAgCiJ0aXRsZSI6ICJ7eyB0aXRsZSB9fSAoe3sgc2V2ZXJpdHkgfX0iLAoiYm9keSI6ICJ7eyBtZXNzYWdlIH19Igp9
header name=Content-Type,value=YXBwbGljYXRpb24vanNvbg==
method post
url http://10.150.88.5:8000/notify/

matcher: all-to-apprise
match-severity info,notice,warning,error,unknown
mode all
target apprise_server

matcher: default-matcher
comment Route everything but successful prune job notifications to mail-to-root
disable true
invert-match true
match-field exact:type=prune
match-severity info
mode all
target mail-to-root
 
You must log in or register to reply here.
Top Bottom
Back