From: Martin D. <mrt...@gm...> - 2012-08-08 10:53:31
|
Hello, I receive this error right after the return of my 'out' function in yaws page. The request is POST coming from Google spreadsheet. I know this is quite vague but I really can't find any peculiarities. Which module is calling the 'out' functions? Thanks in advance, Martin |
From: Steve V. <vi...@ie...> - 2012-08-08 12:44:36
|
On Wed, Aug 8, 2012 at 6:53 AM, Martin Dimitrov <mrt...@gm...> wrote: > Hello, > > I receive this error right after the return of my 'out' function in yaws > page. The request is POST coming from Google spreadsheet. > > I know this is quite vague but I really can't find any peculiarities. > Which module is calling the 'out' functions? The yaws_server module calls the out/1 functions, specifically lines 2271 and 2721. Your error message is coming from the Erlang VM, not from Yaws itself. Maybe you have an unexpected term within an iolist somewhere? --steve |
From: Martin D. <mrt...@gm...> - 2012-08-09 07:00:27
|
Hi Steve, Thanks for the hint. Things got even stranger. I put some debug messages in yaws_server:'POST'/3 around yaws_server:body_method/3. My out/1 function is called without causing any errors. Its return is as simple as {html, "OK"}. Then after yaws_server:'POST'/3 is done executing, the error message appears. Which function is calling yaws_server:'POST'/3? Can it be the HTTP headers Google sends that cause trouble? Best regards, Martin On 8/8/2012 3:44 PM, Steve Vinoski wrote: > On Wed, Aug 8, 2012 at 6:53 AM, Martin Dimitrov <mrt...@gm...> wrote: >> Hello, >> >> I receive this error right after the return of my 'out' function in yaws >> page. The request is POST coming from Google spreadsheet. >> >> I know this is quite vague but I really can't find any peculiarities. >> Which module is calling the 'out' functions? > The yaws_server module calls the out/1 functions, specifically lines > 2271 and 2721. > > Your error message is coming from the Erlang VM, not from Yaws itself. > Maybe you have an unexpected term within an iolist somewhere? > > --steve |
From: Claes W. <kl...@ta...> - 2012-08-09 08:21:20
|
On 8/9/12 9:00 AM, Martin Dimitrov wrote: > Hi Steve, > > Thanks for the hint. Another hint is that it's the 'efile' that is the port that gets something that is bad. So, out() function probably returns ok, but then yaws tries to log things to file. /klacke |
From: Martin D. <mrt...@gm...> - 2012-08-09 10:15:23
|
What 'efile' signifies anyway? Thanks. On 8/9/2012 11:04 AM, Claes Wikstrom wrote: > On 8/9/12 9:00 AM, Martin Dimitrov wrote: >> Hi Steve, >> >> Thanks for the hint. > > > Another hint is that it's the 'efile' that is the port that > gets something that is bad. So, out() function probably returns > ok, but then yaws tries to log things to file. > > > /klacke > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list |
From: CGS <cgs...@gm...> - 2012-08-09 10:39:13
|
http://www.erlang.org/doc/man/erl.html or http://www.erlang.org/doc/man/erl_prim_loader.html (search for efile) (loader related) efile means (to load) a file from local file system. CGS On Thu, Aug 9, 2012 at 12:15 PM, Martin Dimitrov <mrt...@gm...> wrote: > What 'efile' signifies anyway? > > Thanks. > > On 8/9/2012 11:04 AM, Claes Wikstrom wrote: >> On 8/9/12 9:00 AM, Martin Dimitrov wrote: >>> Hi Steve, >>> >>> Thanks for the hint. >> >> >> Another hint is that it's the 'efile' that is the port that >> gets something that is bad. So, out() function probably returns >> ok, but then yaws tries to log things to file. >> >> >> /klacke >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Erlyaws-list mailing list >> Erl...@li... >> https://lists.sourceforge.net/lists/listinfo/erlyaws-list > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list |
From: Claes W. <kl...@ta...> - 2012-08-10 11:53:31
|
On 8/9/12 12:39 PM, CGS wrote: > http://www.erlang.org/doc/man/erl.html or > http://www.erlang.org/doc/man/erl_prim_loader.html (search for efile) > > (loader related) efile means (to load) a file from local file system. > > CGS > Hmm, I though that maybe some of the command below should have produced that error output, but they don't. Eshell V5.8.5 (abort with ^G) 1> {ok, Fd} = file:open("abc", [write, raw]). {ok,{file_descriptor,prim_file,{#Port<0.403>,11}}} 2> file:write(Fd, [anatom]). {error,badarg} 3> file:write(Fd, ["abc", abc, "edf"]). {error,badarg} 4> file:write(Fd, ["abc", 266, "edf"]). {error,badarg} 5> file:write(Fd, [1|2]). {error,badarg} 6> file:write(Fd, "aaa"). ok 7> file:write(Fd, [1|2]). {error,badarg} 8> |
From: Steve V. <vi...@ie...> - 2012-08-10 13:29:42
|
On Fri, Aug 10, 2012 at 7:53 AM, Claes Wikstrom <kl...@ta...> wrote: > On 8/9/12 12:39 PM, CGS wrote: >> http://www.erlang.org/doc/man/erl.html or >> http://www.erlang.org/doc/man/erl_prim_loader.html (search for efile) >> >> (loader related) efile means (to load) a file from local file system. >> >> CGS >> > > Hmm, I though that maybe some of the command below should have produced > that error output, but they don't. > > > Eshell V5.8.5 (abort with ^G) > 1> {ok, Fd} = file:open("abc", [write, raw]). > {ok,{file_descriptor,prim_file,{#Port<0.403>,11}}} > 2> file:write(Fd, [anatom]). > {error,badarg} Hi Klacke, you need to have sasl started to see that efile message: $ erl -boot start_sasl Erlang R15B01 (erts-5.9.1) [source] [smp:8:8] [async-threads:0] [hipe] [kernel-poll:false] Eshell V5.9.1 (abort with ^G) 1> {ok, Fd} = file:open("/tmp/abc", [write, raw]). {ok,{file_descriptor,prim_file,{#Port<0.704>,11}}} 2> file:write(Fd, [anatom]). =ERROR REPORT==== 10-Aug-2012::09:28:11 === Bad value on output port 'efile' {error,badarg} --steve |