Eureka!! I found a new or recently revised file: /etc/apache2/listen.conf. That
had a pair of listen lines under NameVirtualHost that I commented out.
Restarting apache then produced a running server.
Thanks, guys, for your patience and help! I will keep your emails in my
Whatthehell? folder fo
vhosts do not bind to ports - the Listen directive does.
On Thu, Oct 4, 2018 at 3:17 PM Filipe Cifali
wrote:
> 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,
On 04 Oct 2018, at 13:20, Filipe Cifali wrote:
> And the docs, this project is open source, we can change (or rather, propose
> changes) to documentation anytime we want.
Sure, but first you have to figure out the multiple layers of complexity in the
current docs.
--
Boy, it sure would be ni
It's a bit strange to say that considering there is a page covering the
changes from 2.2 to 2.4:
https://httpd.apache.org/docs/2.4/upgrading.html
And the docs, this project is open source, we can change (or rather,
propose changes) to documentation anytime we want.
On Thu, Oct 4, 2018 at 3:54 PM
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.
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 wrote:
>
> Here's what I get for the first part of that:
>
> # netstat -napo | egrep "(:80|:443)"
> tcp0 0 1.2.3.4:43160 23.210.206.246:443
On 04 Oct 2018, at 11:50, Filipe Cifali wrote:
> You want to use a CustomLog for virtualhost config to gather the most info
> you can from the request:
>
> https://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog
Ugh. That is a terrible bit of documentation written by and for peo
Here's what I get for the first part of that:
# netstat -napo | egrep "(:80|:443)"
tcp0 0 1.2.3.4:43160 23.210.206.246:443 ESTABLISHED
1961/(squid-1) off (0.00/0/0)
tcp0 0 1.2.3.4:59116 107.14.47.80:80 TIME_WAIT -
timewait
On Thu, Oct 4, 2018 at 2:01 PM Jack M. Nilles wrote:
>
> Here's what I get:
>
> # lsof -i:443
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> java 710 root 245u IPv6 49204 0t0 TCP
> server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED)
> squid 1961 squi
Jack, don't confuse INCOMING/OUTGOING connections with LISTEN.
Seems this site is gathering some info from other sites, you can see the
commands running *Java* and *squid*, if you have netstat installed
(otherwise just install it because it's super flexible and easy to use?)
run a `netstat -napo|e
Here's what I get:
# lsof -i:443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 710 root 245u IPv6 49204 0t0 TCP
server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED)
squid 1961 squid 13u IPv4 19134 0t0 TCP server.site1.com
55151->ec2-52-32
You want to use a CustomLog for virtualhost config to gather the most info
you can from the request:
https://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog
Also, read the *Context* so you know where you can use them:
https://httpd.apache.org/docs/2.4/mod/core.html#LogLevel
On
On 03 Oct 2018, at 18:27, Filipe Cifali wrote:
> you can for example turn log level to debug and access the site, tailing the
> logs should provide some information about what is breaking.
Is it possible to set the log level just for a virtual host? I thought that was
a server-wide setting. I t
http://wiki.apache.org/httpd/CouldNotBindToAddress will help you
troubleshoot that error.
On Wed, Oct 3, 2018 at 8:21 PM Filipe Cifali
wrote:
> Jack, the logs saying you can't bind the addresses:
>
> Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
> AH00072: make_sock: co
14 matches
Mail list logo
