Hi,

I have a mysql slave database, that, for various reasons, got quite out
of date with its master. Friday, when I left, it was happily chugging
along playing catch-up, or so it seemed. However, now it looks as if
it's just decided to leave off work with this file:

Relay_Master_Log_File: mammut-bin.024

(other slave information)
Master_Log_File: mammut-bin.024
Read_Master_Log_Pos: 205353759
Relay_Log_File: bisonte-relay-bin.058
Relay_Log_Pos: 4
Relay_Master_Log_File: mammut-bin.024
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_do_db: ............
Replicate_ignore_db:
Last_errno: 0
Last_error:
Skip_counter: 0
Exec_master_log_pos: 205353759

the problem is that there are newer files on the server:

mammut-bin.025
mammut-bin.026

I'm looking for a way to give it a kick and make it fully catch up the
main server. How might I accomplish this?

Thankyou,
Dave Welton

It turns out it was stuck trying to authenticate - someone fiddled with
the /etc/hosts file, and that caused the authentication to get weird,
so it wasn't authenticating. Solving that fixed everything.