| Bug #19760 | Upgrade from 4.1 to 5.0 | ||
|---|---|---|---|
| Submitted: | 12 May 2006 9:11 | Modified: | 25 Jun 2006 18:03 |
| Reporter: | Armin Haaf | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.21-1.sles9.x86_64 | OS: | Linux (Linux, SLES 9.0 x86_64) |
| Assigned to: | CPU Architecture: | Any | |
[12 May 2006 9:11]
Armin Haaf
[12 May 2006 13:13]
Valeriy Kravchuk
Thank you for a problem report. Please, send that part of your error log where this startup failure is reflected.
[13 May 2006 8:16]
Armin Haaf
There is nothing in the error log. mysql starts and end without failure message in the error log!
[25 Jun 2006 18:03]
Valeriy Kravchuk
I was not able to repeat the behaviour you described with 5.0.23-BK. I had copied binary logs from 4.1-BK, like that: openxs@suse:~/dbs/5.0> rm var/suse-bin.* openxs@suse:~/dbs/5.0> cp ../4.1/var/suse-bin.* var openxs@suse:~/dbs/5.0> ls -l var/suse-bin.* -rw-r----- 1 openxs users 331 2006-06-25 18:21 var/suse-bin.000001 -rw-r----- 1 openxs users 18 2006-06-25 18:21 var/suse-bin.index openxs@suse:~/dbs/5.0> bin/mysqld_safe --log-bin & [1] 19349 openxs@suse:~/dbs/5.0> Starting mysqld daemon with databases from /home/openxs/d bs/5.0/var openxs@suse:~/dbs/5.0> tail var/suse.err ... 060625 18:21:36 mysqld started 060625 18:21:36 [Warning] No argument was provided to --log-bin, and --log-bin-i ndex was not used; so replication may break when this MySQL server acts as a mas ter and has his hostname changed!! Please use '--log-bin=suse-bin' to avoid this problem. 060625 18:21:36 InnoDB: Started; log sequence number 0 1029082301 060625 18:21:36 [Warning] Neither --relay-log nor --relay-log-index were used; s o replication may break when this MySQL server acts as a slave and has his hostn ame changed!! Please use '--relay-log=suse-relay-bin' to avoid this problem. 060625 18:21:36 [Note] /home/openxs/dbs/5.0/libexec/mysqld: ready for connection s. Version: '5.0.23-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution 060625 18:21:36 [ERROR] Slave I/O thread: error connecting to master 'repl@127.0 .0.1:3340': Error: 'Lost connection to MySQL server during query' errno: 2013 retry-time: 60 retries: 86400 060625 18:21:36 [Note] Slave SQL thread initialized, starting replication in log 'suse-relay-bin.000122' at position 98, relay log './suse-relay-bin.000136' pos ition: 98 So, no crash upon startup (my 5.0.23-BK is a slave itself, but it does not matter). Then: openxs@suse:~/dbs/5.0> bin/mysql -uroot test Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 3 to server version: 5.0.23-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> desc tkill; +-------+---------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------+---------+------+-----+---------+-------+ | s1 | int(11) | YES | | NULL | | +-------+---------+------+-----+---------+-------+ 1 row in set (0.01 sec) mysql> drop table tkill; Query OK, 0 rows affected (0.01 sec) mysql> exit Bye openxs@suse:~/dbs/5.0> ls -l var/suse-bin.* -rw-r----- 1 openxs users 331 2006-06-25 18:21 var/suse-bin.000001 -rw-rw---- 1 openxs users 266 2006-06-25 18:22 var/suse-bin.000002 -rw-r----- 1 openxs users 36 2006-06-25 18:21 var/suse-bin.index So, next binlog just was created, as expected. No problems related to binary logs copied from older version.
