[mod-lisp-devel] Possible bug

[Alain.Picard at memetrics.com]

Dear all,

I'm using modlisp v 2.42 (someone tell me if I'm supposed
to use something better/newer) on Apache 1.3.33.

I came in one day to find my apache helpless to render
any requests, indicating in its log file:
    [Wed Mar 30 18:11:00 2005] [error] System: Too many open files (errno: 24)
    [Wed Mar 30 18:11:08 2005] [error] [client 203.100.236.222] (24)Too many open files: Could not open password file: /w
    ww/conf/passwords

My set up is as follows; I have 4 virtual hosts, each of which has
1 Lispserver directive, e.g.

     <VirtualHost s1-instance-1>
	DocumentRoot /www/clients/instance1
	ServerName xos.memetrics.com
	LispServer  192.168.1.116 3000 "instance1"
	<Location /asp-agg>
	    SetHandler lisp-handler
	</Location>
     </VirtualHost>

and so on for the other 3, with each one having a unique host/port
combination, each vhost talking to a different Lisp back end.

Now, two of my back ends are currently non-existent, i.e. nobody
is listening on ports 192.168.1.118:3002 (say).

There is a process which pings, once per second, a URL which apache
tries to forward to the (non-existent) lisp back end.

Each such ping seems to result in a file descriptor leak; to wit:

    [root at asp1]/www/conf# lsof |grep http | wc ; date
	875    8426   81263
    Wed Mar 30 19:51:03 CST 2005

 ... some time later

    [root at asp1]/www/conf# lsof |grep http | wc ; date
	920    8876   85448
    Wed Mar 30 19:54:51 CST 2005

This does not occur if the Lisp back ends are alive and accepting
requests.


I've looked through the modlisp code, but no obvious leaks are
apparent to me, of course, I've no clue what ap_psocket really does,
and it's not documented.  :-(

Any help is appreciated...

					--Alain Picard