-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, 15.11.2004 at 11:04 +, Richard Lyons wrote:
> > > I'm still trying to find a workaround. 'restart' did not work for me.
> > > Doing it by hand from the command line 'stop' followed by 'start' works
> > > reliably, but when I put it in
On Monday 15 November 2004 09:36, Dave Ewart wrote:
> On Sunday, 14.11.2004 at 11:14 +, Richard Lyons wrote:
>
> > On Monday 01 November 2004 12:20, Dave Ewart wrote:
> > > System: Woody, fully up to date, runs Apache
> > >
> > > Recently, after an 'apt-get upgrade', Apache has been dying when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday, 14.11.2004 at 11:14 +, Richard Lyons wrote:
> On Monday 01 November 2004 12:20, Dave Ewart wrote:
> > System: Woody, fully up to date, runs Apache
> >
> > Recently, after an 'apt-get upgrade', Apache has been dying when doing
> a
> >
On Monday 01 November 2004 12:20, Dave Ewart wrote:
> System: Woody, fully up to date, runs Apache
>
> Recently, after an 'apt-get upgrade', Apache has been dying when doing
a
> logrotate. I have identified the source of the problem -
> '/etc/ini.d/apache reload' kills Apache.
>
> So, I've chan
On Thursday 04 November 2004 22:15, Dave Ewart wrote:
> On Thursday, 04.11.2004 at 22:41 +0100, Richard Lyons wrote:
>
> > > The date sounds the same as for me. The actual root of the
problem is
> > > that '/etc/init.d/apache reload' causes Apache to die. That
command
> > is
> > > issued as pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, 04.11.2004 at 22:41 +0100, Richard Lyons wrote:
> > The date sounds the same as for me. The actual root of the problem is
> > that '/etc/init.d/apache reload' causes Apache to die. That command
> is
> > issued as part of the logrotate
On Thursday 04 November 2004 19:26, Dave Ewart wrote:
> On Thursday, 04.11.2004 at 16:51 +, Jon Dowland wrote:
>
> > On Mon, 1 Nov 2004 12:35:34 +, Dave Ewart <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Nothing abnormal in the logs. There is the 'SIGUSR1 received.
> > > Doing graceful restar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, 04.11.2004 at 16:51 +, Jon Dowland wrote:
> On Mon, 1 Nov 2004 12:35:34 +, Dave Ewart <[EMAIL PROTECTED]>
> wrote:
>
> > Nothing abnormal in the logs. There is the 'SIGUSR1 received.
> > Doing graceful restart' message when 'rel
On Thursday 04 November 2004 16:51, Jon Dowland wrote:
> On Mon, 1 Nov 2004 12:35:34 +, Dave Ewart <[EMAIL PROTECTED]>
wrote:
>
> > Nothing abnormal in the logs. There is the 'SIGUSR1 received.
Doing
> > graceful restart' message when 'reload' is triggered, which appears
> > whether the pr
On Mon, 1 Nov 2004 12:35:34 +, Dave Ewart <[EMAIL PROTECTED]> wrote:
> Nothing abnormal in the logs. There is the 'SIGUSR1 received. Doing
> graceful restart' message when 'reload' is triggered, which appears
> whether the process dies or not ...
When did this start happening? It started fo
On Monday 01 November 2004 12:35, Dave Ewart wrote:
> On Monday, 01.11.2004 at 20:28 +0800, Robert Vangel wrote:
>
> > I can't say that this has happened to me really.
> >
> > What do error logs give? Do you get any abnormal output from
logrotate?
> > Or, does it just die because it *seems* it wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, 01.11.2004 at 13:22 +, Jon Dowland wrote:
> Not sure if this is related but my apache on a woody server keeps
> dying and /tmp filling up. Only recently experienced this, think it
> might be related to PHP4. Do you have php4 linked into
Not sure if this is related but my apache on a woody server keeps
dying and /tmp filling up. Only recently experienced this, think it
might be related to PHP4. Do you have php4 linked into your apache?
Are you on a woody system?
--
Jon Dowland
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, 01.11.2004 at 20:28 +0800, Robert Vangel wrote:
> I can't say that this has happened to me really.
>
> What do error logs give? Do you get any abnormal output from logrotate?
> Or, does it just die because it *seems* it wants to.
Nothing
I can't say that this has happened to me really.
What do error logs give? Do you get any abnormal output from logrotate?
Or, does it just die because it *seems* it wants to.
I've had similar problems due to very stale processes (and even after
stop haven't killed and it's just doing lots of "killa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
System: Woody, fully up to date, runs Apache
Recently, after an 'apt-get upgrade', Apache has been dying when doing a
logrotate. I have identified the source of the problem -
'/etc/ini.d/apache reload' kills Apache.
So, I've changed it to '/etc/ini.
16 matches
Mail list logo