Comment 7 for bug 597905
Revision history for this message
| Patrick Crews (patrick-crews) wrote Re: [Bug 597905] Re: Bad permissions on DATADIR/.temporary causes Segmentation Fault | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I would say that you are on the right track. The test language has
shutdown_server [timeout], but we don't have a handy start_server. The
MySQL test suite has some examples of this kind of stuff in the rpl suite
+ t/crash_
tomorrow if you need any help.
On Sat, Jul 10, 2010 at 4:43 AM, LinuxJedi <email address hidden> wrote:
> Not sure how to express this in a dtr. My best guess would be to create
> a .temporary directory, chown 000 and start drizzled which would cover
> part of this. But how do you create a directory and chown before
> drizzled is started? (I am guessing the dtr test case has to shut down
> drizzled and start it again?).
>
> --
> Bad permissions on DATADIR/.temporary causes Segmentation Fault
> https:/
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud and Web: Fix Committed
>
> Bug description:
> I ran into an obscure segmentation fault after [most likely] inadvertently
> running drizzled as root instead of as 'drizzle':
>
> [root@f12-drizzle ~]# sudo -u drizzle drizzled
> InnoDB: The InnoDB memory heap is disabled
> InnoDB: Mutexes and rw_locks use GCC atomic builtins.
> 100623 23:15:29 - drizzled got signal 11;
> 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.
>
> GDB Back Trace (with some debug symbols missing):
>
> -bash-4.0$ gdb drizzled
> GNU gdb (GDB) Fedora (7.0.1-48.fc12)
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-
> For bug reporting instructions, please see:
> <http://
> Reading symbols from /usr/sbin/
> /usr/lib/
> done.
>
> (gdb) run
> Starting program: /usr/sbin/drizzled
> [Thread debugging using libthread_db enabled]
> InnoDB: The InnoDB memory heap is disabled
> InnoDB: Mutexes and rw_locks use GCC atomic builtins.
> Program received signal SIGSEGV, Segmentation fault.
>
> (gdb) bt full
> #0 0x0000000000000000 in ?? ()
> No symbol table info available.
> #1 0x00000000006722ab in drizzled::my_error (nr=2, MyFlags=36) at
> drizzled/
> format = "Can't create file '%-.200s' (errno: %d)"
> args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
> 0x7fffffffb1c0,
> reg_save_area = 0x7fffffffb0d0}}
> ebuff = "Can't create file '/var/lib/
> (errno: 13)\000\
> \336\376\
> \336\376\
> "\001\000\
> \253\264\
> '\000' <repeats 21 times>,
> "o\262\
> #2 0x00000000006554f4 in drizzled:
> (fd=<value optimized out>,
> FileName=0x24 <Address 0x24 out of bounds>, error_message_
> optimized out>,
> MyFlags=<value optimized out>) at drizzled/
> No locals.
> #3 0x0000000000654d6e in drizzled:
> to=0x7fffffffb250 "/var/lib/
> dir=0xbae158 "/var/lib/
> out>, MyFlags=16)
> at drizzled/
> file = -1
> org_file = -1
> prefix_str = "ibXXXXXX"
> #4 0x00000000005c7965 in drizzled:
> 0x24 out of bounds>)
> at drizzled/
> filename =
> "/var/lib/
> '\000' <repeats 15 times>"\240, ", '\000' <repeats 23 times>,
> "p\263\
> '\000' <repeats 14 times>,
> "%\032\
> '\000' <repeats 15 times>"\240, \000\000\
> fd = <value optimized out>
> #5 0x00000000006a3547 in innobase_
> plugin/
>
>
>
> THE FIX:
>
> Setting the ownership on /var/lib/
> resolved the issue:
>
>
> [root@f12-drizzle ~]# chown -R drizzle:drizzle
> /var/lib/
>
> [root@f12-drizzle ~]# sudo -u drizzle drizzled
> InnoDB: The InnoDB memory heap is disabled
> InnoDB: Mutexes and rw_locks use GCC atomic builtins.
> 100623 23:14:45 InnoDB: highest supported file format is Barracuda.
> 100623 23:14:45 InnoDB Plugin 1.0.4 started; log sequence number 44534
> Listening on 0.0.0.0:9306
> Listening on :::9306
> Listening on 0.0.0.0:3306
> Listening on :::3306
> drizzled: Forcing close of thread 0 user: ''
> drizzled: ready for connections.
> Version: '2010.06.1634' Source distribution (trunk)
> drizzled: Normal shutdown
> drizzled: Shutdown complete
> 100623 23:15:00 InnoDB: Starting shutdown...
> 100623 23:15:00 InnoDB: Shutdown completed; log sequence number 44560
>
>
> SUGGESTION:
>
> Properly check for the ability to read/write on DATADIR/.temporary and
> catch the error condition.. providing a useful error message to the user
> (rather than allowing a segmentation fault condition)
>
>
>