On Dec 16, 5:18 pm, Keith Rarick <[email protected]> wrote: > On Wed, Dec 16, 2009 at 4:19 PM, Steve <[email protected]> wrote: > > My beanstalk stopped responding. I ran gdb and got the following > > stack trace: > > This stack trace looks pretty reasonable. The rehash function is one > of the few that do long-running (i.e. on the order of milliseconds) > work. A load average of 2.38 suggests that some other processes were > trying to run and beanstalkd couldn't get scheduled. Did you have a > high iowait? That would explain a lot.
no processes, including beanstalk, were registering as using any cpu according to top. Here's the relevant line from top: Cpu(s): 0.2%us, 0.0%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st I also ran the stack trace multiple times and it was in exactly the same place. > > > I then *restarted* beanstalk, and it wouldn't finish launching. I got > > this stack trace: > > This stack trace is normal for a running idle beanstalkd. I'm not sure > exactly what you mean by "finish launching". Could you describe the > behavior you saw? Well, clients were unable to connect. They would just hang for multiple minutes before I canceled them. > > If rebooting solved the problem, maybe something else is wrong. Well, yeah, that's totally possible. Beanstalk seemed to have the weirdest behavior - other services responded, albeit very slowly. If it happens again, is there anything I should look for? -- 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.
