[lug] Concurrent apache's
Atkinson, Chip
CAtkinson at Circadence.com
Fri Sep 15 14:06:06 MDT 2000
I just did man httpd on a machine that had it. :-)
I think it's apache.pm missing or something. That's probably the biggest
clue. Any reason the other httpd isn't giving that error message?
-----Original Message-----
From: Ken Kinder [mailto:ken at kenkinder.com]
Sent: Friday, September 15, 2000 2:01 PM
To: 'lug at lug.boulder.co.us'
Subject: RE: [lug] Concurrent apache's
I didn't see that in the list of options. Is there a more complete list
than what I'm getting from -h?
It had the same behavior though. :/
--
Ken Kinder
www.kenkinder.com
On Fri, 15 Sep 2000, Atkinson, Chip wrote:
> Try running it with the -X option. This keeps it from detaching and you
may
> get a better idea of what's going on. It may be core dumping because you
> are trying to load a module that isn't around or dies.
>
> Chip
>
> -----Original Message-----
> From: Ken Kinder [mailto:ken at kenkinder.com]
> Sent: Friday, September 15, 2000 1:46 PM
> To: 'lug at lug.boulder.co.us'
> Subject: RE: [lug] Concurrent apache's
>
>
> There's nothing in messages. Apache's own error_log has this when it tries
> to start up, but it's what you'd expect:
>
> [Fri Sep 15 13:44:54 2000] [warn] pid file
> /usr/local/apache/logs/httpd.pid overwritten -- Unclean shutdown of
> previous Apache run?
>
>
> --
> Ken Kinder
> www.kenkinder.com
>
> On Fri, 15 Sep 2000, Atkinson, Chip wrote:
>
> > That's weird. Can you tail -f the log files? Perhaps it'll be in
> > /var/log/messages as to why it's dying.
> >
> > -----Original Message-----
> > From: Ken Kinder [mailto:ken at kenkinder.com]
> > Sent: Friday, September 15, 2000 1:38 PM
> > To: 'lug at lug.boulder.co.us'
> > Subject: RE: [lug] Concurrent apache's
> >
> >
> > That's exactly what I'm doing. It just mysteriously dies. The test port
is
> > supposed to 8880
> >
> > --
> > Ken Kinder
> > www.kenkinder.com
> >
> > On Fri, 15 Sep 2000, Atkinson, Chip wrote:
> >
> > > You can start apache with the -d for the serverroot, the -f to specify
> the
> > > configuration file, and in the different configuration files, you can
> > > specify which port to listen to with the Listen directive to tell what
> > port
> > > to listen on. We did this to use the same machine for testing as well
> as
> > > production on the corp. intra net. The test httpd listened on port 81
> and
> > > the regular production listened on port 80.
> > >
> > > Chip
> > >
> > > -----Original Message-----
> > > From: Ken Kinder [mailto:ken at kenkinder.com]
> > > Sent: Friday, September 15, 2000 1:21 PM
> > > To: lug at lug.boulder.co.us
> > > Subject: [lug] Concurrent apache's
> > >
> > >
> > > Apache seems to die if you try to have several instances of it running
> on
> > > different ports, different config files, etc. Does anyone know how to
> work
> > > around that?
> > >
> > > --
> > > Ken Kinder
> > > www.kenkinder.com
> > >
> > >
> > > _______________________________________________
> > > Web Page: http://lug.boulder.co.us
> > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > >
> > > _______________________________________________
> > > Web Page: http://lug.boulder.co.us
> > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > >
> >
> >
> > _______________________________________________
> > Web Page: http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >
> > _______________________________________________
> > Web Page: http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >
>
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>
_______________________________________________
Web Page: http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
More information about the LUG
mailing list