> >Well... today I can't seem to reproduce the problem anymore. :/ I was
> >getting it very frequently yesterday (on almost every try). I'm not sure
> >what has changed since then. I'll let you know if the problem happens
again
> >and try to narrow down the exact steps to reproduce.
>
> Is it possible that you had a replicated system running, where the master
> was your updated 3.23.34 and a slave still had 3.23.33 running? -
>
> The same happened to me last night after I updated one of my masters to
> 3.23.34, but still left the slave running 3.23.33 for later updating.
After
> several operations running locally on the new master's version, the same
> error occured. It immediately disappeared after I upgraded the slave to
> 3.23.34 too. Never saw it again.
Hmm, I'm not using replication, but possibly some piece of the old server
was still running(?). I didn't ensure the old server was stopped before I
upgraded the RPM...
Jordan Russell
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
