Bug#688792: syntax error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 23/10/12 06:50, Noah Meyerhans wrote: Ok, good news, and an apology. The good news is that this isn't mysql's fault at all. The network-manager package is breaking /etc/network/interfaces, causing the lo interface to not get an IP address. The SQL syntax error was a red herring, and is not actually related to the server not starting. I'll drop the severity of this bug back to normal. Apologies for cluttering it with a bunch of unrelated stuff. The n-m bug is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688355, fwiw. Thanks noah Noah, Thanks. It's nice to have a respite from the unrelenting sinking feeling. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQhkUAAAoJELbE2bY7/+c8E2oP/RxYDneIeUsyxmy/PZ5D+UGN zUsSg7QgqyAD5k7KMMlh6ENiCdb6WTDErMnADB7L4lILS8kNJ7aIRpswij6aMcsF UiFbSsw05lUspEJxNMDQ7H/BdCMGch5G37LnvJWOl7gQvm1HrFaR/SNh1wM1jB8X cgreY/3q1cL+QWuxo0b3rB84D13jop60U5As3pafOB+0oFgkrFEo8JuuRh/sO74R 0SzrYT1f0pxZiHpY0yaAawN83r7Mng9umHyNYK2/SuvDWt6x9TWHKm2DD6CG/o7c y96n4rNc2yUbTFbrPco8tmVQbGJ1MtCJzcLc/E6rj7QFWPdpOp5Yn1EvgnhxVj8F V0C6I+lyOZXB1q8hz7VZyhxkfeZ1UAhLreF/NgHJVzkyuBnHYNcBb4Gir2DXYX+n e0h/TRwaP8fXQCCuhyN3MitC26Gu8MyGPSafr9Tug3VvvWPz3717e2c/SELysWes TQNkNruokIcFBunlyfvVZTsevFboYoSRUygQhYXtJASBCznfW3NA65kyc67f6CME krjETkBzHz1u3+gQ81Ll7UD8W8mdnhuQy0xrDHPyqB1vAQS7v6NioIuCRLnjKxM4 POG8fnBrkUW/GIYDQMqucC1nkn+WqBI/pZCOjZcQ/meGarzC/HAINaAtPlivbbOJ LaiHohjNakIzxPV8pBNB =rQo6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
Hi. I've just experienced this problem on a fresh wheezy install using
the beta3 installer. The installation was performed using the netboot
image (that is, PXE and downloading the installer components from a TFTP
server) on a physical, non-virtual host.
I haven't put in a lot of time to investigate, but one thing I have
observed is that if I try to install mysql-server-5.5 on a freshly
installed system that has the 'desktop' task installed, the installation
fails. However, if I build a similar system but leave off the 'desktop'
task, the mysql installation is successful. Obviously there are a lot of
packages involved in the desktop task, so I'm not sure how much this
help to narrow things down. It definitely appears repeatable, however.
Since this problem does impact the ability to install the mysql server
packages on a common system configuration, I think a severity of at
least 'important' is warranted. Honestly I think 'grave' would be
appropriate, as I don't think it'd be reasonable to release wheezy with
this bug in place.
Relevant section of the log file:
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 [Note] Plugin
'FEDERATED' is disabled.
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: The InnoDB
memory heap is disabled
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: Mutexes and
rw_locks use GCC atomic builtins
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: Compressed
tables use zlib 1.2.7
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: Using Linux
native AIO
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: Initializing
buffer pool, size = 128.0M
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: Completed
initialization of buffer pool
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: highest
supported file format is Barracuda.
Oct 21 23:11:07 dhcp204 mysqld_safe[4610]: 121021 23:11:07 InnoDB: Waiting for
the background threads to start
Oct 21 23:11:08 dhcp204 mysqld_safe[4610]: 121021 23:11:08 InnoDB: 1.1.8
started; log sequence number 1595675
Oct 21 23:11:08 dhcp204 mysqld_safe[4610]: ERROR: 1064 You have an error in
your SQL syntax; check the manual that corresponds to your MySQL server version
for the right syntax to use near 'ALTER TABLE user ADD column Show_view_priv
enum('N','Y') CHARACTER SET utf8 NOT ' at line 1
Oct 21 23:11:08 dhcp204 mysqld_safe[4610]: 121021 23:11:08 [ERROR] Aborting
Oct 21 23:11:08 dhcp204 mysqld_safe[4610]:
Oct 21 23:11:08 dhcp204 mysqld_safe[4610]: 121021 23:11:08 InnoDB: Starting
shutdown...
Oct 21 23:11:09 dhcp204 mysqld_safe[4610]: 121021 23:11:09 InnoDB: Shutdown
completed; log sequence number 1595675
Oct 21 23:11:09 dhcp204 mysqld_safe[4610]: 121021 23:11:09 [Note]
/usr/sbin/mysqld: Shutdown complete
Oct 21 23:11:09 dhcp204 mysqld_safe[4610]:
signature.asc
Description: Digital signature
Bug#688792: syntax error
On Sun, 2012-10-21 at 23:28 -0700, Noah Meyerhans wrote: Hi. I've just experienced this problem on a fresh wheezy install using the beta3 installer. The installation was performed using the netboot image (that is, PXE and downloading the installer components from a TFTP server) on a physical, non-virtual host. I haven't put in a lot of time to investigate, but one thing I have observed is that if I try to install mysql-server-5.5 on a freshly installed system that has the 'desktop' task installed, the installation fails. However, if I build a similar system but leave off the 'desktop' task, the mysql installation is successful. Obviously there are a lot of packages involved in the desktop task, so I'm not sure how much this help to narrow things down. It definitely appears repeatable, however. Since this problem does impact the ability to install the mysql server packages on a common system configuration, I think a severity of at least 'important' is warranted. Honestly I think 'grave' would be appropriate, as I don't think it'd be reasonable to release wheezy with this bug in place. That sounds more serious than what I experienced, which was that there was an error in the log but mysql 5.5 at least appears to be functioning properly. I did an upgrade, not a fresh install, and it was in a minimalist chroot. It's possible that whatever the offending package is was not on my chroot system. Ross -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
The desktop tasks install various mysql related packages (libmysqlclient18, mysql-server-core-5.5, etc). I've been trying to test installations on a base system (no desktop task) to see if one of these packages, when installed before the 'mysql-server' package, breaks installation of mysql-server. Haven't found anything yet, though... signature.asc Description: Digital signature
Bug#688792: syntax error
On Mon, 2012-10-22 at 11:19 -0700, Noah Meyerhans wrote: The desktop tasks install various mysql related packages (libmysqlclient18, mysql-server-core-5.5, etc). I've been trying to test installations on a base system (no desktop task) to see if one of these packages, when installed before the 'mysql-server' package, breaks installation of mysql-server. Haven't found anything yet, though... Wow! Thanks for doing that; it's a big job. Certainly mysql not working if desktop tasks are installed is a big deal. Ross -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
Ok, good news, and an apology. The good news is that this isn't mysql's fault at all. The network-manager package is breaking /etc/network/interfaces, causing the lo interface to not get an IP address. The SQL syntax error was a red herring, and is not actually related to the server not starting. I'll drop the severity of this bug back to normal. Apologies for cluttering it with a bunch of unrelated stuff. The n-m bug is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688355, fwiw. Thanks noah signature.asc Description: Digital signature
Bug#688792: syntax error
On Wed, 2012-09-26 at 21:51 +0100, Nicholas Bamber wrote: Ross, Actually would it be possible for you to send the output of use mysql; show create table user; for both the external and chrooted databases? Here it is for the chroot: +---++ | Table | Create Table |
Bug#688792: syntax error
tag 688792 +moreinfo thanks Ross, Thanks for the report. First of all whenever I play with mysql inside a chroot I have to bring down the real mysql server as otherwise there is a port clash. (I'm not sure how piuparts avoids this issue.) And that certainly causes upgrade failures. That said I have not yet managaed to get the postinst script to run that SQL. Given that the code is there that should just be a matter of me studying precisely what is needed to trigger it. Also I am fairly sure that all the maintenance scripts need a thorough review but I am trying quite hard to not make any non-essential changes until the freeze is over. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
On Wed, 2012-09-26 at 12:07 +0100, Nicholas Bamber wrote: tag 688792 +moreinfo thanks I'm not sure what more info you want. The host mysql was shut down when I ran the install; in fact, I've disabled the host start up script mysql, although I haven't touch mysql-ndb and mysql-ndb-mgm (I don't know what they do). Do you have any idea what the significance is of the SQL code that didn't run? Ross Ross, Thanks for the report. First of all whenever I play with mysql inside a chroot I have to bring down the real mysql server as otherwise there is a port clash. (I'm not sure how piuparts avoids this issue.) And that certainly causes upgrade failures. That said I have not yet managaed to get the postinst script to run that SQL. Given that the code is there that should just be a matter of me studying precisely what is needed to trigger it. Also I am fairly sure that all the maintenance scripts need a thorough review but I am trying quite hard to not make any non-essential changes until the freeze is over. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
On 26/09/12 17:20, Ross Boylan wrote: On Wed, 2012-09-26 at 12:07 +0100, Nicholas Bamber wrote: tag 688792 +moreinfo thanks I'm not sure what more info you want. Well the information you have sent is useful in its own right, but I have not really got a good idea of all the details. The ideal would be if you can document how to go from a machine (perferably without an external myslq instance - but with one if that is part of the issue), through the building of chroot and so on. But that is the ideal and see below. The host mysql was shut down when I ran the install; in fact, I've disabled the host start up script mysql, although I haven't touch mysql-ndb and mysql-ndb-mgm (I don't know what they do). This is ringing alarm bells. These are part of MySQL cluster and are no longer part of the core MySQL product. It may be just that your external MySQL is just very old. Do you have any idea what the significance is of the SQL code that didn't run? THey are trying to upgrade the privilege tables from an old format. Probably the SQL should be removed but I need to check that. Ross Ross, Thanks for the report. First of all whenever I play with mysql inside a chroot I have to bring down the real mysql server as otherwise there is a port clash. (I'm not sure how piuparts avoids this issue.) And that certainly causes upgrade failures. That said I have not yet managaed to get the postinst script to run that SQL. Given that the code is there that should just be a matter of me studying precisely what is needed to trigger it. Also I am fairly sure that all the maintenance scripts need a thorough review but I am trying quite hard to not make any non-essential changes until the freeze is over. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
On Wed, 2012-09-26 at 12:07 +0100, Nicholas Bamber wrote: That said I have not yet managaed to get the postinst script to run that SQL. Given that the code is there that should just be a matter of me studying precisely what is needed to trigger it. The error is not new with the latest upgrade. I see it for [UPGRADE] mysql-server-5.5:i386 5.5.24+dfsg-6 - 5.5.24+dfsg-7 on Sep 4. I see it at least as far back as March 9, 2012, which was [UPGRADE] mysql-server-5.1 5.1.58-1 - 5.1.61-2 Note I had 5.1 installed before upgrading to 5.5. Ross -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688792: syntax error
On 26/09/12 20:27, Ross Boylan wrote: On Wed, 2012-09-26 at 12:07 +0100, Nicholas Bamber wrote: That said I have not yet managaed to get the postinst script to run that SQL. Given that the code is there that should just be a matter of me studying precisely what is needed to trigger it. The error is not new with the latest upgrade. I see it for [UPGRADE] mysql-server-5.5:i386 5.5.24+dfsg-6 - 5.5.24+dfsg-7 on Sep 4. I see it at least as far back as March 9, 2012, which was [UPGRADE] mysql-server-5.1 5.1.58-1 - 5.1.61-2 Note I had 5.1 installed before upgrading to 5.5. Ross Ross, Actually would it be possible for you to send the output of use mysql; show create table user; for both the external and chrooted databases? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
