D
D
Dmitry Maslennikov2017-05-06 19:32:22
linux
Dmitry Maslennikov, 2017-05-06 19:32:22

How to remove ^null$ errors from Logwatch?

After switching to HTTPS, Logwatch displays ^null$ errors (connection closed before receiving a response from the server) for all hosts that access the site.
How to remove this error?
When testing through https://2ip.ru/server-response/ it gives:

HTTP/1.1 200 OK

In the Logwatch report itself:
*.** MB transferred in 7645 responses (1xx 7645, 2xx 0, 3xx 0, 4xx 0, 5xx 0)

Answer the question

In order to leave comments, you need to log in

1 answer(s)
D
Dmitry Maslennikov, 2017-05-06
@aprenoir

The problem was the wrong format of the Apache log files. I returned the default log format in the apache2.conf file and everything began to work correctly:

LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\""

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question