Ok, I see why it respawns: it doesn't actually exit cleanly. This is what it looks like when you do shutdown from inside drizzled...
hingo@mermaid:~/hacking/drizzle/deb$ sudo /usr/sbin/drizzled --user=drizzle
InnoDB: The log sequence number in ibdata files does not match the log sequence number in the ib_logfiles!
120123 19:46:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
drizzled: /usr/include/boost/smart_ptr/shared_ptr.hpp:418: T* boost::shared_ptr<T>::operator->() const [with T = const std::basic_string<char>]: Assertion `px != 0' failed.
120123 19:46:19 - drizzled 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.
read_buffer_size=131072
max_used_connections=1
connection_count=1
It is possible that drizzled could use up to
(read_buffer_size + sort_buffer_size)*thread_count
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Ok, I see why it respawns: it doesn't actually exit cleanly. This is what it looks like when you do shutdown from inside drizzled...
hingo@mermaid: ~/hacking/ drizzle/ deb$ sudo /usr/sbin/drizzled --user=drizzle boost/smart_ ptr/shared_ ptr.hpp: 418: T* boost:: shared_ ptr<T>: :operator- >() const [with T = const std::basic_ string< char>]: Assertion `px != 0' failed.
InnoDB: The log sequence number in ibdata files does not match the log sequence number in the ib_logfiles!
120123 19:46:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
drizzled: /usr/include/
120123 19:46:19 - drizzled 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.
read_buffer_ size=131072 connections= 1 size)*thread_ count
max_used_
connection_count=1
It is possible that drizzled could use up to
(read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
call_backtrace() began at drizzled/ signal_ handler. cc:156 for drizzled_ handle_ segfault( ) drizzled( ) [0x81a6fea] :__normal_ iterator< drizzled: :plugin: :Logging* *, std::vector< drizzled: :plugin: :Logging* , std::allocator< drizzled: :plugin: :Logging* > > > std::__ find_if< __gnu_cxx: :__normal_ iterator< drizzled: :plugin: :Logging* *, std::vector< drizzled: :plugin: :Logging* , std::allocator< drizzled: :plugin: :Logging* > > >, drizzled: :PostIterate> (__gnu_ cxx::__ normal_ iterator< drizzled: :plugin: :Logging* *, std::vector< drizzled: :plugin: :Logging* , std::allocator< drizzled: :plugin: :Logging* > > >, __gnu_cxx: :__normal_ iterator< drizzled: :plugin: :Logging* *, std::vector< drizzled: :plugin: :Logging* , std::allocator< drizzled: :plugin: :Logging* > > >, drizzled: :PostIterate, std::random_ access_ iterator_ tag) :plugin: :Logging: :postDo( drizzled: :Session* ) drizzled( ) [0x81c2b87] :Session: :executeStateme nt() :Session: :run() ~/hacking/ drizzle/ deb$
Number of stack frames obtained: 19
/usr/sbin/
[0x5a1400]
[0x5a1416]
gsignal()
abort()
__assert_fail()
()
()
__gnu_cxx:
drizzled:
/usr/sbin/
drizzled:
drizzled:
()
()
thread_proxy()
()
clone()
[1]- Killed sudo /usr/sbin/drizzled --user=drizzle
[2]+ Killed sudo /usr/sbin/drizzled --user=drizzle
hingo@mermaid:
It could of course be something related to my own build. Have to continue investigation...