Bug #10864 rpl_openssl test hangs
Submitted: 25 May 2005 17:57 Modified: 25 May 2005 18:33
Reporter: Kathiravan Velusamy Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.12 OS:HP/UX (HP-Unix)
Assigned to: CPU Architecture:Any

[25 May 2005 17:57] Kathiravan Velusamy
Description:
I have built MySQL 4.1.12 in Hp-Unix platform with OpenSSL support. 
Following are my configuration options I have used to build,

./configure --prefix=/opt/iexpress/mysql --localstatedir=/var/opt/iexpress/mysql     --enable-thread-safe-client  --with-named-thread-libs=/usr/lib/libpthread.1 
--with-zlib-dir=/usr/local --with-vio --with-openssl=/opt/openssl 

  When i tried to run the tests inside mysql-test directory after the gmake as,

./mysql-test-run

"openssl_1" and "rpl_openssl" are skipped eventhough i have compiled with OpenSSL.

 Soi have rerun these tests alone as,

./mysql-test-run --with-openssl openssl_1 rpl_openssl

Now openssl_1 test passed but rpl_openssl get hanged.

I have checked the slave.err file, it seems that access denied for slave and it is looks for "sync_with_master", as it was not able to connect, it get hanged.

The slave.err log details is given below,

==================================begin========================
CURRENT_TEST: rpl_openssl
/disk1/release5/mysql/4.1.12/Source/mysql-4.1.12/sql/mysqld: ready for connections.
Version: '4.1.12-log'  socket: '/disk1/release5/mysql/4.1.12/Source/mysql-4.1.12/mysql-test/var/tmp/slave.sock'
 port: 9308  Source distribution
050525 19:11:41 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay lo
g '/disk1/release5/mysql/4.1.12/Source/mysql-4.1.12/mysql-test/var/log/slave-relay-bin.000001' position: 4
050525 19:11:41 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:9306',  replication started in log
'FIRST' at position 4
050525 19:11:41 [ERROR] Slave I/O thread killed while reading event
050525 19:11:41 [ERROR] Slave I/O thread exiting, read up to log 'master-bin.000001', position 229
050525 19:11:41 [ERROR] Error reading relay log event: slave SQL thread was killed
050525 19:11:41 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position
 229, relay log '/disk1/release5/mysql/4.1.12/Source/mysql-4.1.12/mysql-test/var/log/slave-relay-bin.000001' pos
ition: 4
050525 19:11:41 [Note] Slave I/O thread: connected to master 'replssl@127.0.0.1:9306',  replication started in l
og 'master-bin.000001' at position 229
050525 19:11:41 [ERROR] Error on COM_REGISTER_SLAVE: 1045 'Access denied for user ''@'localhost' (using password
: NO)'
050525 19:11:41 [ERROR] Slave I/O thread exiting, read up to log 'master-bin.000001', position 229
050525 19:11:44 [ERROR] Error reading relay log event: slave SQL thread was killed
050525 19:11:44 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position
 229, relay log '/disk1/release5/mysql/4.1.12/Source/mysql-4.1.12/mysql-test/var/log/slave-relay-bin.000001' pos
ition: 4
050525 19:11:44 [Note] Slave I/O thread: connected to master 'replssl@127.0.0.1:9306',  replication started in l
og 'master-bin.000001' at position 229
050525 19:11:44 [ERROR] Error on COM_REGISTER_SLAVE: 1045 'Access denied for user ''@'localhost' (using password
: NO)'
050525 19:11:44 [ERROR] Slave I/O thread exiting, read up to log 'master-bin.000001', position 229
========================end=======================

I have faced the same issue when i used MySQL 4.1.10a.
Please suggest a fix or workaround for this problem...
Or am i do anything wrong to this tests ?

How to repeat:
Run the MySQL OpenSSL tests in MySQL 4.1.12 source as,

./mysql-test-run --with-openssl rpl_openssl

  You will see it get hanged
[25 May 2005 18:33] Jim Winstead
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

Duplicate of Bug #10860.