Menu

#3 HTTPD level error

v1.0 (example)
closed
nobody
None
5
2019-01-11
2018-10-20
Daniel
No

Since the upgrade from debian jessie to stretch logwatch reports each day under httpd errors a level error. I canot find this error in the error log files. What it is and how can I find this error?

Pakage logwatch has version numer 7.4.3+git20161207-2.

Discussion

  • Josh Soref

    Josh Soref - 2018-11-08

    answering to make it easier for me to find the answer...
    https://sourceforge.net/p/logwatch/discussion/1115928/thread/1ca3abbc/?limit=25

    for more information, you can use:

    logwatch --service http-error --range 'since 1 week ago' --filename - --detail 6
    
     
  • Josh Soref

    Josh Soref - 2018-11-08

    I'm going to try a file named /etc/logwatch/conf/services/http-error.conf with:

    Detail = 6
    $HTTP_Error_MatchFilter = "     \
      if ($LogLevel eq 'notice') {   \
       $ThisLine = "";        \
      }                \
      "
    
     
  • Josh Soref

    Josh Soref - 2018-11-09

    Fwiw, I'm much happier w/ those two changes, I'm planning to make a PR to that effect.

     
  • Bjorn

    Bjorn - 2019-01-11
    • status: open --> closed
     
  • Bjorn

    Bjorn - 2019-01-11

    As mentioned in the link referenced above, the output level can be customized with the Detail parameter. A more universal definition would require both a detail level and a severity level specification, which Logwatch does not provide. But Josh provided the answer on how to customize the output using the existing $HTTP_Error_MatchFilter variable, which is also described, together with $HTTP_Error_ReportFilter, in the conf/services/http-error.conf file. Therefore, it does not appear we need to change the source code.

     

Log in to post a comment.

Monday.com Logo