mysql 4.0.2 linux-i386 crash

Hi,
I've a problem with mysql crash on linux 2.4.19-pre2. We use only myisam
tables.

How-To-Repeat:

key_buffer_size=134213632
record_buffer=1044480
sort_buffer=2097144
max_used_connections=100
max_connections=100
threads_connected=57
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 437867 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xba1d1d0
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...
Cannot determine thread, fp=0xbf3be9a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:

0x8071b58 reset_fields__10Field_blob + 8
0x825a668 __evoke_link_warning_llseek + 182600
0x825bc03 __evoke_link_warning_llseek + 188131
0x8258ce4 __evoke_link_warning_llseek + 176068
0x8256dc9 __evoke_link_warning_llseek + 168105
0x80cdd7b mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13s t_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10A lter_dr + 7491
0x80cd811 mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13s t_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10A lter_dr + 6105
0x80cd334 mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13s t_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10A lter_dr + 4860
0x807c9cd create_new_thread__FP3THD + 261
0x807d955 get_options__FiPPc + 1861
0x8078ed3 my_lock + 307
0x807ece1 kill_server_thread__FPv + 49
0x80780ae send_warning__FP6st_netUiPCc + 50
0x8257c7c __evoke_link_warning_llseek + 171868
0x828d3ba __evoke_link_warning_llseek + 390810

New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x775cc5e0 is invalid pointer
thd->thread_id=86646

TIA
--
Martin Mokrejs ,
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12366@lists.mysql.com
To unsubscribe, e-mail

mysql 4.0.2 linux-i386 crash

Hi,

The stacktrace alone is not useful to us...

=?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:
> Hi,

> New value of fp=(nil) failed sanity check, terminating stack trace!
> Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
> stack trace is much more helpful in diagnosing the problem, so please do
> resolve it
> Trying to get some variables.


Please follow the instructions from the URL above.

Regards,

- Jani

For technical support contracts, visit https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Jani Tolonen
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
<___/ www.mysql.com

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12367@lists.mysql.com
To unsubscribe, e-mail

Re: mysql 4.0.2 linux-i386 crash

=3D?iso-8859-2?Q?Martin_MOKREJ=3DA9?=3D writes:
> Hi,
> I've a problem with mysql crash on linux 2.4.19-pre2. We use only m=
yisam
> tables.
>=20
> How-To-Repeat:
>=20

[skip]

> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x775cc5e0 is invalid pointer
> thd->thread_id=3D86646
>=20
> TIA
> --=20
> Martin Mokrejs ,
> PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
> MIPS / Institute for Bioinformatics
> GSF - National Research Center for Environment and Health
> Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
> tel.: +49-89-3187 3683 , fax:=A0+49-89-3187 3585
>=20

Hi!

The above stack trace does not look right.

And simply we can not deduce much from the above.

Do you know which command crashed MySQL ??

4.0.3 contains lot's of fixes for bugs that crash MySQL.

--=20
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic >
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12368@lists.mysql.com
To unsubscribe, e-mail

Re: mysql 4.0.2 linux-i386 crash

On Mon, 19 Aug 2002, Sinisa Milivojevic wrote:

> =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:
> > Hi,
> > I've a problem with mysql crash on linux 2.4.19-pre2. We use only myisam
> > tables.
> >
> > How-To-Repeat:
> >
>
> [skip]
>
> > Trying to get some variables.
> > Some pointers may be invalid and cause the dump to abort...
> > thd->query at 0x775cc5e0 is invalid pointer
> > thd->thread_id=86646
> >
> > TIA
> > --
> > Martin Mokrejs ,
> > PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
> > MIPS / Institute for Bioinformatics
> > GSF - National Research Center for Environment and Health
> > Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
> > tel.: +49-89-3187 3683 , fax: +49-89-3187 3585
> >
>
> Hi!
>
> The above stack trace does not look right.

Hmm, you are right. I forgot that my script to extract the stack trace
does not read itself the /usr/local/mysql/bin/mysqld.sym.gz.
BUT, when looking for it, I see:

-rwxr-xr-x 1 bioadmin bioadmin 20 Jul 1 14:52 mysqld.sym.gz

I've re-extracted the original archive

$ ls -la mysql-4.0.2-alpha-pc-linux-gnu-i686.tar.gz
-rw-r--r-- 1 root staff 11461681 Jul 16 15:59 mysql-4.0.2-alpha-pc-linux-gnu-i686.tar.gz
$

but I get again 20 bytes large file. Maybe you have somewhere the right
symbol table for official binaries. Here's the unresolved stack trace
again:

0x8071b58
0x825a668
0x825bc03
0x8258ce4
0x8256dc9
0x80cdd7b
0x80cd811
0x80cd334
0x807c9cd
0x807d955
0x8078ed3
0x807ece1
0x80780ae
0x8257c7c
0x828d3ba

>
> And simply we can not deduce much from the above.
>
> Do you know which command crashed MySQL ??

No clue.

>
> 4.0.3 contains lot's of fixes for bugs that crash MySQL.

Hmm, but do I have to use the Bitkeeper stuff to get it? Are there some
snapshots available? Sorry but the Downloads page doesn't say anything
about that (http://www.mysql.com/downloads/mysql-4.0.html).

TIA
--
Martin Mokrejs ,
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12369@lists.mysql.com
To unsubscribe, e-mail

Re: mysql 4.0.2 linux-i386 crash

On Mon, 19 Aug 2002, Jani Tolonen wrote:

> Hi,
>
> The stacktrace alone is not useful to us...
>
> =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:
> > Hi,
>
> > New value of fp=(nil) failed sanity check, terminating stack trace!
> > Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
> > stack trace is much more helpful in diagnosing the problem, so please do
> > resolve it
> > Trying to get some variables.
>
>
> Please follow the instructions from the URL above.

$ nm -n /usr/local/mysql-4.0.2-alpha-pc-linux-gnu-i686/bin/mysqld
nm: /usr/local/mysql-4.0.2-alpha-pc-linux-gnu-i686/bin/mysqld: no symbols
$

I use official binaries, I hope. ;)
--
Martin Mokrejs ,
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12370@lists.mysql.com
To unsubscribe, e-mail

Re: mysql 4.0.2 linux-i386 crash

=3D?iso-8859-2?Q?Martin_MOKREJ=3DA9?=3D writes:
> On Mon, 19 Aug 2002, Sinisa Milivojevic wrote:
>=20
> Hmm, you are right. I forgot that my script to extract the stack trac=
e
> does not read itself the /usr/local/mysql/bin/mysqld.sym.gz.
> BUT, when looking for it, I see:
>=20
> -rwxr-xr-x 1 bioadmin bioadmin 20 Jul 1 14:52 mysqld.sym.gz=

>=20
> I've re-extracted the original archive
>=20
> $ ls -la mysql-4.0.2-alpha-pc-linux-gnu-i686.tar.gz
> -rw-r--r-- 1 root staff 11461681 Jul 16 15:59 mysql-4.0.2-al=
pha-pc-linux-gnu-i686.tar.gz
> $
>=20

Can you check our binary tarball ??

