Sorry, one further fact, we have about 160 binlogs, some are 10Mb, I understand this is a bug that was in version 1.4 (which we are using), perhaps if we clean these up correctly then the problem may go away?
- icydee On Monday, 1 October 2012 15:55:36 UTC+1, Ian Docherty wrote: > > Recently when starting beanstalkd we get the following error message > numerous times. > > /usr/bin/beanstalkd: WARNING, EOF while reading version record at > /var/lib/beanstalkd/binlog/binlog.203:0. Continuing. You may be missing data.: > > > Investigating where this error comes from, it seems to be when beanstalkd > checks for a version number in the log file, and can't find it. > > > Is it possible that the binlog has become corrupted? > > > I mention this because we had a problem recently where some NFS drive errors > may have caused it to crash. > > > What is the best way of recovering from this error? Should the binlog be > deleted manually? If we instruct beatstalk to delete all buried jobs, does > this also re-create the binlog file? > > > - icydee > > > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/1g2SK51-OUgJ. 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.
