Hi guys.
I'm not a C coder or anything like that, so I'm not sure what info is
needed, but to kick things off I'll start with this.
I am testing my PHP client, trying to get all the bugs out and make it
bulletproof. I've been running some pretty heavy tests, basically
writing and reading from the server pretty damned hard. After anywhere
between 100k and 300k jobs processed, the server seg faults. I have
monitored the process via telnet and the server is not getting over
full, jobs are being read as they arrive.
Basically all I was doing is making simple, relatively small XML
packets as jobs (maybe 120 chars each), writing them to beanstalkd,
and then reading them out using 2 concurrent readers. This time I got
to just over 360,000 before the crash.
while ($job = $beanstalk->reserve())
{
$jobs ++;
BeanStalk::delete($job);
}
I ran the server through gdb and here are the results:
Beanstalkd Version: 1.2
System: Linux apps 2.6.18-92.1.10.el5PAE #1 SMP Tue Aug 5 08:14:05 EDT
2008 i686 i686 i386 GNU/Linux
Model Name : Intel(R) Xeon(R) CPU E5410 @ 2.33GHz QUAD core
MemTotal : 8311056 kB
(gdb) file /usr/local/bin/beanstalkd
Reading symbols from /usr/local/bin/beanstalkd...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/local/bin/beanstalkd
[Thread debugging using libthread_db enabled]
[New Thread -1208727872 (LWP 32126)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208727872 (LWP 32126)]
pq_take (q=0xd0) at pq.c:143
143 if (q->used == 0) return NULL;
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
