Richard G
Verified User
Several servers configured the same way, the /var/log/httpd/error.log starts the same way the first 7 lines, but then.... this is what's happening on 1 server, no "normal" error logs, only error logs files flooded with this:
So it looks as something is using the host command wrongly and this is the result.
It's flooding the error log and it's only happening on this one server.
How can I find out where it's coming from and to stop this kind of log from which you can learn nothing except that something is wrong somewhere but no pointing to where or what?
Code:
[Sun Aug 13 04:06:11.004031 2017] [ssl:warn] [pid 26813] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Sun Aug 13 04:06:11.004339 2017] [ssl:warn] [pid 26813] AH01909: shared.domain:443:0 server certificate does NOT include an ID which matches the server name
[Sun Aug 13 04:06:11.004644 2017] [ssl:warn] [pid 26813] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Sun Aug 13 04:06:11.004716 2017] [lbmethod_heartbeat:notice] [pid 26813] AH02282: No slotmem from mod_heartmonitor
[Sun Aug 13 04:06:11.004762 2017] [:notice] [pid 26813] mod_ruid2/0.9.8 enabled
[Sun Aug 13 04:06:11.314582 2017] [mpm_prefork:notice] [pid 26813] AH00163: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips PHP/5.6.31 configured -- resuming normal operations
[Sun Aug 13 04:06:11.318640 2017] [core:notice] [pid 26813] AH00094: Command line: '/usr/sbin/httpd'
Usage: host [-aCdlriTwv] [-c class] [-N ndots] [-t type] [-W time]
[-R number] [-m flag] hostname [server]
-a is equivalent to -v -t ANY
-c specifies query class for non-IN data
-C compares SOA records on authoritative nameservers
-d is equivalent to -v
-l lists all hosts in a domain, using AXFR
-i IP6.INT reverse lookups
-N changes the number of dots allowed before root lookup is done
-r disables recursive processing
-R specifies number of retries for UDP packets
-s a SERVFAIL response should stop query
-t specifies the query type
-T enables TCP/IP mode
-v enables verbose output
-w specifies to wait forever for a reply
-W specifies how long to wait for a reply
-4 use IPv4 query transport only
-6 use IPv6 query transport only
-m set memory debugging flag (trace|record|usage)
Usage: host [-aCdlriTwv] [-c class] [-N ndots] [-t type] [-W time]
[-R number] [-m flag] hostname [server]
-a is equivalent to -v -t ANY
-c specifies query class for non-IN data
-C compares SOA records on authoritative nameservers
-d is equivalent to -v
-l lists all hosts in a domain, using AXFR
-i IP6.INT reverse lookups
-N changes the number of dots allowed before root lookup is done
-r disables recursive processing
-R specifies number of retries for UDP packets
-s a SERVFAIL response should stop query
-t specifies the query type
-T enables TCP/IP mode
-v enables verbose output
-w specifies to wait forever for a reply
-W specifies how long to wait for a reply
-4 use IPv4 query transport only
-6 use IPv6 query transport only
-m set memory debugging flag (trace|record|usage)
So it looks as something is using the host command wrongly and this is the result.
It's flooding the error log and it's only happening on this one server.
How can I find out where it's coming from and to stop this kind of log from which you can learn nothing except that something is wrong somewhere but no pointing to where or what?