Re: Problem with Apache2 after upgrade from Ubuntu14.04 to 16.04

[Purvez <purvez@xxxxxxxxxxxxxxxxxxxxxxx>]

Hi Luca

Many thanks for your quick response.  I think you have identified the problem.  I am running an ROR website with Phusion Passenger Standalone to serve it via reverse proxy.  Under 14.04 as far as I can tell Passenger Standalone did not use any outside 'help'.  However their latest version seems to be running nginx core as part of Standalone and I think it is nginx that is grabbing port 80. 

I'm going to go back to Phusion and explain the problem to them and ask for a work around.

I will report back here once I have an answer.

Thanks again

Purvez

On 18/04/17 12:45, Luca Toscano wrote:

Hi!

2017-04-18 13:35 GMT+02:00 Purvez <purvez@xxxxxxxxxxxxxxxxxxxxxxx>:

Hi

Newbie to the forum here so I hope I'm doing this right.  If not please would someone guide me.  Thx in advance.

As the subject line says Apache2 is not working at all / satisfactorily since the Ubuntu upgrade.  The details follow:

===========================

Here is my full post on askubuntu:

http://askubuntu.com/questions/904042/upgrade-to-16-04-lts-has-broken-apache

Currently the biggest help I could get would be if someone would decipher what the following output means when I do :

systemctl status apache2.service

output:
===============

Code:

purvez@127:~$ systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─apache2-systemd.conf
   Active: inactive (dead) since Thu 2017-04-13 10:01:02 BST; 11s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 6997 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
  Process: 6978 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)

Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: no listening sockets available, shutting down

It seems that you have another process holding TCP port 80, so you need to kill/stop it first. You can use something like netstat -nlpt (needs super user to list all the info in this case) to find your target.

Hope that helps!

Luca