On Sat, Mar 09, 2002 at 01:21:44PM -0700, Sasha Pachev wrote:
> On Saturday 09 March 2002 12:46 pm, Jeremy Zawodny wrote:
> > That reminds me of an easy feature request. ?Would it be possible to
> > have a slave-auto-start=no option (or something like that) in my.cnf?
> > There have been cases whe
On Saturday 09 March 2002 12:46 pm, Jeremy Zawodny wrote:
> That reminds me of an easy feature request. ?Would it be possible to
> have a slave-auto-start=no option (or something like that) in my.cnf?
> There have been cases when I want to start a server but do not want
> replication to start on i
On Sat, Mar 09, 2002 at 12:31:20PM -0700, Sasha Pachev wrote:
>
> Jeremy:
>
> I think I now understand what happened, or at least I have a
> pausilble theory that explains what I see in the logs.
>
> When I had you kill the broken mysqld last time it went down in the
> middle of updating db3-re
On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote:
> The 4.0.x slave I had just rebuilt the other day died about 40 minutes
> ago and produced a core file each time. ?It got caught in the cycle of
> "core dump, restart, core dump, restart..."
Jeremy:
I think I now understand what happened
On Fri, Mar 08, 2002 at 05:10:02PM -0800, Jeremy Zawodny wrote:
> >
> > I have tracked down and fixed the assertion failure issue. However,
> > I am still not certail why the sql thread does partial reads. I have
> > pushed my fix into the public tree, so let's have you pull it and
> > try again.
On Fri, Mar 08, 2002 at 03:14:31PM -0700, Sasha Pachev wrote:
> On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote:
> > The 4.0.x slave I had just rebuilt the other day died about 40 minutes
> > ago and produced a core file each time. ?It got caught in the cycle of
> > "core dump, restart, c
On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote:
> The 4.0.x slave I had just rebuilt the other day died about 40 minutes
> ago and produced a core file each time. ?It got caught in the cycle of
> "core dump, restart, core dump, restart..."
Jeremy:
I have tracked down and fixed the asse
On Fri, Mar 08, 2002 at 10:41:32AM -0700, Sasha Pachev wrote:
> On Thursday 07 March 2002 11:39 pm, Jeremy Zawodny wrote:
> > 020307 21:39:03 ?Error in Log_event::read_log_event(): 'read error',
> data_len=193,event_type=2
> > 020307 21:39:03 ?Slave SQL thread: I/O error reading
> event(errno=-1
On Thursday 07 March 2002 11:39 pm, Jeremy Zawodny wrote:
> 020307 21:39:03 ?Error in Log_event::read_log_event(): 'read error',
data_len=193,event_type=2
> 020307 21:39:03 ?Slave SQL thread: I/O error reading
event(errno=-1,cur_log->error=57)
> assertion "mi->io_thd == thd" failed: file "slave.
On Thu, Mar 07, 2002 at 09:48:41PM -0800, Jeremy Zawodny wrote:
> Hey Sasha,
[snip]
> I'll keep it off-line until I hear from you on what data you need.
Oops. Here's the info form the error log:
---snip---
020307 21:39:03 Slave I/O thread initialized
020307 21:39:03 Slave SQL thread initia
Hey Sasha,
The 4.0.x slave I had just rebuilt the other day died about 40 minutes
ago and produced a core file each time. It got caught in the cycle of
"core dump, restart, core dump, restart..."
In any case, here's a backtrace:
#0 0x2839d330 in kill () from /usr/lib/libc_r.so.4
#1 0x283e9ab
11 matches
Mail list logo
