linux-traipu team mailing list archive

[Henrik Ingo <henrik.ingo@xxxxxxxxxxxxx>]

It seems when I just build from source and do make install, it works
fine:

hingo@mermaid:~/hacking/drizzle/builds/2012.01.30-src$ sbin/drizzled
InnoDB: The log sequence number in ibdata files does not match the log sequence number in the ib_logfiles!
120124  9:58:10  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...
"/tmp/mysql.socket" exists already. Do you have another Drizzle or MySQL running? Or perhaps the file is stale and should be removed?
120124 10:01:11  InnoDB: Starting shutdown...
hingo@mermaid:~/hacking/drizzle/builds/2012.01.30-src$ 

So it only happens with debs and/or in relation to upstart. Clint, did
you actually reproduce this yet? Or is it purely an issue with my build?

** Changed in: drizzle
   Importance: High => Medium

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/920175

Title:
  shutdown from within Drizzle panics on assertion - upstart respawn
  consequences

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Confirmed
Status in “drizzle” package in Ubuntu:
  Confirmed

Bug description:
  This seems to be specific to running drizzled under upstart, ie modern
  Ubuntu versions. It happens as installed with the debs that come with
  Ubuntu and also the basis for our future own deb downloads. I don't
  know if this is an error in our upstart script, or upstart itself. In
  particular, should upstart with a respawn directive allow the service
  to shutdown when it exits without error?

  The symptom is that "shutdown" given via the client is ineffective /
  becomes a restart.

  
  hingo@mermaid:~/hacking/drizzle/deb$ ps aux|grep drizzle
  root     19723  0.0  0.0   2040   508 ?        Ss   23:33   0:00 /bin/sh -e -c exec /usr/sbin/drizzled --user drizzle 2>&1 | logger -t drizzle -p daemon.err /bin/sh
  drizzle  19724  0.6  1.9 395252 39592 ?        Sl   23:33   0:00 /usr/sbin/drizzled --user drizzle
  root     19725  0.0  0.0   1952   540 ?        S    23:33   0:00 logger -t drizzle -p daemon.err
  hingo    19749  0.0  0.0   5656   800 pts/0    S+   23:33   0:00 grep drizzle
  hingo@mermaid:~/hacking/drizzle/deb$ drizzle --execute="shutdown"
  hingo@mermaid:~/hacking/drizzle/deb$ ps aux|grep drizzle
  root     19752  0.0  0.0   2040   512 ?        Ss   23:33   0:00 /bin/sh -e -c exec /usr/sbin/drizzled --user drizzle 2>&1 | logger -t drizzle -p daemon.err /bin/sh
  drizzle  19753 10.0  1.9 387056 38948 ?        Sl   23:33   0:00 /usr/sbin/drizzled --user drizzle
  root     19754  0.0  0.0   1952   544 ?        S    23:33   0:00 logger -t drizzle -p daemon.err
  hingo    19776  0.0  0.0   5656   796 pts/0    S+   23:33   0:00 grep drizzle
  hingo@mermaid:~/hacking/drizzle/deb$ sudo service drizzle stop
  drizzle stop/waiting
  hingo@mermaid:~/hacking/drizzle/deb$ ps aux|grep drizzle
  hingo    19836  0.0  0.0   5656   800 pts/0    S+   23:40   0:00 grep drizzle
  hingo@mermaid:~/hacking/drizzle/deb$ 

  
  The standard way "service drizzle stop" works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/920175/+subscriptions