Bug#296403: Bug#297198: does not restart after upgrade

2005-03-01 Thread Christian Hammers
Hello Sean On 2005-03-01 sean finney wrote: > what i was getting at was that i don't think storing temporary > "server is running" or "server should start" type files in > /etc/mysql is really in the spirit of the fhs. As long as the temporary file does not stay longer as an upgrade I think the FH

Bug#296403: Bug#297198: does not restart after upgrade

2005-03-01 Thread sean finney
hey christian, On Wed, Mar 02, 2005 at 01:04:34AM +0100, Christian Hammers wrote: > > this seems kind of dodgy, and somewhat stretching what the fhs > > should allow... > > Why do you think? The FHS governs mainly the locations of files as far as > I know and even our Debian policy does not manda

Bug#296403: Bug#297198: does not restart after upgrade

2005-03-01 Thread Christian Hammers
Hello Sean On 2005-03-01 sean finney wrote: > On Wed, Mar 02, 2005 at 12:24:28AM +0100, Christian Hammers wrote: > > No, it's mainly created by the last version's prerm script if > > "/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping" > > gives some output which is "mysqld alive

Bug#296403: Bug#297198: does not restart after upgrade

2005-03-01 Thread sean finney
On Wed, Mar 02, 2005 at 12:24:28AM +0100, Christian Hammers wrote: > No, it's mainly created by the last version's prerm script if > "/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping" > gives some output which is "mysqld alive" if the server is currently > running. this seems k

Bug#296403: Bug#297198: does not restart after upgrade

2005-03-01 Thread Christian Hammers
tags 296403 + needhelp moreinfo unreproducible thanks Hello Sadly, I'm still not able to reproduce the bug :-( On 2005-02-28 sean finney wrote: > On Sun, Feb 27, 2005 at 08:31:27PM -0500, Joe Drew wrote: > > + '[' -f /etc/mysql/dpkg__mysql_should_be_started ']' > > + exit 0 > > so that file was

Bug#296403: Bug#297198: does not restart after upgrade

2005-02-27 Thread sean finney
hi guys, i looked a little more into this... On Sun, Feb 27, 2005 at 08:31:27PM -0500, Joe Drew wrote: > + '[' -f /etc/mysql/dpkg__mysql_should_be_started ']' > + exit 0 so that file wasn't there because it's only created by the preinst script during fresh installs. christian: i looked throu

Bug#297198: does not restart after upgrade

2005-02-27 Thread Joe Drew
sean finney wrote: could you throw a "set -x" in the top of the postinst script and send us the output? Sure can! [EMAIL PROTECTED]:~# /var/lib/dpkg/info/mysql-server-4.1.postinst configure + export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/sbin:/usr/sbin:/bin

Bug#297198: does not restart after upgrade

2005-02-27 Thread Christian Hammers
Hello Sean On 2005-02-27 sean finney wrote: > could you throw a "set -x" in the top of the postinst script and > send us the output? BTW: I put a special variable in all of my scripts so that you can you get "set -x" and "set -v" after export DEBIAN_SCRIPT_DEBUG=1 BTW2: I'm currently fo

Bug#297198: does not restart after upgrade

2005-02-27 Thread sean finney
hi joe, could you throw a "set -x" in the top of the postinst script and send us the output? sean -- signature.asc Description: Digital signature

Bug#297198: does not restart after upgrade

2005-02-27 Thread Joe Drew
Package: mysql-server-4.1 Severity: serious It looks as though the postinst is trying to stop mysql instead of starting it. I had a working mysql installation previous to this, and I haven't seen this problem before. Relevant portions of the upgrade log are below. Preparing to replace mysql-serv