httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Purvez <pur...@nexar.free-online.co.uk>
Subject Re: [users@httpd] Problem with Apache2 after upgrade from Ubuntu14.04 to 16.04
Date Tue, 18 Apr 2017 15:25:21 GMT
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 <purvez@nexar.free-online.co.uk> 
> <mailto:purvez@nexar.free-online.co.uk>
> Reply: users@httpd.apache.org <mailto:users@httpd.apache.org> 
> <users@httpd.apache.org> <mailto:users@httpd.apache.org>
> Date: 18 April 2017 at 1:35:12 PM
> To: users@httpd.apache.org <mailto:users@httpd.apache.org> 
> <users@httpd.apache.org> <mailto:users@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 <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


Mime
View raw message