Re: [Erlyaws-list] Yaws 1.8.8 (embedded) unexpectedly died

[Martin W. <ta...@gm...>]

Unfortunately that is bit of a problem. There is a lot of code behind it
to post it here (4 other modules/libs called from yaws file).

I debugged my code (not using debugger because of remote servers) using
logging and all seems to be fine - function call returns XML back to
client. But what is strange is that after that call all other requests
returns 404 error until whole OTP application is restarted.

Testing server with X and maybe Erlang debugger will tell me more. But I
really welcome every tip or hint (even I know that it is hard without
any code).


Kind Regards,
Martin

On Thu, 2010-06-03 at 11:45 -0400, Steve Vinoski wrote:
> On Thu, Jun 3, 2010 at 6:14 AM, Martin Wišo <ta...@gm...> wrote:
> > I have a strange issue with Yaws 1.8.8 (from github) running on Ubuntu
> > 10.4 amd64 using embedded mode. My application is not using appmods nor
> > custom url routing. It is just a yaws file that serve XML content. Yaws
> > works just fine for all requests except one that do some IO operations
> > (local files copy, file generation and final zip compression), but it is
> > not about some big files (~ 5MB) or long running request.
> >
> > I faced an error and I am not able to find out what is going on. Code
> > that serves request works fine (according to log entries) and finished
> > without an error, but with next request I get 404 http code and
> > following error report:
> >
> > Yaws process died: {{badmatch,{error,enoent}},
> >                    [{yaws_server,send_file,5},
> >                     {yaws_server,deliver_large_file,4},
> >                     {yaws_server,aloop,3},
> >                     {yaws_server,acceptor0,2},
> >                     {proc_lib,init_p_do_apply,3}]}
> >
> > Only solution to solve 404 problem is restarting whole application.
> > Please is it possible to find out more about it (server is acessible
> > only via ssh)? I am a bit lost.
> 
> Can you post your yaws file? It appears that something is asking for a
> non-existent file, but it's hard to know what's going on without being
> able to see what you're doing.
> 
> --steve