Bug#545751: [debian-mysql] Bug#545751: Still doesn't work for me

2010-02-12 Thread Norbert Tretkowski
Am Freitag, den 12.02.2010, 18:20 +0100 schrieb Marcin Trybus:
 Feb 12 18:02:05 localhost mysqld: 100212 18:02:05 [ERROR] Can't start server: 
 Bind on TCP/IP port: Cannot assign requested address
 Feb 12 18:02:05 localhost mysqld: 100212 18:02:05 [ERROR] Do you already have 
 another mysqld server running on port: 3306 ?

This is the only real problem I see in your log... there seem so be a
service listening on port 3306 already.

Norbert




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#545751: [debian-mysql] Bug#545751

2009-10-20 Thread Marcin Trybus
I'd like to confirm that this also happens with a clean install of pure squeeze 
(only iceweasel taken from experimental). I tried both mysql-server from 
squeeze (5.1.37-2) and sid (5.1.39-1). 

I have no knowledge on how this all works, I only need it as a kmail dependency 
(which is quite silly BTW). I didn't sent an upstream bug. Since it's a syntax 
error the bug is most likely linked to the package itself. 


mar...@localhost:~$ sudo cat /var/log/syslog | grep mysql

Oct 21 01:38:13 localhost mysqld_safe[6640]: 091021  1:38:13 [Warning] Forcing 
shutdown of 2 plugins
Oct 21 01:38:13 localhost mysqld_safe[6640]: 091021  1:38:13 [Warning] Forcing 
shutdown of 2 plugins
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: PLEASE REMEMBER TO SET A PASSWORD 
FOR THE MySQL root USER !
Oct 21 01:38:13 localhost mysqld_safe[6640]: To do so, start the server, then 
issue the following commands:
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: /usr/bin/mysqladmin -u root 
password 'new-password'
Oct 21 01:38:13 localhost mysqld_safe[6640]: /usr/bin/mysqladmin -u root -h 
localhost password 'new-password'
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: Alternatively you can run:
Oct 21 01:38:13 localhost mysqld_safe[6640]: /usr/bin/mysql_secure_installation
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: which will also give you the 
option of removing the test
Oct 21 01:38:13 localhost mysqld_safe[6640]: databases and anonymous user 
created by default.  This is
Oct 21 01:38:13 localhost mysqld_safe[6640]: strongly recommended for 
production servers.
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: See the manual for more 
instructions.
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: Please report any problems with 
the /usr/scripts/mysqlbug script!
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6640]: The latest information about MySQL 
is available at http://www.mysql.com/
Oct 21 01:38:13 localhost mysqld_safe[6640]: Support MySQL by buying 
support/licenses from http://shop.mysql.com/
Oct 21 01:38:13 localhost mysqld_safe[6640]: 
Oct 21 01:38:13 localhost mysqld_safe[6686]: 091021  1:38:13 [Note] Plugin 
'FEDERATED' is disabled.
Oct 21 01:38:13 localhost mysqld_safe[6686]: 091021  1:38:13  InnoDB: Started; 
log sequence number 0 44233
Oct 21 01:38:13 localhost mysqld_safe[6686]: 091021  1:38:13  InnoDB: Starting 
shutdown...
Oct 21 01:38:14 localhost mysqld_safe[6686]: 091021  1:38:14  InnoDB: Shutdown 
completed; log sequence number 0 44233
Oct 21 01:38:14 localhost mysqld_safe[6686]: 091021  1:38:14 [Warning] Forcing 
shutdown of 1 plugins
Oct 21 01:38:15 localhost mysqld_safe[6738]: 091021  1:38:15 [Note] Plugin 
'FEDERATED' is disabled.
Oct 21 01:38:15 localhost mysqld_safe[6738]: 091021  1:38:15  InnoDB: Started; 
log sequence number 0 44233
Oct 21 01:38:15 localhost mysqld_safe[6738]: 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 01:38:15 localhost mysqld_safe[6738]: 091021  1:38:15 [ERROR] Aborting
Oct 21 01:38:15 localhost mysqld_safe[6738]: 
Oct 21 01:38:15 localhost mysqld_safe[6738]: 091021  1:38:15  InnoDB: Starting 
shutdown...
Oct 21 01:38:17 localhost mysqld_safe[6738]: 091021  1:38:17  InnoDB: Shutdown 
completed; log sequence number 0 44233
Oct 21 01:38:17 localhost mysqld_safe[6738]: 091021  1:38:17 [Warning] Forcing 
shutdown of 1 plugins
Oct 21 01:38:17 localhost mysqld_safe[6738]: 091021  1:38:17 [Note] 
/usr/sbin/mysqld: Shutdown complete
Oct 21 01:38:17 localhost mysqld_safe[6738]: 
Oct 21 01:38:17 localhost mysqld_safe[6760]: 091021  1:38:17 [Note] Plugin 
'FEDERATED' is disabled.
Oct 21 01:38:17 localhost mysqld_safe[6760]: 091021  1:38:17  InnoDB: Started; 
log sequence number 0 44233
Oct 21 01:38:17 localhost mysqld_safe[6760]: 091021  1:38:17  InnoDB: Starting 
shutdown...
Oct 21 01:38:18 localhost mysqld_safe[6760]: 091021  1:38:18  InnoDB: Shutdown 
completed; log sequence number 0 44233
Oct 21 01:38:18 localhost mysqld_safe[6760]: 091021  1:38:18 [Warning] Forcing 
shutdown of 1 plugins
Oct 21 01:38:18 localhost mysqld_safe[6786]: 091021  1:38:18 [Note] Plugin 
'FEDERATED' is disabled.
Oct 21 01:38:18 localhost mysqld_safe[6786]: 091021  1:38:18  InnoDB: Started; 
log sequence number 0 44233
Oct 21 01:38:18 localhost mysqld_safe[6786]: ERROR: 1050  Table 'plugin' 
already exists
Oct 21 01:38:18 localhost mysqld_safe[6786]: 091021  1:38:18 [ERROR] Aborting
Oct 21 01:38:18 localhost mysqld_safe[6786]: 
Oct 21 01:38:18 localhost mysqld_safe[6786]: 091021  1:38:18  InnoDB: Starting 
shutdown...

Bug#545751: [debian-mysql] Bug#545751:

2009-09-20 Thread Norbert Tretkowski
reopen 545751
thanks

Am Sonntag, den 20.09.2009, 00:40 -0500 schrieb Ian Greenhoe:
 I just got bitten by this myself.
 
 I have to say that this *is* a bug -- a perfectly legal MySQL
 configuration file for 5.0 causes the 5.1 server to crash in such a way
 as to prevent the upgrade process from finishing.

We are not allowed to change files in /etc/ during an upgrade by policy,
so the only way to fix this is to abort the upgrade process when the
skip-bdb option is found in /etc and display an explanation.

Norbert




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org