08-Dec-03 at 15:33, Jon Carnes ([EMAIL PROTECTED]) wrote :
> Sounds bad kemosabee. The backup is the way to go. You might be able to
> use "strings config.pck" and get a string dump of the file that has some
> helpful information.
Cheers Jon
Got the backup, ran check_db, all OK, and I'm back up
Sounds bad kemosabee. The backup is the way to go. You might be able to
use "strings config.pck" and get a string dump of the file that has some
helpful information.
Good Luck!
On Mon, 2003-12-08 at 12:04, Simon White wrote:
> 08-Dec-03 at 11:51, Jon Carnes ([EMAIL PROTECTED]) wrote :
> > Do you
08-Dec-03 at 11:51, Jon Carnes ([EMAIL PROTECTED]) wrote :
> Do you have a config.pck.last for that list? Try renaming your current
> config.pck and copy over the config.pck.last and see if that works.
I didn't have a config.pck at all, I did cp -r config.pck.last to get
the one I currently have.
Do you have a config.pck.last for that list? Try renaming your current
config.pck and copy over the config.pck.last and see if that works.
If so, then you have a corrupt config.pck file and "check_db" should
have been able to fix this.
Jon Carnes
On Mon, 2003-12-08 at 03:33, Simon White wrote:
Hello
I've seen a few messages with this error in the searchable archive, but
no responses. I've tried to list as much info as I can below. The setup
was working fine until a couple of days ago when an automatic script for
subscribe/unsubscribe suddenly seemed to break things. However the
server h