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 <jnil...@jala.com> 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 <jnil...@jala.com> wrote: > > Here's what I get for the first part of that: > > * #* netstat -napo | egrep "(:80|:443)" > tcp 0 0 1.2.3.4:43160 23.210.206.246*:443* > ESTABLISHED 1961/(squid-1) off (0.00/0/0) > tcp 0 0 1.2.3.4:59116 107.14.47.80*:80* TIME_WAIT > - timewait (45.97/0/0) > tcp 0 0 1.2.3.4:48181 52.20.156.66*:443* > ESTABLISHED 1961/(squid-1) off (0.00/0/0) > tcp 0 0 1.2.3.4:41114 17.248.129.179*:443* TIME_WAIT > - timewait (58.11/0/0) > tcp 0 0 1.2.3.4:55151 52.32.170.59*:443* > ESTABLISHED 1961/(squid-1) off (0.00/0/0) > tcp 0 0 1.2.3.4:59019 172.217.14.74*:443* TIME_WAIT > - timewait (33.72/0/0) > 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 > LISTEN > > On 4 Oct 2018, at 11:13, Filipe Cifali <cifali.fil...@gmail.com> wrote: > > netstat -napo|egrep "(:80|:443) |grep LISTEN > > > > -- [ ]'s Filipe Cifali Stangler
