We had a problem with a particular box which resulted in a lot (~3.6GB) of binlogs being created. I now cannot start Beanstalkd on that box because it gets killed by the kernel with OOM (Out of Memory).
So, I tried to copy them off onto a bigger box and then start Beanstalkd on that box instead, imagining it would recover the contents of these binlogs. What actually happens is that Beanstalk instantly deletes all 3.7GB of binlogs without restoring any of the messages. Any ideas? Thanks in advance. Dave -- 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.
