-----BEGIN PGP SIGNED MESSAGE----- Hello,
the following problems I wrote yesterday has been partly resolved now: > I've installed Apache 2.2.3 on a Redhat Advanced Server 4 (with all > updates installed). You can look at the configuration log at > <http://wwwtest.uni-muenster.de/config.log>. > Every quarter or so, a client dies with one of the following lines in > the error log (lines broken by me): > httpd: ../../../libraries/liblber/io.c:516: ber_get_next: > Assertion `ber->ber_buf == ((void *)0)' failed. > httpd: ../../../libraries/liblber/io.c:710: ber_get_next: > Assertion `0' failed. > often followed by something like > [Tue Sep 19 18:52:12 2006] [notice] child pid 20794 exit signal > Aborted (6) > This also happens if I disabled all LDAP modules during configure. The problem did no longer occur after starting the "nscd" (name service cache daemon) on the same host. > I do not need any LDAP functionality at all, thus I tried to > circumvent the problem by configuring with "--without-ldap", but that > caused the configuration of apr-util to fail because > srclib/apr-util/configure understands "--without-ldap" as > "--with-ldap=no" and looks in the directory "no" for LDAP libraries. Thus I do no longer need to try compiling Apache with --without-ldap. (Maybe this behaviour of the configure program could be worth fixing nevertheless.) > Another phenomenon, maybe completely independent from the problem > above: > After graceful restarts, often two or more of the following lines > appear in the error log: > [Tue Sep 19 18:52:13 2006] [error] (9)Bad file descriptor: > apr_socket_accept: (client socket) This still happens. But I did not yet see problems correlating to this message. (But perhaps this still indicates some problem in Apache that might be worth fixing.) > After this message appears, often about half of the HTTPD child > processes keep owned by root instead of changing their identity to > the user given in the config file. This problem also did not longer occur after starting the "nscd". > The problem is nasty because it causes more and more connections to > hang indefinitly (until the browser times out). This problem also did not longer occur after starting the "nscd". I had installed Apache 2.2.3 on many hosts at the same time, those problems that now disappeared only occured on hosts that were running up-to-date GPFS servers at the same time (but not on those that only were GPFS clients). I cannot imagine how GPFS service can interfere with the name resolution, but obviously it happens. Thanks to all who were willing to help me. cu - -- Rainer Perske, Zentrum für Informationsverarbeitung, Universität Münster Lesetipp: <http://www.textkritik.de/schriftundcharakter/sundc008tofu.htm> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (AIX) iQDVAwUBRRE7/89UbnbjB8C5AQEyaQYAqFlTxS0qcGmHqroVCJxl11mXi/tZyPZ6 bMisCwZ1IKHB2LbeRShD5Rx9Ve4nmaHLL7r7z+0lGLbuCsbOBKY3pk297s/jCYpv siZb3BatHKE3vrk/RuUEm+EFSNOBWrM/ag0iSUhJoSGgAyJcjw0cETR+Pb7bz9BP Ioo/pBZU850CpjAKeFwjDacAUeWNN42YEbg82i8Jp5Vyp5krk7E2q1ZsRVFDA2tb C/Efo1tH7uj1zhiv/xMpoJ9owYZphkIT =koPh -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
