Re: [Nss-mysql-users] Re: Nss-mysql-users digest, Vol 1 #3 - 2 msgs

[Doug Currey]

>
> The segfault does not appear to happen in the library.. That is weird.
> If this is only thing that is generated before the crash, I guess it is
> an MySQL bug. Did you try to upgrade ?
>
I think it is mysql itself crashing on the nss-mysql stuff but can't figure
out why only the group entry blows its mind.

I went to version 3.23.43 latest stable and do get the same results.
However my err file shows the following,

Again this only happens if nsswitch.conf has the line "group: files mysql"
in it.
---------------------------------------------------------------------
mysqld 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 agaist 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=67104768
record_buffer=1044480
sort_buffer=1048568
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 269931 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbfffe618, stack_bottom=0xffffaba0,
thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer
thd->thread_id=136291072


Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 136291072 did to cause the crash.  In some cases of
really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
011024 18:39:04  mysqld ended
----------------------------------------------------------------------------
-