problem with beanstalk on os x

[Steve]

I'm getting this error after beanstalk is running for a few minutes:

% /usr/local/bin/beanstalkd
[warn] kevent: Invalid argument
/usr/local/bin/beanstalkd: beanstalkd.c:323 in main: got here for some
reason
*exits*

this is with snow leopard (10.6.1), beanstalkd (1.4) and libevent
(1.4.12-stable)

Not sure how you want me to characterize client activity. I'd guess
there only a hundredish jobs executed successfully before this error
appears and beanstalkd dies.

[Keith Rarick]

On Sun, Nov 15, 2009 at 1:04 PM, Steve <sfar...@gmail.com> wrote:
> I'm getting this error after beanstalk is running for a few minutes:
>
> % /usr/local/bin/beanstalkd
> [warn] kevent: Invalid argument
> /usr/local/bin/beanstalkd: beanstalkd.c:323 in main: got here for some
> reason
> *exits*
>
> this is with snow leopard (10.6.1), beanstalkd (1.4) and libevent
> (1.4.12-stable)

Sorry it's taken me so long to respond; this got buried in my inbox.

This is probably a bug in either beanstalkd's use of libevent, or
libevent's use of kqueue. It will be hard for me to reproduce.

Do you see this behavior consistently? Can you provide a capture of
beanstalkd's network traffic, or a reduced test case that causes this
to happen?

kr

[Steve Farrell]

Hi,

It does happen consistently.  I'll try to get you something reproducible or a network dump, as you suggest.

In the meantime, a few more data points: beanstalk 1.4.2 and 1.4 both exhibit this problem.  1.3, when linked with the exact same libevent, does *not*.

--

You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beansta...@googlegroups.com.
To unsubscribe from this group, send email to beanstalk-tal...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.

[Luke Redpath]

I'm seeing this issue on OSX Snow Leopard too, except it happens as
soon as I try and start beanstalkd:

beanstalkd.c:323 in main: got here for some reason

libevent 1.4.12 and beanstalkd 1.4.3.

[Steve]

I'm still getting this problem even with beanstalk 1.4.3 and libevent
1.4.13. I think it might have something to do with calling reserve
with a timeout of 0.

Keith, I have a dump. It's small - just 1.2k. I'll mail it to your
personal address.