New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault in connsoonestjob at conn.c:166 #160
Comments
Can you reproduce the error? If so, would you mind compiling
and producing a stack trace? |
Hi Kr, I could not proceed for further testing due to workload. Could you please guide how to see general protection error as I am starting Thanks. On 14 December 2012 13:29, Keith Rarick notifications@github.com wrote:
Aaqib Salman Malik | Technical Manager MOBIZONE PAKISTAN – An ARPUPLUS Company |
Hi Kr, I managed to get core dump. GNU gdb (GDB) Red Hat Enterprise Linux (7.2-56.el6)
On 24 January 2013 10:26, Aaqib Salman Malik aqibsm@gmail.com wrote:
Aaqib Salman Malik | Technical Manager MOBIZONE PAKISTAN – An ARPUPLUS Company |
@kr Did you have any idea on this? |
We're getting the same error on v1.10:
Anyone found the cause of this? @kr ? |
We have just hit this, as well: Apr 8 17:46:37 db01 kernel: [56880694.274429] traps: beanstalkd[1048] general protection ip:40241c sp:7ffd78a06a20 error:0 in beanstalkd[400000+e000] |
@jhammer, what version do you run? Can you produce the stack trace? |
@ysmolsky version 1.9. Sorry, I do not have the stack trace. Seem pretty rare in our case. Only hit the issue once after literally years of uptime. |
There are a few stacktraces lying around here. We hit it once in a while. Lately not much, since we've moved majority of our workload to another queue manager. It seems the number of crashes correlate with workload. |
@thorro could you paste those stacktraces here? Did you move to another queue manager because beanstalkd failed to handle the load? |
@ysmolsky we moved mainly because of the crashes. Link to bt: Also, because sometimes binlog files got out of hand. Meaning, when there were a lot of jobs, binglog size grew, which is normal, but when the jobs got processed and deleted, binlog size stayed the same, it didn't shrink. But that's another issue. |
Without a core dump it's next to impossible to fix this kind of error. If anyone can share core dump (that will contain everything that is inside of beanstalkd), I would be glad to look at and try to fix this. |
Reported by @aqibsm in #119:
The text was updated successfully, but these errors were encountered: