Hi again, sorry for replying to my own message, but I found the [obscure] problem.
turns out mysql doesn't like getting its gid information from an LDAP server. There is no mention of this in any of the docs I found, but I will do more looking this morning. The solution was to change my nsswitch.conf file from group: files ldap to group: files and this solved things. I think this is dumb and should be fixed/changed in mysql. I now have to have my group definitions on every system, even though the information for users is taken from LDAP. (and yes, I've tried simply creating a local group/user for mysql, but to no avail - so long as the "group" line contains "ldap" in nsswitch.conf, mysql falls over). -Dan On Mon, 29 Dec 2003, Dan Goodes wrote: > Hi folks, > > just compiled up mysql-4.0.17.tar.gz on a (stock, basic install) RHEL3 > system, and get similar symptoms to something I experienced a while ago > with RH9. that is... it compiles fine, but wont start. > > The ./configure options are: > > ./configure '--prefix=/opt/local/stow/mysql-4.0.17' '--without-innodb' \ > '--without-debug' '--with-extra-charsets=none' '--enable-assembler' \ > '--localstatedir=/data/mysql' '--with-mysqld-ldflags=-all-static' > > > The output i get in my error log file is: > > 031229 13:04:33 mysqld started > 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 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. > > key_buffer_size=8388600 > read_buffer_size=131072 > max_used_connections=0 > max_connections=100 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x82a8378 > 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=0xbfff62c8, stack_bottom=0x6a696867, > thread_stack=196608, aborting backtrace. > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x66656463 is invalid pointer > thd->thread_id=137005528 > The manual page at http://www.mysql.com/doc/en/Crashing.html contains > information that should help you find out what is causing the crash. > 031229 13:04:33 mysqld ended > > > > If anybody has any ideas please help. > > -Dan > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > Regards, Dan Goodes : Systems Programmer : [EMAIL PROTECTED] Help support PlanetMirror - Australia's largest Internet archive by signing up for PlanetMirror Premium : http://planetmirror.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
