Trouble's a'brewing ... database weas not shut down normally

[Daniel Kasak]

Number of processes running now: 0
050502 20:31:26  mysqld restarted
050502 20:31:27  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 301734057
InnoDB: Doing recovery: scanned up to log sequence number 0 301734057
InnoDB: Last MySQL binlog file position 0 2049456, file name
./screamer-bin.021
050502 20:31:27  InnoDB: Flushing modified pages from the buffer pool...
050502 20:31:27  InnoDB: Started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.24-log'  socket: '/var/run/mysqld/mysqld.sock'  port:
3306  Gentoo Linux mysql-4.0.24
A mysqld process already exists at  Mon May 2 20:31:58 EST 2005

My 'backup' ( basically shutdown, truncate query log, start again )
script looks like:

---

for I in database_1 database_2 database_3
do
        mysqldump --opt $I > $I.sql -psome_password
done

/etc/init.d/mysql stop
sleep 30
echo "" > /var/log/mysql/mysql.log
/etc/init.d/mysql start

---

There would have been nothing else happening at the time of the backup -
everyone was at home.
Whenever I see stuff in the logs like the above, I start to worry.
Should I 'trust' everything is OK, or dump, restore from a backup, and
process the transaction log?

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: ([phone] / F: ([phone]
email: dkasak@stripped
website: http://www.nusconsulting.com.au