ok, so I think what the issue is. I found a different rule that would
do:
& ~
However, that means " stop logging anything that matches the last rule",
however, instead of stopping just that rule, it was stopping everything.
The reason why this was stopping everything is because it didn't really
Ok, so MAAS install's an rsyslog config to forward messages from syslog
to /var/log/maas/maas.log. Today we noticed that maas.log was completely
empty, and on further checking, we noticed that syslog was completely
empty as well. The fun fact, however, is that MAAS has not changed its
syslog
