Closed atomical closed 5 years ago
Hrm. Maybe Sphinx has crashed at some point? There's nothing in the log prior to that indicating when it was last stopped it happened unexpectedly?
I presume you've got past it? The easiest way to do so is to delete everything in the binlog directory - and if you're using any real-time indices, reprocess the data to be on the safe side.
Just to elaborate slightly: I feel like the binlog files being missing/invalid could happen due to Sphinx crashing… but if you're not seeing that, I'm less certain what the cause is in your case.
Possibly a crash. Closing this for now until I have more information.
Hi Pat,
We've seen this a lot during deploys. I might have mentioned it in a few other issues. Any ideas on what might cause this show stopper?
We're using Thinking Sphinx 4.0.0 and Sphinx 2.3.2-id64-beta.