Hi, aren't there any other clues before restarting? 2009/5/20 Duane Hebert <duane.heb...@group-upc.com>
> I'm having a problem where every day or so, the mysql service is > restarting. This is MySql 5 running on a win2003 server. > The error in the event log says: > > Faulting application mysqld-nt.exe, version 0.0.0.0, faulting module > mysqld-nt.exe, version 0.0.0.0, fault address 0x001fa173. > > In MySql's error file, it only shows that the service stopped unexpectedly > and it's trying to recover: > > Version: '5.0.18-nt' socket: '' port: 3306 MySQL Community Edition (GPL) > 090519 8:04:31 InnoDB: Database was not shut down normally! > InnoDB: Starting crash recovery. > InnoDB: Reading tablespace information from the .ibd files... > InnoDB: Restoring possible half-written data pages from the doublewrite > InnoDB: buffer... > 090519 8:04:32 InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 7 3461755255. > InnoDB: Doing recovery: scanned up to log sequence number 7 3461778224 > 090519 8:04:32 InnoDB: Starting an apply batch of log records to the > database... > InnoDB: Progress in percents: 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 > 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 > 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 > 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 > 88 89 90 91 92 93 94 95 96 97 98 99 > InnoDB: Apply batch completed > InnoDB: Last MySQL binlog file position 0 0, file name > 090519 8:04:32 InnoDB: Started; log sequence number 7 3461778224 > 090519 8:04:32 [Note] D:\Mysql\bin\mysqld-nt: ready for connections. > > > I have excluded the mysql data directory from the virus scan (Trend Micro) > and this seems to have reduced the frequency > but it still happens every day or two. > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com > >
