Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Nov 2005 21:09:17 +0000
From:      markzero <mark@darklogik.org>
To:        freebsd-questions@freebsd.org
Subject:   Jailed Apache1.3, processes won't die
Message-ID:  <20051127210917.GA74091@logik.internal.network>

next in thread | raw e-mail | index | archive | help

--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi.

I'm using a standard install of FreeBSD 6.0-RELEASE.

I have a minimal jail, configured in the usual manner (a minimal install
into a directory). I installed Apache 1.3 from ports into the jail and
all seemed to be well until I tried:

  # apachectl restart

The error log said:

[Sun Nov 27 20:51:23 2005] [warn] child process 59809 did not exit, sending=
 another SIGHUP
[Sun Nov 27 20:51:23 2005] [warn] child process 59986 did not exit, sending=
 another SIGHUP
[Sun Nov 27 20:51:23 2005] [warn] child process 60000 did not exit, sending=
 another SIGHUP
[Sun Nov 27 20:51:23 2005] [warn] child process 60075 did not exit, sending=
 another SIGHUP
[Sun Nov 27 20:51:23 2005] [warn] child process 60140 did not exit, sending=
 another SIGHUP
[Sun Nov 27 20:51:23 2005] [warn] child process 60147 did not exit, sending=
 another SIGHUP
[Sun Nov 27 20:51:24 2005] [warn] child process 59809 still did not exit, s=
ending a SIGTERM
[Sun Nov 27 20:51:24 2005] [warn] child process 59986 still did not exit, s=
ending a SIGTERM
[Sun Nov 27 20:51:24 2005] [warn] child process 60000 still did not exit, s=
ending a SIGTERM
[Sun Nov 27 20:51:24 2005] [warn] child process 60075 still did not exit, s=
ending a SIGTERM
[Sun Nov 27 20:51:24 2005] [warn] child process 60140 still did not exit, s=
ending a SIGTERM
[Sun Nov 27 20:51:24 2005] [warn] child process 60147 still did not exit, s=
ending a SIGTERM
[Sun Nov 27 20:51:28 2005] [error] child process 59809 still did not exit, =
sending a SIGKILL
[Sun Nov 27 20:51:28 2005] [error] child process 59986 still did not exit, =
sending a SIGKILL
[Sun Nov 27 20:51:28 2005] [error] child process 60000 still did not exit, =
sending a SIGKILL
[Sun Nov 27 20:51:28 2005] [error] child process 60075 still did not exit, =
sending a SIGKILL
[Sun Nov 27 20:51:28 2005] [error] child process 60140 still did not exit, =
sending a SIGKILL
[Sun Nov 27 20:51:28 2005] [error] child process 60147 still did not exit, =
sending a SIGKILL
[Sun Nov 27 20:51:30 2005] [error] could not make child process 59809 exit,=
 attempting to continue anyway
[Sun Nov 27 20:51:30 2005] [error] could not make child process 59986 exit,=
 attempting to continue anyway
[Sun Nov 27 20:51:30 2005] [error] could not make child process 60000 exit,=
 attempting to continue anyway
[Sun Nov 27 20:51:30 2005] [error] could not make child process 60075 exit,=
 attempting to continue anyway
[Sun Nov 27 20:51:30 2005] [error] could not make child process 60140 exit,=
 attempting to continue anyway
[Sun Nov 27 20:51:30 2005] [error] could not make child process 60147 exit,=
 attempting to continue anyway
[Sun Nov 27 20:51:30 2005] [notice] SIGHUP received.  Attempting to restart
[Sun Nov 27 20:51:31 2005] [notice] Apache/1.3.34 (Unix) configured -- resu=
ming normal operations
[Sun Nov 27 20:51:31 2005] [notice] suEXEC mechanism enabled (wrapper: /usr=
/local/sbin/suexec)
[Sun Nov 27 20:51:31 2005] [notice] Accept mutex: flock (Default: flock)

For some reason, the processes will not die. The old processes prior to
the restart die by themselves in the usual way (when 'consumed' by an
HTTP request) and the parent process creates new processes to fill the
spots. All is apparently well.

However, if I do this:

  # apachectl stop

I get the same error message as above and the old child processes still
occupy the port and the server cannot be restarted. Effectively, the
http server will not shut down (and believes that it HAS shut down) and
then will not be restarted.

The only way to rectify the situation is to log into the host machine
and kill the httpd processes running in the jail.

What is going on here?

Anybody experiencing this?

M

(please CC as I'm no longer subscribed to this list)

--=20
pgp: http://www.darklogik.org/pub/pgp/pgp.txt
0160 A46A 9A48 D3B0 C92F B690 17FB 4B72 0207 ED43

--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iQIVAwUBQ4ogfBf7S3ICB+1DAQo2Bg/9FgPLS2RFCiPQV4XBEu4GcJEvkKWtJb4j
LtvIz5UCJqAPYNKywvcA0Obt8g2a4k+V8So6td+kKCAfp0tMQ79AoGtmwjLBDn5O
cd8F9191v1NNYVNAKG70bvxm9Z2Jj/E4oieLX5/M5LLzQR1rCCg4+ogvhC7Ortak
PvVNLbbg132jl3U76Pc/OfKU5FRUQttUN13uThaB0JAYPl67JSLwPIVvhU1SLr1N
MR7bhuK/Vd4inM3HNEp9Qy4//rc3Mme2WPyNQWjsB8vIYKN+jzBf+vm11SyioBdL
BHw15DNB0eMT7zWFh0+cZieRSFBN7KoGj6GGWDvAY23efkOf9O5FUN5vjGco6Git
J6URfPHAdpauDAxB+uhg8BxdF9QORfa1jZ2U7S46MW4PtzcuGxMiJaxGbK3v+tfs
CRXo+XuPOOxME2OvAusKYoRUqdxp8xQb2Kuwthg/ybgR9ZTMS+nyrg8CeuHNBPQS
TWUGfwR8et4yyuBX1AMeP7AXYiHtqOgis7qV3m7hJ/nn12tp3pTFcvdnvcgaz6yT
XU3xiK1XYd5sjPW51G2DNftv9D8soPHOGC5PfF0FDn6+HW2HPQyLKJsTQJ5Rtaa9
BeUGpT/aRYwM4shhf86WLZvBnpJ9GO36afF4lG7x9XfgB6KFFENrUjsLvXun4kkx
V1SysAW+Rog=
=TeDV
-----END PGP SIGNATURE-----

--M9NhX3UHpAaciwkO--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051127210917.GA74091>