>=20
> Hmm, but do I have to use the Bitkeeper stuff to get it? Are there so=
me
> snapshots available? Sorry but the Downloads page doesn't say anythin=
g
> about that (http://www.mysql.com/downloads/mysql-4.0.html).
>=20
> TIA
> --=20
> Martin Mokrejs ,
> PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
> MIPS / Institute for Bioinformatics
> GSF - National Research Center for Environment and Health
> Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
> tel.: +49-89-3187 3683 , fax:=A0+49-89-3187 3585
>=20


4.0.3 should be hopefully out this week.

--=20
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic >
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12371@lists.mysql.com
To unsubscribe, e-mail

Re: mysql 4.0.2 linux-i386 crash

On Mon, 19 Aug 2002, Sinisa Milivojevic wrote:

> =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:
> > On Mon, 19 Aug 2002, Sinisa Milivojevic wrote:
> >
> > Hmm, you are right. I forgot that my script to extract the stack trace
> > does not read itself the /usr/local/mysql/bin/mysqld.sym.gz.
> > BUT, when looking for it, I see:
> >
> > -rwxr-xr-x 1 bioadmin bioadmin 20 Jul 1 14:52 mysqld.sym.gz
> >
> > I've re-extracted the original archive
> >
> > $ ls -la mysql-4.0.2-alpha-pc-linux-gnu-i686.tar.gz
> > -rw-r--r-- 1 root staff 11461681 Jul 16 15:59 mysql-4.0.2-alpha-pc-linux-gnu-i686.tar.gz
> > $
> >
>
> Can you check our binary tarball ??

I've already downloaded another tar file from
http://mysql.tonnikala.org/Downloads/MySQL-4.0/mysql-4.0.2-a lpha-pc-linux-gnu-i686.tar.gz
but same sontents - i.e. "20 Jul 1 14:52 mysqld.sym.gz". Same with PliGUK
source from England. Should I try more?

ftp://ftp.mysql.com refuses connections, ftp://support.mysql.com doesn't
show /pub/ at all. It seems I don't know how to download from primary
site. :(

> 4.0.3 should be hopefully out this week.

Good. I hope I won;'t have to make symlinks to make mysqld happy finding
the share subdir, as posted I posted
http://lists.mysql.com/cgi-ez/ezmlm-cgi?1:mss:116853:200208: dbomplnneemmcgegiepn
although I've received no response so far and no lines in Changelog refer
to it. ;)
--
Martin Mokrejs ,
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12372@lists.mysql.com
To unsubscribe, e-mail

mysql 4.0.2 linux-i386 crash

Hi!

>>>>> "Martin" == Martin MOKREJ writes:

Martin> Hi,
Martin> I've a problem with mysql crash on linux 2.4.19-pre2. We use only myisam
Martin> tables.

Martin> How-To-Repeat:



Martin> 0x8071b58 reset_fields__10Field_blob + 8
Martin> 0x825a668 __evoke_link_warning_llseek + 182600
Martin> 0x825bc03 __evoke_link_warning_llseek + 188131
Martin> 0x8258ce4 __evoke_link_warning_llseek + 176068
Martin> 0x8256dc9 __evoke_link_warning_llseek + 168105
Martin> 0x80cdd7b mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13s t_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10A lter_dr + 7491
Martin> 0x80cd811 mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13s t_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10A lter_dr + 6105
Martin> 0x80cd334 mysql_alter_table__FP3THDPcT1P24st_ha_create_informationP13s t_table_listRt4List1Z12create_fieldRt4List1Z3KeyRt4List1Z10A lter_dr + 4860
Martin> 0x807c9cd create_new_thread__FP3THD + 261
Martin> 0x807d955 get_options__FiPPc + 1861
Martin> 0x8078ed3 my_lock + 307
Martin> 0x807ece1 kill_server_thread__FPv + 49
Martin> 0x80780ae send_warning__FP6st_netUiPCc + 50
Martin> 0x8257c7c __evoke_link_warning_llseek + 171868
Martin> 0x828d3ba __evoke_link_warning_llseek + 390810

The above looks like a logical error in ALTER TABLE.

Can you find out what query you used and if you can repeat the problem
by re-issuing the query ?

If yes, then by giving us access to the CREATE TABLE to your original
table and the ALTER TABLE statement, we should be able to repeat this.

Regards,
Monty

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12379@lists.mysql.com
To unsubscribe, e-mail

Re: mysql 4.0.2 linux-i386 crash

Hi!

>>>>> "Martin" == Martin MOKREJ writes:



>> Can you check our binary tarball ??

Martin> I've already downloaded another tar file from
Martin> http://mysql.tonnikala.org/Downloads/MySQL-4.0/mysql-4.0.2-a lpha-pc-linux-gnu-i686.tar.gz
Martin> but same sontents - i.e. "20 Jul 1 14:52 mysqld.sym.gz". Same with PliGUK
Martin> source from England. Should I try more?

No, it looks like something went wrong when we made the 4.0.2
distribution. I am just now building 4.0.3 and I will check that the
sym file will get generated properly this time. Sorry for the
confusion.

Martin> ftp://ftp.mysql.com refuses connections, ftp://support.mysql.com doesn't
Martin> show /pub/ at all. It seems I don't know how to download from primary
Martin> site. :(

>> 4.0.3 should be hopefully out this week.

Martin> Good. I hope I won;'t have to make symlinks to make mysqld happy finding
Martin> the share subdir, as posted I posted
Martin> http://lists.mysql.com/cgi-ez/ezmlm-cgi?1:mss:116853:200208: dbomplnneemmcgegiepn
Martin> although I've received no response so far and no lines in Changelog refer
Martin> to it. ;)

I checked your original email, but could not from this see where the
problem could be as you did not provide us with all information we
need to locate the problem.

My guess is that your original problem is that you added
/usr/local/mysql/bin to PATH, which is wrong.

The right way is to not do ANY changes in mysql.server but instead set
in /etc/my.cnf set the lines:

[mysqld]
basedir=path-to-mysql-installation

I did some testing regarding this and noticed that if you do 'make
install' then things works nicely but if you install mysql.server from
the MySQL binary distribution, then things are not working
'perfectly'.

I have now fixed this and updated the comments in the mysql.server
script. This will be be in 4.0.3.

Regards,
Monty

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12396@lists.mysql.com
To unsubscribe, e-mail

Configuring my.cnf (was: mysql 4.0.2 linux-i386 crash)

On Fri, 23 Aug 2002, Michael Widenius wrote:

Hi,

> No, it looks like something went wrong when we made the 4.0.2
> distribution. I am just now building 4.0.3 and I will check that the
> sym file will get generated properly this time. Sorry for the
> confusion.
>

No problem. Do you have the unstripped binaries for 4.0.2? Can you decode
the stack trace?

> My guess is that your original problem is that you added
> /usr/local/mysql/bin to PATH, which is wrong.

Well, this was one of the attempts, as it seemed mysqld did chdir() to
some wrong directory, and wasn't able to locate my_print_defaults and
other binaries. The PATH solved this part of the problem, but the problem
with share/mysql/ not being found remained. It turned out the soflink from
withing /usr/local/mysql to itself under
mysql-4.0.2-alpha-pc-linux-gnu-i686 solved that.

Currently, mysqld --help reports:
basedir /usr/local/mysql
bind-address 0
chroot (No default value)
character-sets-dir mysql-4.0.2-alpha-pc-linux-gnu-i686/share/mysql/charsets/
datadir /data/mysql
default-character-set latin1
default-table-type (No default value)


>
> The right way is to not do ANY changes in mysql.server but instead set
> in /etc/my.cnf set the lines:
>
> [mysqld]
> basedir=path-to-mysql-installation
>
> I did some testing regarding this and noticed that if you do 'make
> install' then things works nicely but if you install mysql.server from
> the MySQL binary distribution, then things are not working
> 'perfectly'.

Hmm, yes, there's somewhere @HOSTNAME@ which I thought should be already
expanded via some make command. But I only untar the distribution and
that's almost all I do after upgrade.


I have sometimes problems configuring /etc/my.cnf. I'm getting errors that
some variable is not recognized. I'm not sure if it has to be critical
error so that mysqld exits immediately, but that's your choice. For
example, when it cannot create .pid file, it gives error 02 but continues.
I'm very bad with understanding doc's I think, but while looking at
http://www.mysql.com/doc/en/SHOW_VARIABLES.html, it only says:
"have_innodb YES if mysqld supports InnoDB tables. DISABLED if
--skip-innodb is used. " Beginner doesn't come to the conclusion he's
supposed to use
[mysqld]
skip-innodb

Actually, originally I tried have_innodb=0 (or set have_innodb=0 ?) with
not much success either. I thought that all --cmd arguments to mysqld can
be specified in the [mysqld] section. skip-locking works for me under
[mysqld]. But these details are not in the doc's, probably they seem to
you clear enough. :(

Just have a look at http://www.mysql.com/doc/en/Option_files.html. Reading
that tells me, that skip-innodb is an ARGUMENT, not an OPTION/VARIABLE, so
I should not try
set skip-innodb

but I could try
set have_innodb=0
what gave me unfortunately
/usr/local/mysql/bin/mysqld: ERROR: unknown variable 'have_innodb=0'

trying
set have_innodb=OFF
gives
/usr/local/mysql/bin/mysqld: ERROR: unknown variable 'have_innodb=OFF'

Obviously,
skip-innodb
works. ;)

However, the connection between have_innodb and skip-innodb is only
through the documentation. It seems to me have_innodb is there just for
confusion and to say, that InnoDB is currenly disabled or not compiled
into at all. :) Well, it's just folling me, othwerwise no problem.


