You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Radhika Sambamurti <ra...@yahoo.com> on 2002/03/21 15:55:11 UTC
Apache pid keeps changing
Hi,
I am running apache 1.3.20 and mentioned previously that
the apache pid keeps changing. from my monitoring script I
found that apache's pid changed sometime today between 8:15
and 8:45. The consistent message that keeps appearing is as
below: the fcntl: F_SETLKW....
[Thu Mar 21 08:36:15 2002] [emerg] (9)Bad file number:
fcntl: F_SETLKW: Error getting accept lock, exiting!
Perhaps you need to use the LockFile directive to place
your lock file on a local disk!
[Thu Mar 21 08:36:15 2002] [alert] Child 19138 returned a
Fatal error...
Apache is exiting!
This server is not running any nfs file system and apache
was not configured with the lockfile directive. We are
running jrun on jre. could any of this be causing the
apache pid to change. I have looked at all the cron jobs
and apart from system maintenance, there is nothing
affecting apache.
Any help will be appreciated.
Thanks,
Radhika
[Thu Mar 21 08:19:56 2002] [error] mod_ssl: SSL handshake
interrupted by system [Hint: Stop button pressed in
browser?!] (System error follows)
[Thu Mar 21 08:19:56 2002] [error] mod_ssl: SSL handshake
interrupted by system [Hint: Stop button pressed in
browser?!] (System error follows)
[Thu Mar 21 08:19:56 2002] [error] System: Connection reset
by peer (errno: 131)
[Thu Mar 21 08:19:56 2002] [error] System: Connection reset
by peer (errno: 131)
[Thu Mar 21 08:33:25 2002] [notice] child pid 18584 exit
signal Segmentation Fault (11)
[Thu Mar 21 08:33:34 2002] [notice] child pid 18483 exit
signal Segmentation Fault (11)
[Thu Mar 21 08:33:44 2002] [notice] child pid 18575 exit
signal Segmentation Fault (11)
[Thu Mar 21 08:35:00 2002] [notice] child pid 17802 exit
signal Segmentation Fault (11)
[Thu Mar 21 08:35:00 2002] [notice] child pid 18482 exit
signal Segmentation Fault (11)
[Thu Mar 21 08:35:04 2002] [notice] child pid 18576 exit
signal Segmentation Fault (11)
[Thu Mar 21 08:36:15 2002] [emerg] (9)Bad file number:
fcntl: F_SETLKW: Error getting accept lock, exiting!
Perhaps you need to use the LockFile directive to place
your lock file on a local disk!
[Thu Mar 21 08:36:15 2002] [alert] Child 19138 returned a
Fatal error...
Apache is exiting!
=====
It's all a matter of perspective. You can choose your view by choosing where to stand.
--Larry Wall
__________________________________________________
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards�
http://movies.yahoo.com/
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Apache pid keeps changing
Posted by Owen Boyle <ob...@bourse.ch>.
Radhika Sambamurti wrote:
>
> Hi,
> I am running apache 1.3.20 and mentioned previously that
> the apache pid keeps changing. from my monitoring script I
> found that apache's pid changed sometime today between 8:15
> and 8:45. The consistent message that keeps appearing is as
> below: the fcntl: F_SETLKW....
>
> [Thu Mar 21 08:36:15 2002] [emerg] (9)Bad file number:
> fcntl: F_SETLKW: Error getting accept lock, exiting!
> Perhaps you need to use the LockFile directive to place
> your lock file on a local disk!
> [Thu Mar 21 08:36:15 2002] [alert] Child 19138 returned a
> Fatal error...
> Apache is exiting!
>
> This server is not running any nfs file system and apache
> was not configured with the lockfile directive. We are
> running jrun on jre. could any of this be causing the
> apache pid to change. I have looked at all the cron jobs
> and apart from system maintenance, there is nothing
> affecting apache.
Did you read the docs on LockFile? It has a default so you get it even
if you don't define it... And you must have your lockfile on a local
disk. Is your logs directory on a network (not necessarily nfs-mounted)?
What is happening is that apache is dying because of this and then being
restarted. That is why the PID is changed. You need to stop it dying by
fixing the problem with the lockfile.
Rgds,
owen Boyle.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org