Varlogsyslog not updating
For example, with the above settings, an incoming message with status logging to multiple locations.
At the end of our firewall script we have the following catch-all to LOG details of any access attempts that weren't already either ACCEPT'ed or REJECT'ed by earlier rules: We've excluded kernel messages from the syslog, and put a stop on kern.debug messages to prevent them being picked up by subsequent filters.
If this threshold is breached, Opsview Monitor will elegantly shutdown instead of crashing and leaving the system in a problematic state when the disk space issue is resolved.
To confirm you are encountering the disk space issue, run the command: # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/ovauthorvg-rootlv 9.3G 7.6G 1.2G 87% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 2.5G 4.0K 2.5G 1% /dev tmpfs 497M 352K 496M 1% /run none 5.0M 0 5.0M 0% /run/lock none 2.5G 0 2.5G 0% /run/shm none 100M 0 100M 0% /run/user /dev/mapper/ovauthorvg-bootlv 233M 38M 179M 18% /boot Logs are always a good place to start when it comes to troubleshooting.
An alternative approach used by some is: There are now three types of filters available in rsyslog.
We've been working with the "traditional" selectors, but there are also Rainer Script-based filters and property-based filters which you can read up on here.
Additionally, you can read the Rsyslog manual, try their support forum (they offer professional Rsyslog support), or check out our Rsyslog manual configuration docs.
The syntax for the stop has changed from tilde (~) to the word 'stop' in the latest version.
If the watchdog process starts but the processes it is monitoring do not, check your sudo configuration (using the command Finally, if your watchdog services start (as per the 'summary' command), but suddenly shutdown after a minute, you may not have enough free disk space.
Opsview Monitor requires a MINIMUM of 2GB free space.
They allow for regular expression matching among other things.