Re: Debugging COMM:START-UP-SERVER hang
Martin Simmons <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
>>>>> On Fri, 27 Feb 2026 12:30:57 +0000, Adam Weaver said: > > Martin spake: > > > I suggest adding the -f option to strace (which will make it show all threads) > > and then try to make a new connection to the port to see if it is accepted. > > Thanks Martin! Like I mentioned earlier, new connections weren't htting > the ACCEPT phase. There's a little tool `cgi-fastcgi -bind` which can mock > a FCGI process. That was failing at the CONNECT phase. Is there an error message from the failing CONNECT phase? > > You could also look at the output of lsof -p $pid to check that the process is > > not running out of file descriptors. > > oh yeah... that also sounds plausible. It *does* take a good week for the > acceptor func to hang. Maybe the problem is the (ignore-errors (close connection) ...)? If there is any output in the stream's buffer, then close will try to write it before closing the handle. Writing to a socket might cause an error if the other end of the connection has been closed already. If you don't care about flushing, then use (close connection :abort t). Also, log errors rather than silently ignoring them. -- Martin Simmons LispWorks Ltd http://www.lispworks.com/ _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html