MySQL Forums
Forum List  »  Falcon

falcon exception on start-up
Posted by: Martin Waite
Date: September 25, 2008 10:56PM

Hi,

I am having problems starting up mysql 6.0.6 on a debian etch box.

I have downloaded mysql-6.0.6-alpha-linux-i686-glibc23, and followed instructions for installing. However, the server will only run if the --skip-falcon option is set in the my.cnf file.

Digging deeper, with falcon enabled an exception is soon thrown. I have run "strace -f" around the init script, and see the following sequence:

[pid 29247] getcwd("/var/lib/mysql/6.0/data", 4096) = 24
[pid 29247] lstat64("/var/lib/mysql/6.0/data/falcon_master.fts", 0xbfababec) = -1 ENOENT (No such file or directory)
[pid 29247] time(NULL) = 1222402077
[pid 29247] time(NULL) = 1222402077
[pid 29247] unlink("_falcon_backlog.fts") = -1 ENOENT (No such file or directory)
[pid 29247] uname({sys="Linux", node="vm-029-etch-mw", ...}) = 0
[pid 29247] open("/var/lib/mysql/6.0/data/falcon_master.fts", O_RDWR|O_DIRECT|O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid 29247] open("/var/lib/mysql/6.0/data/falcon_master.fts", O_RDWR|O_SYNC|O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid 29247] open("/var/lib/mysql/6.0/data/falcon_master.fts", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid 29247] futex(0x92425bc, FUTEX_WAKE, 2147483647) = 0
[pid 29247] fstat64(2, {st_mode=S_IFREG|0660, st_size=14210, ...}) = 0
[pid 29247] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb203e000
[pid 29247] rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
[pid 29247] write(2, "terminate called after throwing "..., 58) = 58
[pid 29247] tgkill(29247, 29247, SIGABRT) = 0
[pid 29247] --- SIGABRT (Aborted) @ 0 (0) ---


This might be a coincidence, but is the problem that I do not have a "falcon_master.fts" tablespace file ? If so, how/when does it get created ?

The failure generates the following in the error log:

080925 16:02:25 mysqld_safe Starting mysqld-6-0 daemon with databases from /var/lib/mysql/6.0/data
080925 16:02:25 [Note] Plugin 'InnoDB' disabled by command line option
terminate called after throwing an instance of 'SQLError'
/usr/local/mysql-6-0/bin/mysqld-6-0(my_print_stacktrace+0x1c)[0x862b088]
/usr/local/mysql-6-0/bin/mysqld-6-0(handle_segfault+0x2f1)[0x823bc69]
[0xb7f0e420]
/lib/tls/i686/cmov/libc.so.6(abort+0x109)[0xb7c91fb9]
/usr/lib/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x154)[0xb7ec2994]
/usr/lib/libstdc++.so.6[0xb7ec03b5]
/usr/lib/libstdc++.so.6[0xb7ebf6ea]
/usr/lib/libstdc++.so.6(__gxx_personality_v0+0x2c2)[0xb7ec0212]
/usr/local/mysql-6-0/bin/mysqld-6-0[0x86bec13]
/usr/local/mysql-6-0/bin/mysqld-6-0[0x86beccd]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN3Dbb4openEPKcxj+0x437)[0x8442ae3]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN8Database12openDatabaseEPKc+0x25)[0x843a839]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN10Connection11getDatabaseEPKcS1_P7Threads+0xc7)[0x84322db]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN10Connection12openDatabaseEPKcS1_S1_S1_S1_P7Threads+0x76)[0x84327f6]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN15StorageDatabase17getOpenConnectionEv+0x43)[0x8404b03]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN14StorageHandler10initializeEv+0x72)[0x8406d1a]
/usr/local/mysql-6-0/bin/mysqld-6-0(_ZN16StorageInterface11falcon_initEPv+0xd5)[0x83f61f9]
/usr/local/mysql-6-0/bin/mysqld-6-0(_Z24ha_initialize_handlertonP13st_plugin_int+0x36)[0x831d0ba]
/usr/local/mysql-6-0/bin/mysqld-6-0[0x8394479]
/usr/local/mysql-6-0/bin/mysqld-6-0(_Z11plugin_initPiPPci+0x65c)[0x8398de0]
/usr/local/mysql-6-0/bin/mysqld-6-0[0x823e09d]
/usr/local/mysql-6-0/bin/mysqld-6-0(main+0x3f5)[0x8240859]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8)[0xb7c7cea8]
/usr/local/mysql-6-0/bin/mysqld-6-0(__gxx_personality_v0+0x109)[0x818ffd1]
080925 16:02:25 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=67108864
read_buffer_size=1048576
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 375764 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x30000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
080925 16:02:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld-6-0.pid ended



regards,
Martin

Options: ReplyQuote


Subject
Written By
Posted
falcon exception on start-up
September 25, 2008 10:56PM
September 25, 2008 11:30PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.