My beanstalk stopped responding.  I ran gdb and got the following
stack trace:

#0  rehash (j=<value optimized out>) at job.c:85
#1  store_job (j=<value optimized out>) at job.c:57
#2  0x0804c60e in make_job_with_id (pri=65536, delay=0, ttr=120000000,
body_size=316, tube=0x95c4e80,
    id=0) at job.c:145
#3  0x0804f2c5 in dispatch_cmd (c=<value optimized out>) at prot.c:
1115
#4  0x080506ea in do_cmd (fd=25, which=2, c=0x95c31c0) at prot.c:1494
#5  h_conn_data (fd=25, which=2, c=0x95c31c0) at prot.c:1532
#6  h_conn (fd=25, which=2, c=0x95c31c0) at prot.c:1643
#7  0xb778a248 in event_base_loop () from /usr/lib/libevent-1.4.so.2
#8  0xb778a3c9 in event_loop () from /usr/lib/libevent-1.4.so.2
#9  0xb778a3ee in event_dispatch () from /usr/lib/libevent-1.4.so.2
#10 0x08049aab in main (argc=1, argv=0xbff4da54) at beanstalkd.c:321

I then *restarted* beanstalk, and it wouldn't finish launching.  I got
this stack trace:

#0  0xb7773416 in __kernel_vsyscall ()
#1  0xb76c0738 in epoll_wait () from /lib/tls/i686/nosegneg/libc.so.6
#2  0xb7768792 in ?? () from /usr/lib/libevent-1.4.so.2
#3  0xb775af82 in event_base_loop () from /usr/lib/libevent-1.4.so.2
#4  0xb775b3c9 in event_loop () from /usr/lib/libevent-1.4.so.2
#5  0xb775b3ee in event_dispatch () from /usr/lib/libevent-1.4.so.2
#6  0x08049aab in main (argc=1, argv=0xbfdffbd4) at beanstalkd.c:321

The output from top was bizarre too - 0% cpu utilization and 2.38 load
avg... and that wasn't just a timing fluke - I checked and it was
reporting similar numbers for 5 minutes.

It only worked again after rebooting the system.  I'm running ubuntu
9.10 on ec2 with 2.6.31-302-ec2.

Where do I start?

--

You received this message because you are subscribed to the Google Groups 
"beanstalk-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/beanstalk-talk?hl=en.


Reply via email to