Well, the ebadf errors are still there but doesn't seem to be posing a problem and its be running for 4 days.


lsof also has less than 50 entries. 

The server is not sending large files so I think it could be something else so will have a look at it further.

Thanks to everyone for the help. Much appreciated.


On Sat, Dec 21, 2013 at 11:36 PM, Christopher Faulet <christopher.faulet@capflam.org> wrote:
On 20/12/2013 15:29, Steven wrote:
> Hi all,
> We are running Yaws 1.96 on Erlang 15B03-1 for hosting and experienced
> this continuously in the nohup file.
> =ERROR REPORT==== 4-Dec-2013::11:52:31 ===
> Unhandled reply fr. do_recv() {error,ebadf}
> =ERROR REPORT==== 4-Dec-2013::11:52:31 ===
> Unhandled reply fr. do_recv() {error,ebadf}
> =ERROR REPORT==== 4-Dec-2013::12:01:06 ===
> Unhandled reply fr. do_recv() {error,ebadf}


This error happens if a connection is closed when the server is sending
a large file. In that case, the yaws_sendfile:send/2 function returns
the error "{error, closed}" but this error is ignored by the caller. So,
when we try to read headers of the next request, the file descriptor is
invalid and we get the error "{error, ebadf}".

I'll try to fix this bug very soon. But, as far as I can see, and as
ugly as it can be, this bug just seems to generates awkward error
messages. So I doubt that it could crash the server. But maybe I'm
wrong, hard to say.

I try to figure out why erlang fails to accept new connection if there
is no fds leak. But I have no clue for now.


Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
Erlyaws-list mailing list