httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abrar hazarika <>
Subject Re: httpd failed (weird pid file)
Date Mon, 15 Jul 2002 06:15:02 GMT
Thanks Mark,

The apache server started ok with pid 7150 but it also
created in /var/run. With loglevel
'debug' it gave the following in error_log. I think
running this way will again cause the server to fail.
Though it is not a production server but is only for
inhouse s/w development with php and mysql, it is
still worrying me. 

Can you guide me more?

And how do i start httpd with -X option. i tried from
/etc/rc.d/init.d but it does not take any option only
start,restart etc.

Thanks again   

[Mon Jul 15 11:21:46 2002] [info] created shared
memory segment #393218
[Mon Jul 15 11:21:46 2002] [notice] Apache/1.3.19
(Unix)  (Red-Hat/Linux) mod_ssl/2.8.1 OpenSSL/0.9.6
DAV/1.0.2 PHP/4.2.1 mod_perl/1.24_01 configured --
resuming normal operations
[Mon Jul 15 11:21:46 2002] [notice] suEXEC mechanism
enabled (wrapper: /usr/sbin/suexec)
[Mon Jul 15 11:21:46 2002] [info] Server built: Mar 29
2001 12:52:37 

--- Mark Mentovai <> wrote: >
Abrar Hazarika wrote:
> > This is my first post to this group.
> > Apache 1.3.19-5 was running fine on RH7.1 machine.
> But
> > from yesterday it failed to start. There is no
> error
> > on the error_log file. In the /var/run it shows as
> > where xxxx=number which i
> believe is
> > the pid. 
> > Searching through google i found a bit which says
> 'mm'
> > relates to shared memory. But didn't help me much.
> is used as a semaphore for certain
> shared memory 
> operations when using a version of Apache built with
> the extended API 
> and common configurations of the MM library.  EAPI
> is added to Apache 
> in order to support mod_ssl.
> Sometimes, Apache will exit in such a way that this
> file (and 
> potentially other files) will not be cleaned up. 
> They're safe to 
> remove, but their presence alone doesn't tell you
> much specifically 
> about why Apache is exiting or refusing to start.
> Apache may be exiting before it has an error log
> available.  Does it 
> print anything to stderr when you attempt to start
> it yourself?  It's 
> also possible that you have an inappropriate
> ErrorLog or LogLevel 
> setting in your configuration file, try "LogLevel
> info" or possibly 
> even "debug".  You might also consider starting
> httpd with the -X 
> argument in addition to the arguments that you
> normally use; this will 
> cause debugging messages to be printed on stderr and
> will prevent the 
> server from forking.
> Mark
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Want to sell your car? advertise on Yahoo Autos Classifieds. It's Free!!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message