[SOLVED] No system emails send

Daniel-Doggy

Daniel-Doggy

Active Member
Proxmox Subscriber
Nov 27, 2023
235
55
28
Netherlands
daniel-doggy.com
Hello everyone,

I just logged in into my Proxmox VE 8 Node and noticed that it had a lot of packages that needed updating. (They where already listed in "Node > Updates" and some package updates where already 1 to 2 months old.)
I used to get emails when it auto refreshed the repositories and it found updates for packages, but now I do no get them anymore.

I think this is due to the Notification Matcher Rule I have configured. (But not 100% sure.)
Since I created a filter to filter out successful backup emails (as I do not want those emails every day if the backups are successful), now I do not get (any?) emails from the Proxmox VE 8 Node.

The way I created the rules in the default matcher:
Match If: No rules matches

Match field: Exact
Field: Job ID
Value: (The UUID of my nightly backup & nightly remote backup)

Match severity: info

Could it be that it reads as:
If either job ID a or b matches or severity is info then ignore and otherwise send email.

The way I want my matcher to work is:
If job ID is a or b and severity is info, then ignore and in all other cases send email.

If it is a matcher issue then howwould I fix it?
And if not how would I debug this? (root user has email configured so it knows where to send it to.)

Many thanks in advance.
 
If it was just for the updates then yes, that would be a great rule to use.
But I want to receive all notifications except when it is a successful backup notification.

I might just remove the info and only filter out backups. (Since backups have also there own matchers to send a web request when successful so that my uptime monitor knows it successfully backed up.)
But I would prefer to keep the backup fail email, so that if it fails, I will 100% know about it, and all other notifications.
 
Last edited:
Daniel-Doggy said:
If it was just for the updates then yes, that would be a great rule to use.
But I want to receive all notifications except when it is a successful backup notification.

I might just remove the info and only filter out backups. (Since backups have also there own matchers to send a web request when successful so that my uptime monitor knows it successfully backed up.)
But I would prefer to keep the backup fail email, so that if it fails, I will 100% know about it, and all other notifications.
Click to expand...
Then I think you can use regex match rules.
 
For what I can see, the Job ID a or b in combination with and severity info is just not possible. :(
But there is a easy workaround. (No idea why I did not think of this earlier.)

Create one matcher for all notifications types, except vzdump.
And create a second matcher only for vzdump and add a does not match severity info.
 
  • Like
Reactions: Gilberto Ferreira
Daniel-Doggy said:
For what I can see, the Job ID a or b in combination with and severity info is just not possible. :(
But there is a easy workaround. (No idea why I did not think of this earlier.)

Create one matcher for all notifications types, except vzdump.
And create a second matcher only for vzdump and add a does not match severity info.
Click to expand...
Ah that should work, for sure.
 
Daniel-Doggy said:
It is sad I cannot combine them into one match but this will work. :)
Click to expand...

At some point we want to extend notification matchers to allow arbitrary nesting of rules, which would also allow to add more "All rules match/etc." nodes as 'sub-nodes', which would then allow one to create arbitrarily complex match 'expressions'. This is the reason why the rules are displayed in a tree in the first place. But unfortunately some limitations of the tech stack make this quite hard to implement in a clean way, which is the reason why this has not been added yet.
 
  • Like
Reactions: Daniel-Doggy
You must log in or register to reply here.
Top Bottom