yaws

On 4/23/09, Wojciech Kaczmarek <kaczmarek.w@...> wrote:
> Hi!
> I upgraded yaws from 1.77 to 1.81 and it crashes on start:
>
> Kernel pid terminated (application_controller)
> ({application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}})

Two things:

1. Can you send your report.log file to me please? No need to spam the
list, just send it to me directly.

2. For 1.81 if you reconfigure with --disable-sendfile and then
rebuild, does it then work?

It's possible there's some OS X PPC issue, which item 2 in the list
will tell us. I don't think it's a PPC issue as I run that driver on a
Linux PPC box and it works OK there. Coincidentally I just got an old
OS X PPC laptop of mine returned to me last night so if there really
is an issue on that platform, testing it and fixing it shouldn't be
too hard.

thanks,
--steve

On 4/23/09, Steve Vinoski <vinoski@...> wrote:
> On 4/23/09, Wojciech Kaczmarek <kaczmarek.w@...> wrote:
>  > Hi!
>  > I upgraded yaws from 1.77 to 1.81 and it crashes on start:
>  >
>  > Kernel pid terminated (application_controller)
>  > ({application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}})
>
>  It's possible there's some OS X PPC issue, which item 2 in the list
>  will tell us. I don't think it's a PPC issue as I run that driver on a
>  Linux PPC box and it works OK there. Coincidentally I just got an old
>  OS X PPC laptop of mine returned to me last night so if there really
>  is an issue on that platform, testing it and fixing it shouldn't be
>  too hard.

I just built Erlang/OTP R13B and Yaws 1.81 from the current HEAD on
github on OS X Leopard on a PPC PowerBook, and it all works just fine.
I verified with dtrace that sendfile was being called, and I
transferred a variety of files and each came through perfectly and
quickly.

When you moved from 1.77 to 1.81, did you reconfigure your source tree
and all that?

--steve

On Fri, Apr 24, 2009 at 04:25, Steve Vinoski <vinoski@...> wrote:
> On 4/23/09, Steve Vinoski <vinoski@...> wrote:
>> On 4/23/09, Wojciech Kaczmarek <kaczmarek.w@...> wrote:
>>  > Hi!
>>  > I upgraded yaws from 1.77 to 1.81 and it crashes on start:
>>  >
>>  > Kernel pid terminated (application_controller)
>>  > ({application_start_failure,yaws,{shutdown,{yaws_app,start,[normal,[]]}}})
>>
>>  It's possible there's some OS X PPC issue, which item 2 in the list
>>  will tell us. I don't think it's a PPC issue as I run that driver on a
>>  Linux PPC box and it works OK there. Coincidentally I just got an old
>>  OS X PPC laptop of mine returned to me last night so if there really
>>  is an issue on that platform, testing it and fixing it shouldn't be
>>  too hard.
>
> I just built Erlang/OTP R13B and Yaws 1.81 from the current HEAD on
> github on OS X Leopard on a PPC PowerBook, and it all works just fine.
> I verified with dtrace that sendfile was being called, and I
> transferred a variety of files and each came through perfectly and
> quickly.

I have OS X Tiger 10.4.11, not Leopard.

> When you moved from 1.77 to 1.81, did you reconfigure your source tree
> and all that?

Yes of I did make clean, configure and stuff.
I also repeated configure/make after a sequence of:
git reset --hard && git clean -fd
which is a handy way to ensure you have only the repository files in
your dir hierarchy with no intermediate compilation products in the
case of 'make clean' omitting something.
The result was the same error.

report.log was tiny so I cite it here:
=INFO REPORT==== 24-Apr-2009::17:03:44 ===
Ctlfile : /Users/wk/.yaws/yaws/default/CTL

=INFO REPORT==== 24-Apr-2009::17:03:44 ===
Yaws: Listening to 0.0.0.0:443 for servers
 - https://vault under /tmp

=INFO REPORT==== 24-Apr-2009::17:03:44 ===
Yaws: Listening to 0.0.0.0:80 for servers
 - http://vault under /usr/local/yaws/test/var/yaws/www
 - http://localhost under /tmp

=INFO REPORT==== 24-Apr-2009::17:03:44 ===
    application: yaws
    exited: {shutdown,{yaws_app,start,[normal,[]]}}
    type: permanent
------

Setting --disable-sendfile indeed makes yaws work.

So, the bug appearance seem to narrow to sendfile usage on OS X 10.4.

cheers

On Fri, Apr 24, 2009 at 17:17, Wojciech Kaczmarek <kaczmarek.w@...>
>
> Setting --disable-sendfile indeed makes yaws work.
>
> So, the bug appearance seem to narrow to sendfile usage on OS X 10.4.
>

Haha, quick investigation shows Tiger doesn't have sendfile(2) at all:
HISTORY
     The sendfile() system call first appeared in Darwin 9.0 (Mac OS X
version 10.5) .

^^ http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man2/sendfile.2.html

I bet yaws autoconf stuff wrongly  assumes that we have sendfile(2)
only because we're on OS X. That would be the place to fix.

Cheers!

On 4/24/09, Wojciech Kaczmarek <kaczmarek.w@...> wrote:
> Haha, quick investigation shows Tiger doesn't have sendfile(2) at all:

That could be problematic. :-)

>  I bet yaws autoconf stuff wrongly  assumes that we have sendfile(2)
>  only because we're on OS X. That would be the place to fix.

I went home for lunch and fired up my old Tiger box, which I haven't
touched in months, and left it updating. When I get home I'll fix Yaws
config to avoid this problem. Thanks for tracking it down!

--steve

On 4/24/09, Steve Vinoski <vinoski@...> wrote:
> On 4/24/09, Wojciech Kaczmarek <kaczmarek.w@...> wrote:
>  > Haha, quick investigation shows Tiger doesn't have sendfile(2) at all:

I just pushed the fix for this up to github. Thanks again for finding
the problem.

--steve

On Sun, Apr 26, 2009 at 16:38, Steve Vinoski <vinoski@...> wrote:
>
> I just pushed the fix for this up to github. Thanks again for finding
> the problem.

Yeah it works. Thanks! :-]