Second real example:
While playing with those setting in /etc/my.cnf, I see when there's any
kind of error, mysqld is started but exits because of wrong config lines
in my.cnf. BUT, why does it create $hostname.err file not as usually in
our case under basedir/log/ but under datadir/?

I have in my.cnf:
[mysqld_safe]
set-variable = err_log=/usr/local/mysql/log/$host.err
set-variable = pid_file=/usr/local/mysql/var/run/$host.pid

but it's somehow ignored. I had to modify mysqld_safe (see below).

This doesn't allow mysqld to start at all:
[mysqld]
err_log = /usr/local/mysql/log/jerboas.err
pid_file = /usr/local/mysql/var/run/jerboas.pid

with message:
/usr/local/mysql/bin/mysqld: ERROR: unknown variable 'err_log=/usr/local/mysql/log/jerboas.err'


To make things more complicated, "mysqld --help" doesn't work if there's a
syntax error in /etc/my.cnf. :(

Hmm, after commenting out #err_log the help works, but no variables or
options seem to refer to the errorlog file. Well,
log = /usr/local/mysql/log/jerboas.err
turned on the logging of SQL commands, what I did not want. :(
*So how can one relocate the .err file?*

http://www.mysql.com/doc/en/Error_log.html is again sparse on information.
The Comments on that page seem to be related to completely different
chapter than 4.9.1!

How do I relocate .err file currently (shown grep output)?
/usr/local/mysql/bin/safe_mysqld:err_log=$MY_BASEDIR_VERSION /log/`/bin/hostname`.err
/usr/local/mysql/bin/safe_mysqld: $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking >> $err_log 2>&1
/usr/local/mysql/bin/safe_mysqld: eval "$NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking $args >> $err_log 2>&1"


>
> I have now fixed this and updated the comments in the mysql.server
> script. This will be be in 4.0.3.

For me would be the best if there would be mentioned variables/options,
using which I could modify the settings in my.cnf. ;) What the user might
want to change? Only few, believe me. ;) datadir, basedir, error log and
pid file locations.

