Because something else could be listening on those ports, preventing httpd from starting. This is not so uncommon to happen. httpd is complaining on listening to both IPv4 and IPv6, so maybe a greedy virtualhost is trying to map more addresses than it should?On Thu, Oct 4, 2018 at 3:59 PM Jack M. Nilles <jnilles@xxxxxxxx> wrote:Of course, since Apache isn't running -- failed to start -- why would I get any LISTEN ports?On 4 Oct 2018, at 11:46, Jack M. Nilles <jnilles@xxxxxxxx> wrote:Here's what I get for the first part of that:# netstat -napo | egrep "(:80|:443)"tcp 0 0 1.2.3.4:52752 216.17.8.47:443 ESTABLISHED 710/java keepalive (320.48/0/0)and I get no return for # netstat -napo | egrep "(:80|:443)" | grep LISTENOn 4 Oct 2018, at 11:13, Filipe Cifali <cifali.filipe@xxxxxxxxx> wrote:netstat -napo|egrep "(:80|:443) |grep LISTEN
--[ ]'s
Filipe Cifali Stangler