Re: was database too old or corrupt error on debian ever solved

Hi Dan,

Holy s...! We could have solved this months ago by simply looking at the output
of the refdb-bug script (which was designed to find configuration errors like
this). I should have insisted on having a look.

Flexibility seems to have its price. How can we prevent mishaps like this one in
the future? Better debug information? Better error messages? Better docs? All of
the above?

regards,
Markus

Dan O'Donnell <[email protected]> was heard to say:

> A redfaced solution.
>
> I think I figured out what the problem is. It doesn't speak well of me,
> but since I hate people who answer their own queries with "nevermind, I
> solved it" I'll specify:
>
> There were always two problems: 1) I was getting a dbase too old or
> corrupt, and 2) I didn't seem to be using MySql. The solution to both
> problems lay in the config files: you need to change the default dbase
> to MySql (if that's what you want), and you need to change the default
> username to whatever is required by the dbase.
>
> This gets rid of the errors I've been having all along. Now I don't seem
> able to able to finish the creation or new users or databases, but that
> may be simply a result of my never reading the manual past trouble
> shooting, since I couldn't get past the "main db corrupt" error.
>



-- 
Markus Hoenicka
[email protected]
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de



-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642