TIA
--
Martin Mokrejs ,
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12398@lists.mysql.com
To unsubscribe, e-mail

Re: Configuring my.cnf (was: mysql 4.0.2 linux-i386 crash)

On Friday 23 August 2002 11:07, Martin MOKREJÅ  wrote:

> Hmm, yes, there's somewhere @HOSTNAME@ which I thought should be alread=
y
> expanded via some make command. But I only untar the distribution and
> that's almost all I do after upgrade.

That would be the 'hostname' command, which isn't available on all platfo=
rms=20
or available in the PATH of a normal user. Additionally - this also appli=
es=20
to safe_mysqld and other scripts.

I have a different hostname installed in my shell, from the sh-utils, tha=
n the=20
OS supplied. Problem is, that in the chrooted environment my homedir does=
n't=20
exist, so I have to rewrite those (even if I changed my PATH, /usr/bin=20
doesn't exist in the chrooted env either).

Would be nice to have some --with-pub-executables option, to set the dirn=
ame=20
of those binaries (tee, rmdir, hostname etc.).

But - this is of 'minor irritataion level' - once you know :-)
--=20
Best regards,

IDG.nl
Melvyn Sopacua
WebMaster

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12400@lists.mysql.com
To unsubscribe, e-mail

Configuring my.cnf (was: mysql 4.0.2 linux-i386 crash)

Hi!

>>>>> "Martin" == Martin MOKREJ writes:

Martin> On Fri, 23 Aug 2002, Michael Widenius wrote:
Martin> Hi,

>> No, it looks like something went wrong when we made the 4.0.2
>> distribution. I am just now building 4.0.3 and I will check that the
>> sym file will get generated properly this time. Sorry for the
>> confusion.
>>

