Notifications not working on new Cluster Host

Drallas

Member
Feb 17, 2023
52
16
13
Planet Earth
I had to reinstall one of my hosts earlier this week, unfortunatley the new host won't send any notifications for Backup Jobs / SMART.
Via the (new) notification-system SMTP or Discord works fine on my pve01 and pve2 but the third pve03 won't pick it up.

Screenshot 2025-02-02 at 12.15.48.png

I did verify and the SMART notifications are generated on the third node:

Code:
smartd -q onecheck -c /etc/smartd.conf

Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.WDC_WDS200T2G0A_00JH30-230201A0050A.ata.state
Device: /dev/nvme0, opened
Device: /dev/nvme0, Samsung SSD 980 PRO 500GB, S/N:S5GYNX0TA24220T, FW:5B2QGXA7, 500 GB
Device: /dev/nvme0, is SMART capable. Adding to "monitor" list.
Device: /dev/nvme0, state read from /var/lib/smartmontools/smartd.Samsung_SSD_980_PRO_500GB-S5GYNX0TA24220T.nvme.state
Device: /dev/nvme1, opened
Device: /dev/nvme1, WD Blue SN570 500GB, S/N:224015467102, FW:234110WD, 500 GB
Device: /dev/nvme1, is SMART capable. Adding to "monitor" list.
Device: /dev/nvme1, state read from /var/lib/smartmontools/smartd.WD_Blue_SN570_500GB-224015467102.nvme.state
Monitoring 1 ATA/SATA, 0 SCSI/SAS and 2 NVMe devices
Executing test of /usr/share/smartmontools/smartd-runner to root ...
Test of /usr/share/smartmontools/smartd-runner to root: successful
Device: /dev/sda [SAT], opened ATA device
Device: /dev/sda [SAT], initial Temperature is 30 Celsius (Min/Max ??/36)
Executing test of /usr/share/smartmontools/smartd-runner to root ...
Test of /usr/share/smartmontools/smartd-runner to root: successful
Device: /dev/nvme0, opened NVMe device
Device: /dev/nvme0, initial Temperature is 38 Celsius (Min/Max ??/40)
Executing test of /usr/share/smartmontools/smartd-runner to root ...
Test of /usr/share/smartmontools/smartd-runner to root: successful
Device: /dev/nvme1, opened NVMe device
Device: /dev/nvme1, initial Temperature is 36 Celsius (Min/Max ??/38)
Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WDS200T2G0A_00JH30-230201A0050A.ata.state
Device: /dev/nvme0, state written to /var/lib/smartmontools/smartd.Samsung_SSD_980_PRO_500GB-S5GYNX0TA24220T.nvme.state
Device: /dev/nvme1, state written to /var/lib/smartmontools/smartd.WD_Blue_SN570_500GB-224015467102.nvme.state
Started with '-q onecheck' option. All devices successfully checked once.

I carefully read https://pve.proxmox.com/pve-docs/chapter-notifications.html but can't find anything that's off, is there anything special that has to be done on the individual host?

Screenshot 2025-02-02 at 12.10.54.png
 
Last edited:
First check if mail could be send from shell otherwise look on your postfix config before searching in pve to problem.
 
First check if mail could be send from shell otherwise look on your postfix config before searching in pve to problem.
Mail is working on the host 1 and host 2, yet I don't use mail any more but Discord, which is also working on host 1 and host 2! Assuming I don't need Postfix for SMTP mail and or Discord!
 
Solved: The /etc/aliases.db file was missing!

Recreated it, ran sudo newaliases, and restarted Postfix with sudo systemctl restart postfix.

Notifications from the third host started working immediately.
 
  • Like
Reactions: waltar