When we first examined our server logs, we saw the same.. in our case
(again) it was only when we slowed down and examined the timestamps on
the start/stop messages that we realized that the server was
restarting at unexpected intervals. Over the course of our
development, we came across this issue a couple of times.. the
problem was never found to be on the clint or have anything to do with
nefarious sql being executed.. we found binary data issues, build
issues (how did you get your binaries? pre-compiled from the archive
or build your own? and for what OS?) and server config problems..
When you do find the cause let me know; I"m thinking of starting a
On 5/9/07, Jon Ribbens <jon+mysql@stripped> wrote:
> On Wed, May 09, 2007 at 09:22:34AM -0400, Michael Dykman wrote:
> > I realize that's quite unlikely that you have performed a similar
> > sloppy import but there is likely some edge condition on your server
> > (wierd permissions in the data directory, corruoted tables, etc.)
> > but I still recommend that you scrutinize your server logs for
> > evidence of a spontaneous restart. If that turns up nothing, you
> > might try a fresh install of mysql on a separate host to see if the
> > problem persists.
> Thanks for your suggestions. The hostname.err log contains absolutely
> nothing however, just the usual 'mysqld started' and 'Version:' lines.
> Certainly there's nothing about any restart.
> > Worst case, there is an upgrade patch available which might
> > magically raise you above the problem.
> Indeed, I see there is 5.0.37 now. I'd rather not go through an
> upgrade though unless I knew it was likely to fix the problem.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
- michael dykman
- All models are wrong. Some models are useful.