#358 [Debian] Install logcheck rules

Reporter admin@rwky.net
Owner MattJ
Created
Updated
Stars ★ (1)  
Tags
  • Status-WontFix
  • Priority-Medium
  • Type-Defect
  • Milestone-0.10
  1. admin@rwky.net on

    The default log settings in 1nightly156-1~precise are log = { info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for verbose logging error = "/var/log/prosody/prosody.err"; "*syslog"; } I suggest adjusting them to: log = { info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for verbose logging error = "/var/log/prosody/prosody.err"; warn = "*syslog"; } To prevent syslog from being flooded, if a user really wants debug messages going to syslog then they can change the config file.

  2. MattJ on

    Part of the reasoning behind the current config is that syslog has its own filtering, which is probably more efficient (logging and filtering is syslog's whole purpose in life, after all). Indeed, most standard syslog configs already filter out low priority log messages into /var/log/debug already.

    Changes
    • owner MattJ
  3. MattJ on

    That sounds like a great idea. I have no experience with logcheck, but if you can provide some rules to ignore info and lower from Prosody, I'd be happy to include it in our packages.

  4. admin@rwky.net on

    Ok I'll take a few days to collect the log entries that need to be omitted. I'll attach the file here when done.

  5. admin@rwky.net on

    Ok logcheck file attached I've ran this on my production server for a few days and it seems to filter everything that's common and doesn't require much attention. You can add it to the deb package script with dh_installlogcheck http://manpages.ubuntu.com/manpages/precise/en/man1/dh_installlogcheck.1.html

    Attachments
  6. MattJ on

    Many thanks! I'll add this when I'm next working on packages.

    Changes
    • title [Debian] Install logcheck rules
    • tags Milestone-0.10 Status-Accepted
  7. MattJ on

    This was scheduled for 0.10 a long time ago. I'm not confident that the attached logcheck config is still up to date, and I don't want to delay the release any further. This issue has also had no input from anyone other than the original reporter, therefore I'm going to close it. If someone feels strongly about this, feel free to reply.

    Changes
    • tags Status-WontFix

New comment