Comment 2 for bug 670165

@dlebauer: Did the workaround recommended by John worked ?

We only rarely hear about this kind of failure so it's hard to diagnose, any weird event you can remember before this failure occurred ?

You're using a pretty old version: 2.0.3 was released 2009-12-14 and 2.0.6 is the latest release in the 2.0 series.
The current stable release is 2.2.1, I don't have a precise pointer but I'm pretty sure it has been packaged for redhat, so you should be able to upgrade.