Martin> No problem. Do you have the unstripped binaries for 4.0.2? Can you decode
Martin> the stack trace?

Sorry, but we don't have that :(

>> My guess is that your original problem is that you added
>> /usr/local/mysql/bin to PATH, which is wrong.

Martin> Well, this was one of the attempts, as it seemed mysqld did chdir() to
Martin> some wrong directory, and wasn't able to locate my_print_defaults and
Martin> other binaries. The PATH solved this part of the problem, but the problem
Martin> with share/mysql/ not being found remained. It turned out the soflink from
Martin> withing /usr/local/mysql to itself under
Martin> mysql-4.0.2-alpha-pc-linux-gnu-i686 solved that.

Yes, this softlink is the recommended way to install a MySQL binary
distribution as it makes it trivial to change MySQL version almost instantly.



Martin> Hmm, yes, there's somewhere @HOSTNAME@ which I thought should be already
Martin> expanded via some make command. But I only untar the distribution and
Martin> that's almost all I do after upgrade.

I noticed the HOSTNAME issue and this is fixed in the 4.0.3 binary
version that I am building just now...

Martin> I have sometimes problems configuring /etc/my.cnf. I'm getting errors that
Martin> some variable is not recognized. I'm not sure if it has to be critical
Martin> error so that mysqld exits immediately, but that's your choice. For
Martin> example, when it cannot create .pid file, it gives error 02 but continues.

In most cases MySQL exits at once, which I think is the right thing as
the option you may have misspelled could be critical for your
operation.

When it comes to the pid file, MySQL works perfectly even without it
and that's we decided to ignore the error in this case.


Martin> I'm very bad with understanding doc's I think, but while looking at
Martin> http://www.mysql.com/doc/en/SHOW_VARIABLES.html, it only says:
Martin> "have_innodb YES if mysqld supports InnoDB tables. DISABLED if
Martin> --skip-innodb is used. " Beginner doesn't come to the conclusion he's
Martin> supposed to use
Martin> [mysqld]
Martin> skip-innodb

