Re: [Cooker] mysql-max 4.0.16 segfaults
onsdagen den 12 november 2003 16.52 skrev Luca Berra: > On Wed, Nov 12, 2003 at 01:02:58AM +0100, Oden Eriksson wrote: > >onsdagen den 12 november 2003 00.06 skrev Luca Berra: > >> 031112 00:03:52 mysqld started > >> mysqld got signal 11; > > > >Weird. It's running just fine on 9.2. Would a rebuild help? > > nope, i tried rebuilding today > mysqld works > mysqld-max segfaults Hmmm..., I'm using this in production and I'm not experiencing any problems like this. You're sure nothing's wrong at your end? To be honest I'm not using max generally, but I have briefly switched over to max but had no problems.
Re: [Cooker] mysql-max 4.0.16 segfaults
On Wed, Nov 12, 2003 at 01:02:58AM +0100, Oden Eriksson wrote: onsdagen den 12 november 2003 00.06 skrev Luca Berra: 031112 00:03:52 mysqld started mysqld got signal 11; Weird. It's running just fine on 9.2. Would a rebuild help? nope, i tried rebuilding today mysqld works mysqld-max segfaults -- Luca Berra -- [EMAIL PROTECTED] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL / \
Re: [Cooker] mysql-max 4.0.16 segfaults
onsdagen den 12 november 2003 00.06 skrev Luca Berra: > 031112 00:03:52 mysqld started > mysqld got signal 11; Weird. It's running just fine on 9.2. Would a rebuild help?
[Cooker] mysql-max 4.0.16 segfaults
031112 00:03:52 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=0x84491f8 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=0xbfffdb38, stack_bottom=0x5040504, thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x5040504 is invalid pointer thd->thread_id=0 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. 031112 00:03:52 mysqld ended -- Luca Berra -- [EMAIL PROTECTED] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL / \
[Cooker] MySQL-Max with no SSL
MySQL-Max-4.0.10-1mdk seems not to be compiled with OpenSSL. I think it's woth including it since it is a new hot 4.0 option. -- Toni Hermoso Pulido -- web: http://www.arrakis.es/~toniher http://caudeldrac.homelinux.org email: [EMAIL PROTECTED] [EMAIL PROTECTED] pgp_public_key: http://www.arrakis.es/~toniher/toniher.pgp *** CĂfratelo, cĂfraselo *** -- signature.asc Description: This is a digitally signed message part
[Cooker] MySQL-Max
What's this? All the '.\c'? root@tl-dhcp-100:/var/lib/mysql# service mysql restart Stopping MySQL Server(pid 3019)Wait for mysqld to exit\c .\c .\c .\c .\c .\c .\c .\c .\c [ OK ] Starting MySQL Server [ OK ] root@tl-dhcp-100:/var/lib/mysql#