osdir.com

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [users@httpd] 403 error upon upgrade


http://wiki.apache.org/httpd/CouldNotBindToAddress will help you troubleshoot that error.

On Wed, Oct 3, 2018 at 8:21 PM Filipe Cifali <cifali.filipe@xxxxxxxxx> 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: could not bind to address [::]:443
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Oct 03 14:44:01 donner start_apache2[3998]: AH00015: Unable to open logs

This are the important bits, also, you should set error_log and put debug level on it if you can't find out why.

On Wed, Oct 3, 2018 at 7:15 PM Jack M. Nilles <jnilles@xxxxxxxx> wrote:
A few minutes later I get:

apache2.service - The Apache Webserver
   Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled)
   Active: failed (Result: exit-code) since Wed 2018-10-03 15:10:27 PDT; 38s ago
  Process: 5147 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=0/SUCCESS)
  Process: 5140 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE)
 Main PID: 5140 (code=exited, status=1/FAILURE)

This after I tracked down some port interference.





--
[ ]'s

Filipe Cifali Stangler