Hi All,
Running with the MySQL 5.1.19 (Linux) I am getting some strange
behavior on shutdown:
If I start MySQL, do a SELECT on a PBXT table, and then shutdown
MySQL, I get the following:
070622 13:19:17 [Note] Event Scheduler: Purging the queue. 0 events
070622 13:19:17 InnoDB: Starting shutdown...
070622 13:19:19 InnoDB: Shutdown completed; log sequence number 0 46409
070622 13:19:19 [Warning] Forcing shutdown of 1 plugins
070622 13:19:19 [Note] Plugin 'PBXT' will be forced to shutdown
070622 13:19:19 [Note] PrimeBase XT Engine shutdown...
070622 13:19:19 [Note] libexec/mysqld: Shutdown complete
Why is MySQL forced to shutdown PBXT?
Is there something I can do to have MySQL shutdown PBXT "normally"?
After this, MySQL hangs sometimes, with the following threads active:
(gdb) info threads
2 Thread 1152089008 (LWP 25195) 0xffffe410 in ?? ()
1 Thread 1076666144 (LWP 25185) 0xffffe410 in ?? ()
(gdb) thread 1
[Switching to thread 1 (Thread 1076666144 (LWP 25185))]#0 0xffffe410
in ?? ()
(gdb) where
#0 0xffffe410 in ?? ()
#1 0xbfdf6cc8 in ?? ()
#2 0x00000000 in ?? ()
#3 0xbfdf6bd8 in ?? ()
#4 0x4020ef61 in ___newselect_nocancel () from /lib/tls/libc.so.6
#5 0x08224d26 in handle_connections_sockets (arg=0x0) at mysqld.cc:4388
#6 0x0822a297 in main (argc=2, argv=0xbfdf6da4) at mysqld.cc:3909
(gdb) thread 2
[Switching to thread 2 (Thread 1152089008 (LWP 25195))]#0 0xffffe410
in ?? ()
(gdb) where
#0 0xffffe410 in ?? ()
#1 0x44ab7374 in ?? ()
#2 0x00000000 in ?? ()
#3 0x00000000 in ?? ()
#4 0x4004365e in do_sigwait () from /lib/tls/libpthread.so.0
#5 0x400436ff in sigwait () from /lib/tls/libpthread.so.0
#6 0x0822a67b in signal_hand (arg=0x0) at mysqld.cc:2434
#7 0x4003d297 in start_thread () from /lib/tls/libpthread.so.0
#8 0x4021637e in clone () from /lib/tls/libc.so.6
#9 0x44ab7bb0 in ?? ()
This is running with PBXT 0.9.86, which did not have this problem in
MySQL 5.1.16.
If I don't do the SELECT, MySQL shuts down normally.
Any ideas would be welcome.
Thanks,
Paul
