You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Purvez <pu...@nexar.free-online.co.uk> on 2017/04/18 11:35:12 UTC
[users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04 to 16.04
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
\u25cf apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
\u2514\u2500apache2-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
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: AH00015:
Unable to open logs
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: Action
'start' failed.
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: The Apache
error log may have more information.
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: *
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: * Stopping
Apache httpd web server apache2
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: *
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 systemd[1]: Started LSB:
Apache2 web server.
purvez@127:~$
The MAIN question is : Is Apache started and functioning or is it
inactive (dead)?
The last line of the output suggests that it is working but the 5th /
6th line from the top suggests the opposite.
The errorlog is blank and the accesslog is blank as well since the day
of the upgrade.
===========================
Thanks in advance
Purvez
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04 to 16.04
Posted by Marat Khalili <mk...@rqc.ru>.
> Given where I AM what would you suggest would be the best course of action to get back to a working system please?
As was already suggested, run:
sudo netstat -tpln
to see what program occupies port 80. Also try:
ps -AFH
to see if other instances of Apache are already running. Compare their PIDs with those reported by:
systemctl status apache2
If you don't know how to interpret the outputs post them here.
If you already established that e.g. nginx is to blame, decide what to do with it, e.g. daisy-chain web servers, bind them to different IPs or leave only one.
--
With Best Regards,
Marat Khalili
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Purvez <pu...@nexar.free-online.co.uk>.
Hi Eric
The info I'm getting from Phusion is that Standalone Passenger only uses
port 3000 by default or whatever else you stipulate at start time.
However they are helping me decipher why nginx 'appears' to be grabbing
port 80. Once I have an understanding of 'that bit' maybe I'll have a
better understanding of what to do next.
I do agree that currently there appears to be a squabble about port 80
between the servers. Once I get to the bottom of it I will post my
findings here so that others may benefit from my (painful) experience. LOL!!
On 18/04/17 17:04, Eric Covener wrote:
> On Tue, Apr 18, 2017 at 12:01 PM, Purvez <pu...@nexar.free-online.co.uk> wrote:
>> Given where I AM what would you suggest would be the best course of action
>> to get back to a working system please?
> Decide which http server will listen on port 80? Whoever gets port 80
> may have to proxy to the other server on an alt port.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Eric Covener <co...@gmail.com>.
On Tue, Apr 18, 2017 at 12:01 PM, Purvez <pu...@nexar.free-online.co.uk> wrote:
> Given where I AM what would you suggest would be the best course of action
> to get back to a working system please?
Decide which http server will listen on port 80? Whoever gets port 80
may have to proxy to the other server on an alt port.
--
Eric Covener
covener@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Purvez <pu...@nexar.free-online.co.uk>.
Hi Marat
Many thanks for your input. Yes 14.04 was an upgrade from 13.10 ...BUT
I had tested it and it DID WORK!! I must admit that I didn't look at
the apache versions between 13.10 and 14.04 on ubuntu. (I really had no
'need' to...as everything worked)
Given where I AM what would you suggest would be the best course of
action to get back to a working system please?
Regards
Purvez
On 18/04/17 16:49, Marat Khalili wrote:
> Versions of Apache used by 14.04 and 16.04 are in fact very close:
> 2.4.7 and 2.4.18, I doubt their configurations are so much different
> (unless 14.04 was also an upgrade, since 13.10 used 2.2.x AFAIR).
> Breakage in the way Apache is started (upstart vs systemd) is much
> more probable. Reinstallation of Apache might not even fix this.
>
> Moreover, Apache clearly complains on ports being already in use. It'd
> investigate what uses the ports before doing anything else. It could
> even be Apache itself (different instance started independently).
>
>
> --
>
> With Best Regards,
> Marat Khalili
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Marat Khalili <mk...@rqc.ru>.
Versions of Apache used by 14.04 and 16.04 are in fact very close: 2.4.7
and 2.4.18, I doubt their configurations are so much different (unless
14.04 was also an upgrade, since 13.10 used 2.2.x AFAIR). Breakage in
the way Apache is started (upstart vs systemd) is much more probable.
Reinstallation of Apache might not even fix this.
Moreover, Apache clearly complains on ports being already in use. It'd
investigate what uses the ports before doing anything else. It could
even be Apache itself (different instance started independently).
--
With Best Regards,
Marat Khalili
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Mitchell Krog Photography <mi...@gmail.com>.
Trust me. it’s the safest way to know you are starting off clean and have
no remnants that didn’t upgrade properly, there were a number of
deprecations from old to new Apache and they do not upgrade nicely.
And it really does not take that long, it should take you (depending on how
many sites) that entire fresh upgrade in under an hour.
For me when I had to do it after one upgrade from 14 > 16 I had 18 sites,
it took me barely an hour and everything was fresh and working properly,
then I moved to Nginx a few months later but that was for other reasons.
Tell me about it ….. the things we have to do !!! LOL
But just bite the bullet and start fresh, then you know you are fresh and
squeaky clean
Cheers
Mitch
From: Purvez <pu...@nexar.free-online.co.uk>
<pu...@nexar.free-online.co.uk>
Reply: users@httpd.apache.org <us...@httpd.apache.org>
<us...@httpd.apache.org>
Date: 18 April 2017 at 5:25:21 PM
To: users@httpd.apache.org <us...@httpd.apache.org> <us...@httpd.apache.org>
Subject: Re: [users@httpd] Problem with Apache2 after upgrade from
Ubuntu14.04 to 16.04
Hi Mitchell
Many thanks for your response. I'm coming to the same conclusion as you.
Best to cut my losses and rebuild Apache and PHP....but I HATE not knowing
what went wrong. So...I'm going to spend some time getting to the bottom
of the problem...whilst being pragmatic and building my production server
with apache and php again to get back to 'real life'!! Ugh the things we
have to do to survive in this game!! LOL.
On 18/04/17 12:59, Mitchell Krog Photography wrote:
My experience with upgrading from 14.04 to 16.04 is apache does not upgrade
well at all, had it happen on several servers already in the past.
I would suggest backup your entire etc/apache2 folder or rename it
/etc/apache_backup/
Then uninstall apache and purge it, uninstall PHP and purge it and then
reinstall both Apache and PHP
Then you will get a clean Apache with PHP 7, then move your sites back into
/etc/apache2/sites-available/ one at a time, enable them one at a time and
test as you go along.
Good luck
From: Purvez <pu...@nexar.free-online.co.uk>
<pu...@nexar.free-online.co.uk>
Reply: users@httpd.apache.org <us...@httpd.apache.org>
<us...@httpd.apache.org>
Date: 18 April 2017 at 1:35:12 PM
To: users@httpd.apache.org <us...@httpd.apache.org> <us...@httpd.apache.org>
Subject: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
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
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: AH00015: Unable
to open logs
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: Action 'start'
failed.
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: The Apache error
log may have more information.
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: *
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: * Stopping
Apache httpd web server apache2
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: *
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 systemd[1]: Started LSB:
Apache2 web server.
purvez@127:~$
The MAIN question is : Is Apache started and functioning or is it inactive
(dead)?
The last line of the output suggests that it is working but the 5th / 6th
line from the top suggests the opposite.
The errorlog is blank and the accesslog is blank as well since the day of
the upgrade.
===========================
Thanks in advance
Purvez
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Purvez <pu...@nexar.free-online.co.uk>.
Hi Mitchell
Many thanks for your response. I'm coming to the same conclusion as
you. Best to cut my losses and rebuild Apache and PHP....but I HATE not
knowing what went wrong. So...I'm going to spend some time getting to
the bottom of the problem...whilst being pragmatic and building my
production server with apache and php again to get back to 'real
life'!! Ugh the things we have to do to survive in this game!! LOL.
On 18/04/17 12:59, Mitchell Krog Photography wrote:
> My experience with upgrading from 14.04 to 16.04 is apache does not
> upgrade well at all, had it happen on several servers already in the past.
>
> I would suggest backup your entire etc/apache2 folder or rename it
> /etc/apache_backup/
>
> Then uninstall apache and purge it, uninstall PHP and purge it and
> then reinstall both Apache and PHP
>
> Then you will get a clean Apache with PHP 7, then move your sites back
> into /etc/apache2/sites-available/ one at a time, enable them one at a
> time and test as you go along.
>
> Good luck
>
>
> From: Purvez <pu...@nexar.free-online.co.uk>
> <ma...@nexar.free-online.co.uk>
> Reply: users@httpd.apache.org <ma...@httpd.apache.org>
> <us...@httpd.apache.org> <ma...@httpd.apache.org>
> Date: 18 April 2017 at 1:35:12 PM
> To: users@httpd.apache.org <ma...@httpd.apache.org>
> <us...@httpd.apache.org> <ma...@httpd.apache.org>
> Subject: [users@httpd] Problem with Apache2 after upgrade from
> Ubuntu14.04 to 16.04
>
>> 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
>> \u25cf apache2.service - LSB: Apache2 web server
>> Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
>> Drop-In: /lib/systemd/system/apache2.service.d
>> \u2514\u2500apache2-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 <http://0.0.0.0:80>
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: no
>> listening sockets available, shutting down
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: AH00015:
>> Unable to open logs
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: Action
>> 'start' failed.
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: The Apache
>> error log may have more information.
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: *
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: *
>> Stopping Apache httpd web server apache2
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: *
>> Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 systemd[1]: Started LSB:
>> Apache2 web server.
>> purvez@127:~$
>>
>>
>>
>> The MAIN question is : Is Apache started and functioning or is it
>> inactive (dead)?
>>
>> The last line of the output suggests that it is working but the 5th /
>> 6th line from the top suggests the opposite.
>>
>> The errorlog is blank and the accesslog is blank as well since the
>> day of the upgrade.
>> ===========================
>> Thanks in advance
>>
>> Purvez
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Mitchell Krog Photography <mi...@gmail.com>.
My experience with upgrading from 14.04 to 16.04 is apache does not upgrade
well at all, had it happen on several servers already in the past.
I would suggest backup your entire etc/apache2 folder or rename it
/etc/apache_backup/
Then uninstall apache and purge it, uninstall PHP and purge it and then
reinstall both Apache and PHP
Then you will get a clean Apache with PHP 7, then move your sites back into
/etc/apache2/sites-available/ one at a time, enable them one at a time and
test as you go along.
Good luck
From: Purvez <pu...@nexar.free-online.co.uk>
<pu...@nexar.free-online.co.uk>
Reply: users@httpd.apache.org <us...@httpd.apache.org>
<us...@httpd.apache.org>
Date: 18 April 2017 at 1:35:12 PM
To: users@httpd.apache.org <us...@httpd.apache.org> <us...@httpd.apache.org>
Subject: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
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
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: AH00015: Unable
to open logs
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: Action 'start'
failed.
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: The Apache error
log may have more information.
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6978]: *
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: * Stopping
Apache httpd web server apache2
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 apache2[6997]: *
Apr 13 10:01:02 127.0.1.1purvez-Aspire-5750 systemd[1]: Started LSB:
Apache2 web server.
purvez@127:~$
The MAIN question is : Is Apache started and functioning or is it inactive
(dead)?
The last line of the output suggests that it is working but the 5th / 6th
line from the top suggests the opposite.
The errorlog is blank and the accesslog is blank as well since the day of
the upgrade.
===========================
Thanks in advance
Purvez
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Purvez <pu...@nexar.free-online.co.uk>.
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@nexar.free-online.co.uk
> <ma...@nexar.free-online.co.uk>>:
>
> 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
> <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
> \u25cf apache2.service - LSB: Apache2 web server
> Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
> Drop-In: /lib/systemd/system/apache2.service.d
> \u2514\u2500apache2-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 <http://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
>
Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04
to 16.04
Posted by Luca Toscano <to...@gmail.com>.
Hi!
2017-04-18 13:35 GMT+02:00 Purvez <pu...@nexar.free-online.co.uk>:
> 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