[Openmcl-devel] "Bad file descriptor during read"

[Ron Garret]

This happens when a client closes an HTTP connection prematurely and Hunchentoot attempts to read from what is now a closed TCP socket.  It can also happen if you have a flaky network connection.  But neither of these explains why you’re getting more of these on AWS than before you moved there.

Where were you hosted before moving to AWS?

On Feb 7, 2020, at 9:20 AM, Mark Klein <m_klein at MIT.EDU> wrote:

> 
> > Error: on #<BASIC-CHARACTER-INPUT-STREAM UTF-8 (CHARACTER-SPECIAL/0) #x302000431CAD> : 
> >        Bad file descriptor during read
> > While executing: #<CCL::STANDARD-KERNEL-METHOD CCL::STREAM-IO-ERROR (STREAM T T)>, in process listener(1).
> 
> 
> I got tons (hundreds) of these in the server log after I moved my hunchentoot-based web server to a AWS linux instance.
> 
> Any suggestions re what it means and how I can fix it?
> 
>      Thanks!
> 
> Mark
> 
> ----------------------
> Mark Klein, PhD
> Principal Research Scientist
> Massachusetts Institute of Technology
> http://cci.mit.edu/klein/
> 
> 
> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> https://lists.clozure.com/mailman/listinfo/openmcl-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20200207/115d89f2/attachment.htm>