hi stella, i'm adding the bug address back to the CC list for the email, so we have all of this for posterity. also this way if christian or anyone else notices something they can chime in.
On Tue, May 30, 2006 at 01:53:38PM +0100, Stella Power wrote:
> > - could you tell us more about what software you have interacting with
> > mysql?
> I have some php scripts that read from and write to a database. These haven't
> been changed recently and were working fine before mysql was upgraded.
okay. i'm curious not because i think the software is at fault, but i'm
trying to determine if the software is triggering the problem. there
are, for exmaple, two different versions of mysql in sarge, and
some software is compiled against one version of the client library while some
software is compiled against the other.
could you give the output of
dpkg -l 'php*' | grep ^ii
and find the mysql.so file provided by your php library (probably
somewhere like /usr/lib/phpFOO/BAR/mysql.so, and then run
ldd /usr/lib/phpFOO/BAR/mysql.so | grep mysql
> > - it would be helpful to have the actual mysqld cmdline being called
> > (you can figure this out by placing a "set -x" minus the quotes at
> > the top of /usr/bin/mysqld_safe and looking for the call to mysqld).
> That adds the following line to the top of the syslog messages I sent you
> before:
> May 30 13:28:23 /etc/init.d/mysql[21552]:
i should have been more clear. what i meant was put a set -x near the
top of /usr/bin/mysqld_safe, and then run it as root. you should get
something like:
<snip>
+ test -z '--port=3306 --socket=/var/run/mysqld/mysqld.sock '
+ eval 'nohup /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql
--user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking --port=3306
--socket=/var/run/mysqld/mysqld.sock 2>&1 | logger -p daemon.err -t
mysqld_safe -i -t mysqld'
++ nohup /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql
--pid-file=/var/run/mysqld/mysqld.pid --skip-locking --port=3306
--socket=/var/run/mysqld/mysqld.sock
towards the end. this is the actual mysql command line being executed,
which is what i want to see.
> > - having the output of ltrace on the above mysqld cmdline would be
> > helpful.
> I've never used ltrace before. I tried the following command but it didn't
> work. Not sure what it is I'm doing wrong.
> /> /usr/bin/ltrace -o ltrace.out /usr/bin/mysqld_safe
> /usr/bin/ltrace: Can't open ELF file "/usr/bin/mysqld_safe"
yes, because mysqld_safe is a wrapper script around the real command
line. once you find the above command line, try passing the whole
line as arguments to ltrace (minus the "++ nohup").
sean
--
signature.asc
Description: Digital signature
