OUT_OF_MEMORY error with -d AND -b about beanstalkd HOT 12 CLOSED

The problem was also reported in this thread http://groups.google.com/group/beanstalk-talk/browse_thread/thread/f70697558a44ac20/

from beanstalkd.

This is because beanstalk does a chdir("/") when it detaches, and the relative path given on the command line is being misinterpreted when it comes time to open a second binlog segment.

To get consistent behavior, you should provide an absolute path to the -b option.

I'll have beanstalkd require an absolute path in the future, when you combine -b and -d.

from beanstalkd.

Require absolute path when -b is used with -d.

Closed by a4b5484.

from beanstalkd.

Still an issue. CentOS 5.2 (Final).
Launched with:
$ beanstalkd -d -b /var/spool/beanstalkd -f 1000 -u beanstalkd

Despite of the absolute path being used and newest beanstalkd version (1.4.6), it crashes with OUT_OF_MEMORY error after about 10-20 thousand of jobs.

from beanstalkd.

Found the conditions under which it's a problem:

1. Start beanstalkd with flags above
2. Use it
3. do killall -9 beanstalkd
4. Start it again
5. On use it immediately crashes

That's fake persistence.

from beanstalkd.

The only hackaround is to start beanstalkd again, do plain killall, and restart it again.

from beanstalkd.

Also, it seems to exhibit this behavior only when the queue is empty before crash.

from beanstalkd.

Running in non-detached mode does the same. Debug info:
beanstalkd: binlog.c:589 in maintain_invariants_iter: newest binlog has invalid 182 reserved
beanstalkd: prot.c:841 in enqueue_incoming_job: server error: OUT_OF_MEMORY

from beanstalkd.

Will post a new issue, though

from beanstalkd.

I've reproduced this, and I'm working on a fix.

from beanstalkd.

Just for clarity, the new issue is at http://github.com/kr/beanstalkd/issues/closed/issue/44 and it's fixed as well.

from beanstalkd.

Sorry, that link should be http://github.com/kr/beanstalkd/issues/issue/44

from beanstalkd.