[Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
https://qa.mandrakesoft.com/show_bug.cgi?id=638 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-02-09 12:50 --- Fixed with MySQL-4.0.10-1mdk. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: 021215 00:32:15 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 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=8388600 record_buffer=131072 sort_buffer=2097144 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 = 225791 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=0xbfffdfc8, stack_bottom=0x40662390, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x3f9b1c90 is invalid pointer thd->thread_id=1413825280 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1413825280 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 021215 00:32:15 mysqld ended
Re: [Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
Warly wrote: Warly <[EMAIL PROTECTED]> writes: "[Bug 638]" <[EMAIL PROTECTED]> writes: https://qa.mandrakesoft.com/show_bug.cgi?id=638 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Version|3.23.53-2mdk|3.23.53-5mdk --- Additional Comments From [EMAIL PROTECTED] 2002-12-15 00:51 --- Happens here as well. If I have a look at /var/lib/mysql/*err, I get the impression, that MySQL hasn't been started since July 2002. Guess I don't need it that much ;) Anyhow, both Stefan and I are using LDAP on our systems. I do not know if this is related at all or not... I'm right now using (hmm, let's say, I've got installed) MySQL-3.23.53-5mdk. Could you try with the 3.23.54a-1mdk? No luck here... Stefan smime.p7s Description: S/MIME Cryptographic Signature
[Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
https://qa.mandrakesoft.com/show_bug.cgi?id=638 --- Additional Comments From [EMAIL PROTECTED] 2002-12-26 16:00 --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 poops out here too. I have a fresh cooker install as of this morning about 1am EST. - -- Jason Straight ICQ: 1796276 PGP: http://www.jeetkunedomaster.net/~jason/pubkey.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iQCVAwUBPgsWPhFHZPcobeHxAQIbXwP/b1JJzGEn3WH9CE+it+fgIEgvt1evmvzV 9swmqcyp2sLNM6vTvg3+h4yUU40On+15mZ0YC/akajJysAY/2VtDwKdZF74UWMk2 SmAAnMURs2CJXx/BMHLqHX+4pBp+vvMwVYNq5Udxj+QG2/Gcsb5tWxaHRNHHbYag gEDTmqGPXJI= =CYVA -END PGP SIGNATURE- --- Additional Comments From [EMAIL PROTECTED] 2002-12-26 17:20 --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 26 December 2002 09:46 am, Jason Straight wrote: Mine was because of a perms problem, I installed cooker but my var partition wasn't formatted - mysql dir was owned by htdig. ;) - -- Jason Straight ICQ: 1796276 PGP: http://www.jeetkunedomaster.net/~jason/pubkey.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iQCVAwUBPgsocBFHZPcobeHxAQJFRwP/SJVbkDpSnI5wI2S1iZwB3kEaZ7iGOHve Ny6OSshskYzUem597JIFc8NbN3kHXuCjofoHN/XoeC7JftFcKwTQ5OB6/2ms2BGD g8txLyGqlwwYn5LsLwlQGIzFl6l2S23spZo4IY8DQxnNHMMgmu6XGR0y9DNSLtcg VFurBcn9ycE= =Ndt7 -END PGP SIGNATURE- --- Additional Comments From [EMAIL PROTECTED] 2002-12-30 16:00 --- Warly <[EMAIL PROTECTED]> writes: Could you try with the 3.23.54a-1mdk? --- Additional Comments From [EMAIL PROTECTED] 2003-01-02 18:18 --- 3.23.54a-1mdk still crashes on my machine. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] description: 021215 00:32:15 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 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=8388600 record_buffer=131072 sort_buffer=2097144 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 = 225791 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=0xbfffdfc8, stack_bottom=0x40662390, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x3f9b1c90 is invalid pointer thd->thread_id=1413825280 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1413825280 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 021215 00:32:15 mysqld ended
Re: [Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
Warly <[EMAIL PROTECTED]> writes: > "[Bug 638]" <[EMAIL PROTECTED]> writes: > >> https://qa.mandrakesoft.com/show_bug.cgi?id=638 >> >> [EMAIL PROTECTED] changed: >> >>What|Removed |Added >> >> Status|UNCONFIRMED |NEW >> Ever Confirmed||1 >> Version|3.23.53-2mdk|3.23.53-5mdk >> >> >> >> --- Additional Comments From [EMAIL PROTECTED] 2002-12-15 00:51 >--- >> Happens here as well. If I have a look at /var/lib/mysql/*err, I get the >> impression, that MySQL hasn't been started since July 2002. Guess I don't need >> it that much ;) >> >> Anyhow, both Stefan and I are using LDAP on our systems. I do not know if this >> is related at all or not... I'm right now using (hmm, let's say, I've got >> installed) MySQL-3.23.53-5mdk. Could you try with the 3.23.54a-1mdk? -- Warly
[Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
https://qa.mandrakesoft.com/show_bug.cgi?id=638 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2002-12-26 15:36 --- OK I will try to invesitgate. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] description: 021215 00:32:15 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 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=8388600 record_buffer=131072 sort_buffer=2097144 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 = 225791 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=0xbfffdfc8, stack_bottom=0x40662390, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x3f9b1c90 is invalid pointer thd->thread_id=1413825280 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1413825280 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 021215 00:32:15 mysqld ended
Re: [Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
Am Montag, 16. Dezember 2002 13:58 schrieb Brian Smith: > On Mon, 16 Dec 2002 12:32:21 +0100 > > Warly <[EMAIL PROTECTED]> wrote: > >"[Bug 638]" <[EMAIL PROTECTED]> writes: > >> https://qa.mandrakesoft.com/show_bug.cgi?id=638 > >> > >> [EMAIL PROTECTED] changed: > >> > >>What|Removed |Added > >> - > >>--- Status|UNCONFIRMED |NEW > >> Ever Confirmed||1 > >> Version|3.23.53-2mdk > >> > >> |3.23.53-5mdk > >> > >> --- Additional Comments From > >>[EMAIL PROTECTED] 2002-12-15 00:51 --- > >> Happens here as well. If I have a look at > >>/var/lib/mysql/*err, I get the > >> impression, that MySQL hasn't been started since July > >>2002. Guess I don't need > >> it that much ;) > >> > >> Anyhow, both Stefan and I are using LDAP on our systems. > >> I do not know if this > >> is related at all or not... I'm right now using (hmm, > >>let's say, I've got > >> installed) MySQL-3.23.53-5mdk. > > > >I cannot reproduce, are you using a full cooker install ? > > I'm having the same problem, on both my Cooker and 9.0 > boxes. It might be related to LDAP somehow, I think folks > using LDAP are rare enough that we find some odd bugs that > noone else can reproduce. Yes, it is definitely caused by LDAP. I have done some tests with the nsswitch.conf and if the group section looks up into LDAP the MySQL server crashes. Entries in password and shadow does not mater. I have three solutions: 1. grap the src.rpm from mdk8.2, recompile it and force a install (I have not seen any sideeffects until now) This MySQL version does not have any problems. 2. change the mysql-init script and start the safe_mysqld as user mysql (with 'su - mysql -c'). 3. change the mysql-init script: move away the nsswitch.conf befor the start of safe_mysqld and move it back after the start of safe_mysqld. beware: use a little timeout before moving it back (1 to 2 seconds) because safe_mysqd is started asyncronous. mysql ist faster with moving back than safe_mysqld can start mysqld. Martin -- H E L I X Gesellschaft für Software & Engineering mbH Hanauer Landstrasse 52 Telefon (069) 4789 35-30 60314 Frankfurt am Main Telefax (069) 4789 35-44 http://www.helix-gmbh.net[EMAIL PROTECTED] msg83995/pgp0.pgp Description: signature
Re: [Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
"[Bug 638]" <[EMAIL PROTECTED]> writes: > https://qa.mandrakesoft.com/show_bug.cgi?id=638 > > [EMAIL PROTECTED] changed: > >What|Removed |Added > > Status|UNCONFIRMED |NEW > Ever Confirmed||1 > Version|3.23.53-2mdk|3.23.53-5mdk > > > > --- Additional Comments From [EMAIL PROTECTED] 2002-12-15 00:51 --- > Happens here as well. If I have a look at /var/lib/mysql/*err, I get the > impression, that MySQL hasn't been started since July 2002. Guess I don't need > it that much ;) > > Anyhow, both Stefan and I are using LDAP on our systems. I do not know if this > is related at all or not... I'm right now using (hmm, let's say, I've got > installed) MySQL-3.23.53-5mdk. I cannot reproduce, are you using a full cooker install ? -- Warly
[Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
https://qa.mandrakesoft.com/show_bug.cgi?id=638 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] description: 021215 00:32:15 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 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=8388600 record_buffer=131072 sort_buffer=2097144 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 = 225791 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=0xbfffdfc8, stack_bottom=0x40662390, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x3f9b1c90 is invalid pointer thd->thread_id=1413825280 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1413825280 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 021215 00:32:15 mysqld ended
[Cooker] [Bug 638] [MySQL] mysql won't start, invalid pointer?
https://qa.mandrakesoft.com/show_bug.cgi?id=638 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Version|3.23.53-2mdk|3.23.53-5mdk --- Additional Comments From [EMAIL PROTECTED] 2002-12-15 00:51 --- Happens here as well. If I have a look at /var/lib/mysql/*err, I get the impression, that MySQL hasn't been started since July 2002. Guess I don't need it that much ;) Anyhow, both Stefan and I are using LDAP on our systems. I do not know if this is related at all or not... I'm right now using (hmm, let's say, I've got installed) MySQL-3.23.53-5mdk. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] description: 021215 00:32:15 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 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=8388600 record_buffer=131072 sort_buffer=2097144 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 = 225791 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=0xbfffdfc8, stack_bottom=0x40662390, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x3f9b1c90 is invalid pointer thd->thread_id=1413825280 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1413825280 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 021215 00:32:15 mysqld ended
