Il 09/09/2015 07:15, Paolo Cavallini ha scritto:
> am I the only one having this problem? I'm pretty much stuck - if not
> here, is there another place to seek for help?
purged once more all apache2 related packages, removed all apache2
remaining files, now all ok.
sorry for the noise, and thanks
Il 09/09/2015 07:32, Alexis ha scritto:
> Given Apache is unable to open the log file, i'm wondering if Apache is
> trying to store logs on a full partition?
no full partitions here.
standard conf:
ErrorLog ${APACHE_LOG_DIR}/error.log
ls -l /var/log/apache2/error.log
-rw-rw 1 root ww
Paolo Cavallini writes:
Il 08/09/2015 14:27, Paolo Cavallini ha scritto:
Il 08/09/2015 14:12, Reco ha scritto:
It there anything useful in apache's error.log? Maybe failed
dpkg configuration script left httpd.conf in invalid state, or
something.
Unfortunately the log is empty (a previous
Il 08/09/2015 14:27, Paolo Cavallini ha scritto:
> Il 08/09/2015 14:12, Reco ha scritto:
>
>> It there anything useful in apache's error.log? Maybe failed dpkg
>> configuration script left httpd.conf in invalid state, or something.
>
> Unfortunately the log is empty (a previous error showed apach
Il 08/09/2015 14:12, Reco ha scritto:
> It there anything useful in apache's error.log? Maybe failed dpkg
> configuration script left httpd.conf in invalid state, or something.
Unfortunately the log is empty (a previous error showed apache was
unable to open it, so I changed ownership to root:www
Hi.
On Tue, Sep 08, 2015 at 11:18:31AM +0200, Paolo Cavallini wrote:
> Il 08/09/2015 10:59, Reco ha scritto:
>
> > Wait. You mean that you've purged lighttpd first, and *then* 'ss -lnpt'
> > shows that lighttpd is still running? Seems like a bug to me.
>
> Sorry I was unclear: I confirmed light
Il 08/09/2015 10:59, Reco ha scritto:
> Wait. You mean that you've purged lighttpd first, and *then* 'ss -lnpt'
> shows that lighttpd is still running? Seems like a bug to me.
Sorry I was unclear: I confirmed lighttpd was occupying port 80, then I
removed it, and I restarted apache2, without succ
Hi.
On Tue, Sep 08, 2015 at 10:36:45AM +0200, Paolo Cavallini wrote:
> Il 08/09/2015 10:21, Reco ha scritto:
>
> > Please post the output of 'ss -lnpt'. Someone took port 80 on this host
> > already and this is the source of your trouble.
>
> Oh, you're right: lighttp seems the culprit.
> Howev
Il 08/09/2015 10:21, Reco ha scritto:
> Please post the output of 'ss -lnpt'. Someone took port 80 on this host
> already and this is the source of your trouble.
Oh, you're right: lighttp seems the culprit.
However, purging it does not solve the issue.
What else?
Thanks.
===
root@440:/usr/local/s
Hi.
On Tue, Sep 08, 2015 at 09:08:26AM +0200, Paolo Cavallini wrote:
> Sep 08 08:30:30 440 apache2[5689]: (98)Address already in use: AH00072:
> make_sock: could not bind to address [::]:80
> Sep 08 08:30:30 440 apache2[5689]: (98)Address already in use: AH00072:
> make_sock: could not bind to a
Hi all,
on an updated Sid box I have trouble with apache:
==
service apache2 reload
Job for apache2.service failed because the control process exited with
error code. See "systemctl status apache2.service" and "journalctl -xe"
for deta
11 matches
Mail list logo