We can't repeat all manual information at all places some construct is
used :(

From the manual:

If you don't want to use InnoDB tables, add the skip-innodb option to
the option file.

I have now added some more references to --skip-innodb

Martin> Actually, originally I tried have_innodb=0 (or set have_innodb=0 ?) with
Martin> not much success either. I thought that all --cmd arguments to mysqld can
Martin> be specified in the [mysqld] section. skip-locking works for me under
Martin> [mysqld]. But these details are not in the doc's, probably they seem to
Martin> you clear enough. :(

Yes, all options can be specified in the [mysqld] section. The
problem here is that 'have_innodb' is not an option but a status
variable that gives you the state of innodb.

Martin> Just have a look at http://www.mysql.com/doc/en/Option_files.html. Reading
Martin> that tells me, that skip-innodb is an ARGUMENT, not an
Marten> OPTION/VARIABLE.

That is correct. Note that the idea with option files is to specify
ARGUMENTS for MySQL.

have_innodb is not an variable that can be set but a status indication.



Martin> Second real example:
Martin> While playing with those setting in /etc/my.cnf, I see when there's any
Martin> kind of error, mysqld is started but exits because of wrong config lines
Martin> in my.cnf. BUT, why does it create $hostname.err file not as usually in
Martin> our case under basedir/log/ but under datadir/?

A small note about this; the err file is created by mysqld_safe as
follows:

mysqld > error-file-name

Martin> I have in my.cnf:
Martin> [mysqld_safe]
Martin> set-variable = err_log=/usr/local/mysql/log/$host.err
Martin> set-variable = pid_file=/usr/local/mysql/var/run/$host.pid

This is becasue you should not use set-variable with mysqld_safe but
just:

[mysqld_safe]
err_log=/usr/local/mysql/log/$host.err
pid_file=/usr/local/mysql/var/run/$host.pid

In MySQL 4.0.3 everything is easier as you never have to use
'set-variable' anymore.

Martin> but it's somehow ignored. I had to modify mysqld_safe (see below).

Martin> This doesn't allow mysqld to start at all:
Martin> [mysqld]
Martin> err_log = /usr/local/mysql/log/jerboas.err
Martin> pid_file = /usr/local/mysql/var/run/jerboas.pid

The above doesn't work as mysqld doesn't understand the err_log
option. This is an option for the mysqld_safe script, not for mysqld.



Martin> To make things more complicated, "mysqld --help" doesn't work if there's a
Martin> syntax error in /etc/my.cnf. :(

Just specify '--no-defaults' as the first option to mysqld:

mysqld --no-defaults --help

always works...

>> I have now fixed this and updated the comments in the mysql.server
>> script. This will be be in 4.0.3.

Martin> For me would be the best if there would be mentioned variables/options,
Martin> using which I could modify the settings in my.cnf. ;) What the user might
Martin> want to change? Only few, believe me. ;) datadir, basedir, error log and
Martin> pid file locations.

In the option files you can set all options and variables that 'mysqld --help'
prints.

Regards,
Monty
CTO of MySQL AB

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12402@lists.mysql.com
To unsubscribe, e-mail

Re: Configuring my.cnf (was: mysql 4.0.2 linux-i386 crash)

Hi!

>>>>> "Melvyn" == Melvyn Sopacua writes:

Melvyn> On Friday 23 August 2002 11:07, Martin MOKREJÅ  wrote:
>> Hmm, yes, there's somewhere @HOSTNAME@ which I thought should be alr=
eady
>> expanded via some make command. But I only untar the distribution an=
d
>> that's almost all I do after upgrade.

Melvyn> That would be the 'hostname' command, which isn't available on =
all platforms=20
Melvyn> or available in the PATH of a normal user. Additionally - this =
also applies=20
Melvyn> to safe_mysqld and other scripts.

This has probably nothing to do with this special case.
The mysql_bin_log script that fixes up mysql.server script did not
even try to replace the @HOSTNAME@; This was a bug in the script.

Melvyn> I have a different hostname installed in my shell, from the sh-=
utils, than the=20
Melvyn> OS supplied. Problem is, that in the chrooted environment my ho=
medir doesn't=20
Melvyn> exist, so I have to rewrite those (even if I changed my PATH, /=
usr/bin=20
Melvyn> doesn't exist in the chrooted env either).

It's almost impossible for a general usable script to handle things
like this. If you are not using a default installation, I think it's
not unreasonable for us to require you to take the consequences of
this.

Melvyn> Would be nice to have some --with-pub-executables option, to se=
t the dirname=20
Melvyn> of those binaries (tee, rmdir, hostname etc.).

You can always submit us a patch for this...

Regards,
Monty

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12405@lists.mysql.com
To unsubscribe, e-mail

Re: Configuring my.cnf (was: mysql 4.0.2 linux-i386 crash)

Hi,


On Sunday 25 August 2002 20:01, Michael Widenius wrote:

[...]

> Melvyn> I have a different hostname installed in my shell, from the
> sh-utils, than the Melvyn> OS supplied. Problem is, that in the chroote=
d
> environment my homedir doesn't Melvyn> exist, so I have to rewrite thos=
e
> (even if I changed my PATH, /usr/bin Melvyn> doesn't exist in the chroo=
ted
> env either).
>
> It's almost impossible for a general usable script to handle things
> like this. If you are not using a default installation, I think it's
> not unreasonable for us to require you to take the consequences of
> this.

I understand that, but mysqld has a chroot option and can be run chrooted=
, so=20
why the hardcoded paths in a startupscript? I don't see the need for the=20
performance increase, by calling the binary without path.
Is there any other reason?
Otherwise the patch would be substituting AC_PATH_PROG with AC_CHECK_PROG=
=20
macro's.

> Melvyn> Would be nice to have some --with-pub-executables option, to se=
t
> the dirname Melvyn> of those binaries (tee, rmdir, hostname etc.).
>
> You can always submit us a patch for this...

If a path is needed, I will work this out.

--=20
Best regards,

IDG.nl
Melvyn Sopacua
WebMaster

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12418@lists.mysql.com
To unsubscribe, e-mail