Bug #39240 Falcon disclaims existing directory
Submitted: 4 Sep 2008 12:04 Modified: 4 Sep 2008 18:07
Reporter: Daniel Fischer Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version:6.0 OS:Any
Assigned to: CPU Architecture:Any

[4 Sep 2008 12:04] Daniel Fischer
Description:
As of recently, the pushbuild 2 gcov build is not testing Falcon because it refuses to initialize itself, disclaiming the existance of the mysql test var directory that is created by mysql-test-run.pl.

First observed in mysql-6.0 after the push that brought it to revision vvaintroub@mysql.com-20080827144354-lptt2zlg8con9d05.

$ stat /export/home/pb2/tmp/mysql-6.0-gcov/mysql-test/var/master-data
  File: `/export/home/pb2/tmp/mysql-6.0-gcov/mysql-test/var/master-data'
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 805h/2053d      Inode: 7307728     Links: 4
Access: (0755/drwxr-xr-x)  Uid: ( 7155/   bteam)   Gid: (   10/   wheel)
Access: 2008-09-04 13:59:42.000000000 +0200
Modify: 2008-09-04 13:59:40.000000000 +0200
Change: 2008-09-04 13:59:40.000000000 +0200

$ perl mysql-test-run.pl --suite falcon falcon_bugs
Logging: mysql-test-run.pl --suite falcon falcon_bugs
MySQL Version 6.0.7
Using dynamic switching of binlog format
Using ndbcluster when necessary, mysqld supports it
Setting mysqld to support SSL connections
Binaries are debug compiled
Using MTR_BUILD_THREAD      = 14
Using MASTER_MYPORT         = 10140
Using MASTER_MYPORT1        = 10141
Using SLAVE_MYPORT          = 10142
Using SLAVE_MYPORT1         = 10143
Using SLAVE_MYPORT2         = 10144
Using NDBCLUSTER_PORT       = 10145
Using NDBCLUSTER_PORT_SLAVE = 10146
Killing Possible Leftover Processes
Removing Stale Files
Creating Directories
Installing Master Database
=======================================================

TEST                           RESULT         TIME (ms)
-------------------------------------------------------

falcon.falcon_bugs             [ skipped ]   Test needs the Falcon storage engine
-------------------------------------------------------
Stopping All Servers
All 0 tests were successful.
The servers were restarted 1 times
Spent 0.000 of 2 seconds executing testcases
mysql-test-run: WARNING: Got errors/warnings while running tests, please examine "/export/home/pb2/tmp/mysql-6.0-gcov/mysql-test/var/log/warnings" for details.

mysql-test-run: *** ERROR: there were failing test cases

$ cat var/log/master.err
CURRENT_TEST: falcon.falcon_bugs
080904 14:59:47 [Note] Plugin 'InnoDB' disabled by command line option
Falcon: The specified serial log directory, "/export/home/pb2/tmp/mysql-6.0-gcov/mysql-test/var/master-data/", does not exist.
Falcon: The serial log directory must be created by the user before initializing Falcon.
080904 14:59:47 [ERROR] Falcon: Exception 'Invalid serial log directory path "/export/home/pb2/tmp/mysql-6.0-gcov/mysql-test/var/master-data/"' during initialization
080904 14:59:47 [ERROR] Plugin 'Falcon' init function returned error.
080904 14:59:47 [ERROR] Plugin 'Falcon' registration as a STORAGE ENGINE failed.
080904 14:59:47 [Note] Event Scheduler: Loaded 0 events
080904 14:59:47 [Note] /export/home/pb2/tmp/mysql-6.0-gcov/sql/mysqld: ready for connections.
Version: '6.0.7-alpha-gcov-debug-log'  socket: '/export/home/pb2/tmp/mysql-6.0-gcov/mysql-test/var/tmp/master.sock'  port: 10140  Source distribution
080904 14:59:48 [Note] Got signal 15 to shutdown mysqld
080904 14:59:48 [Note] /export/home/pb2/tmp/mysql-6.0-gcov/sql/mysqld: Normal shutdown

080904 14:59:48 [Note] Event Scheduler: Purging the queue. 0 events
080904 14:59:48 [Note] Debug sync points hit:                   16
080904 14:59:48 [Note] Debug sync points executed:              0
080904 14:59:48 [Note] Debug sync points max active per thread: 0
080904 14:59:48 [Note] /export/home/pb2/tmp/mysql-6.0-gcov/sql/mysqld: Shutdown complete

How to repeat:
Build and test in the same way as the pushbuild 2 gcov build.
[4 Sep 2008 18:07] Sveta Smirnova
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.

Duplicate of bug #39194 or even bug #39098