I had the very same problem. Upgrades from 3.1.1 to 3.1.2 went fine, but an upgrade of my running QA system from 3.0.1 direct to 3.1.2 failed just as yours did. The last line in the setup log was an ldapadd line and it had a single quote in the string (ie: "John's site") and so I assumed, wrongly, that it was the addition that caused the failure.
Out of despiration, an hour later I restored 3.0.1 from a backup, started it up to verify it was properly restored and running, and then upgraded it from 3.0.1 to 3.1.1 and then upgraded from 3.1.1 to 3.1.2. Didn't have a single problem.
So the take away for me is that rather than use a work-around I'll simply step my upgrades in production, since it just feels safer.
As a side note, I'll note that my biggest problems when moving back and forth between releases has been on /etc/sudoers. It'd be nice if rather than using the full paths with version numbers if the sudoers referenced a more generic path that wasn't changing every release. It'd sure cut down on a lot of problems, for me at least.  |