[opensuse] MySQL Update Table Error.

newer
[opensuse] No GUI 10.3 new install

older
[opensuse] Way to detect the type...

G T Smith

5 Oct 2007 5 Oct '07

14:14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SuSE 10.2 Did an update today including MySQL security updates. Found MySQL had failed to reload for some reason. Restarted MySQL and got a a duplicate column error message when an attempt to update the mysql database tables was applied. (unfortunately, error message went before I could take notes and nothing in logs). Nothing seems to broken but unable to repeat error (I suspect because the database schema update has now been flagged as applied). Because there is an issue with funambol I am running MySQL with case sensitivity disabled... As I do not think this is a change applied at the MySQL end (the mysql schema is reasonably consistent across platforms and if this is a case of two columns differing by case this it would generate problems on Windows) I am not sure whether the update has been applied a second time for some reason (then I need not worry) or there has been a change and I should have two columns lexically differing only on case or replaced. Has anyone noticed anything similar? - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHBka3asN0sSnLmgIRAmHxAJ4+N6CJRkPhzHNehWRHVHJGCRdB/gCgxDUv Ll50rIlHUAWSYOF87fQPlCI= =uzGv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

J Sloan

5 Oct 5 Oct

15:13

G T Smith wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

SuSE 10.2

Did an update today including MySQL security updates.

Found MySQL had failed to reload for some reason. Restarted MySQL and got a a duplicate column error message when an attempt to update the mysql database tables was applied. (unfortunately, error message went before I could take notes and nothing in logs). Nothing seems to broken but unable to repeat error (I suspect because the database schema update has now been flagged as applied).

Because there is an issue with funambol I am running MySQL with case sensitivity disabled...

As I do not think this is a change applied at the MySQL end (the mysql schema is reasonably consistent across platforms and if this is a case of two columns differing by case this it would generate problems on Windows) I am not sure whether the update has been applied a second time for some reason (then I need not worry) or there has been a change and I should have two columns lexically differing only on case or replaced.

Has anyone noticed anything similar?

Yes, I noticed that mysql was dead after the last upgrade on my suse 10.2/64 server, and a bit of lookikng in the the mysqld log turned up a complaint about a duplicate column IIRC - but I started it with the rc script and it has run normally from that point on, so I hadn't give it too much further thought. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

G T Smith

15:35

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 J Sloan wrote:

...

G T Smith wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

SuSE 10.2

<snip>

...

...
Yes, I noticed that mysql was dead after the last upgrade on my suse 10.2/64 server, and a bit of lookikng in the the mysqld log turned up a complaint about a duplicate column IIRC - but I started it with the rc script and it has run normally from that point on, so I hadn't give it too much further thought.

Joe

Interesting.. my mysqld.log did not report this error at all, ... in fact it also did not report anything before it got pulled down (but I think logrotate has something to do with that). Seems to be nothing to worry about then .... I hope :-) - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHBlnSasN0sSnLmgIRAnzVAKDYrHfG0mAFMDRZJjFlPMGEthJWzwCfddY8 NqLu3C/HQTPY4pthmvdR9nM= =tDKv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michal Marek

8 Oct 8 Oct

14:05

J Sloan wrote:

...

G T Smith wrote:

...
SuSE 10.2

Did an update today including MySQL security updates.

Found MySQL had failed to reload for some reason. Restarted MySQL and got a a duplicate column error message when an attempt to update the mysql database tables was applied. (unfortunately, error message went before I could take notes and nothing in logs). Nothing seems to broken but unable to repeat error (I suspect because the database schema update has now been flagged as applied).

Yes, I noticed that mysql was dead after the last upgrade on my suse 10.2/64 server, and a bit of lookikng in the the mysqld log turned up a complaint about a duplicate column IIRC - but I started it with the rc script and it has run normally from that point on, so I hadn't give it too much further thought.

Hi, the 'duplicate column' errors come from mysql_fix_privilege_tables.sql and are in fact harmless (see https://bugzilla.novell.com/228248 , fixed in 10.3). However, it seems that the init script thinks that something failed during the upgrade :-(. Could you try # touch /var/lib/mysql/.run-mysql_upgrade # rcmysql restart ? Also please file a bugreport and assign it to mmarek@novell.com. I'm going to try it myself. thanks, Michal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

G T Smith

9 Oct 9 Oct

11:52

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michal Marek wrote:

...

J Sloan wrote:

...
G T Smith wrote:

...
SuSE 10.2

Did an update today including MySQL security updates.

Found MySQL had failed to reload for some reason. Restarted MySQL and got a a duplicate column error message when an attempt to update the mysql database tables was applied. (unfortunately, error message went before I could take notes and nothing in logs). Nothing seems to broken but unable to repeat error (I suspect because the database schema update has now been flagged as applied).

Yes, I noticed that mysql was dead after the last upgrade on my suse 10.2/64 server, and a bit of lookikng in the the mysqld log turned up a complaint about a duplicate column IIRC - but I started it with the rc script and it has run normally from that point on, so I hadn't give it too much further thought.

Hi,

the 'duplicate column' errors come from mysql_fix_privilege_tables.sql and are in fact harmless (see https://bugzilla.novell.com/228248 , fixed in 10.3). However, it seems that the init script thinks that something failed during the upgrade :-(. Could you try

# touch /var/lib/mysql/.run-mysql_upgrade # rcmysql restart

? Also please file a bugreport and assign it to mmarek@novell.com. I'm going to try it myself.

thanks, Michal

Whoa! Some clarification here... in my case this was not a big issue... Originally I just needed to make certain that that I was not picking up a problem that was something specific to my setup (which is not exactly standard SuSE). I have run the above without any issues, and as far as I can work out the problem (if it really was a problem) is fixed (for me) with 10.2... I will file a report if you still wish me to, and BTW should it be against original... I cannot say anything about the 10.3 reports as I am still on 10.2. (As I have accumulated number of non-SuSE bits and pieces I am probably going to be late to the 10.3 party as I need to put together a cunning plan to manage the 10.3 upgrade :-) ) So I am not really best placed to comment on these... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHC2t4asN0sSnLmgIRAoYlAJ9xu0QMkWyxEv1xdXUiEGHZPegzYQCeKF8G PnIoW8ZRG+KKEg731z1UfhQ= =UVJd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michal Marek

13:09

G T Smith wrote:

...

I have run the above without any issues, and as far as I can work out the problem (if it really was a problem) is fixed (for me) with 10.2...

Yeah, it's not _that_ bug issue as long as your data is there, but still the fact that mysqld sometimes doesn't restart after the sec. update scares me. But I weren't able to reproduce it yet.

...

I will file a report if you still wish me to, and BTW should it be against original...

Thanks.

...

I cannot say anything about the 10.3 reports as I am still on 10.2.

Well, the 10.3 reports are unrelated

...

I am probably going to be late to the 10.3 party as I need to put together a cunning plan to manage the 10.3 upgrade :-)

;-) Michal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

G T Smith

10 Oct 10 Oct

12:47

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michal Marek wrote:

...

G T Smith wrote:

<snip>

...

...
I will file a report if you still wish me to, and BTW should it be against original...

Thanks.

Finally (hopefully) as required... https://bugzilla.novell.com/show_bug.cgi?id=332530

...

...
I cannot say anything about the 10.3 reports as I am still on 10.2.

<snip> - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHDMniasN0sSnLmgIRAjF5AJ41LmLUxOh1g/3iBxaBjqDNII2U9wCeN+B+ Z9ljw6dRCAFQmtevGmdN+rc= =aJ31 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ionut Vancea

19:44

Hello,

...

Finally (hopefully) as required...

https://bugzilla.novell.com/show_bug.cgi?id=332530

ten minutes ago Suse asked me to do some updates, I did, and now, mysql is working again well. I don't know which was the problem, but now I am happy that it is solved. thanks, Ionut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ionut Vancea

8 Oct 8 Oct

23:13

hello, On 10/5/07, G T Smith wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

SuSE 10.2

Did an update today including MySQL security updates.

Found MySQL had failed to reload for some reason. Restarted MySQL and got a a duplicate column error message when an attempt to update the mysql database tables was applied. (unfortunately, error message went before I could take notes and nothing in logs). Nothing seems to broken but unable to repeat error (I suspect because the database schema update has now been flagged as applied).

Because there is an issue with funambol I am running MySQL with case sensitivity disabled...

As I do not think this is a change applied at the MySQL end (the mysql schema is reasonably consistent across platforms and if this is a case of two columns differing by case this it would generate problems on Windows) I am not sure whether the update has been applied a second time for some reason (then I need not worry) or there has been a change and I should have two columns lexically differing only on case or replaced.

Has anyone noticed anything similar?

yes, I have something similar. After I did the update from 10.2 to 10.3 mysql doesn't work. It seems that the databases and the tables are ok, the mysql is starting, but when I tried wordpress, mambo, mysql.log tells me that mysql restarted during a SELECT. I tried this SELECT command also in mysql command line, also in phpmyadmin, but I got the same error and mysqld restarted. I don't know how to fix that. thanks, -- === Ioan Vancea http://www.vioan.ro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Guillermo Ballester Valor

9 Oct 9 Oct

05:33

El Monday 08 October 2007 23:13:57 Ionut Vancea escribió:

...

hello,

On 10/5/07, G T Smith wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

SuSE 10.2

Did an update today including MySQL security updates.

Found MySQL had failed to reload for some reason. Restarted MySQL and got a a duplicate column error message when an attempt to update the mysql database tables was applied. (unfortunately, error message went before I could take notes and nothing in logs). Nothing seems to broken but unable to repeat error (I suspect because the database schema update has now been flagged as applied).

Because there is an issue with funambol I am running MySQL with case sensitivity disabled...

As I do not think this is a change applied at the MySQL end (the mysql schema is reasonably consistent across platforms and if this is a case of two columns differing by case this it would generate problems on Windows) I am not sure whether the update has been applied a second time for some reason (then I need not worry) or there has been a change and I should have two columns lexically differing only on case or replaced.

Has anyone noticed anything similar?

yes, I have something similar. After I did the update from 10.2 to 10.3 mysql doesn't work. It seems that the databases and the tables are ok, the mysql is starting, but when I tried wordpress, mambo, mysql.log tells me that mysql restarted during a SELECT. I tried this SELECT command also in mysql command line, also in phpmyadmin, but I got the same error and mysqld restarted. I don't know how to fix that.

I had the same problem than you, i.e, mysql was continuosly restarting after select after upgrading to 10.3 . The logs were showing crashes. My solution was to recompile the binaries linked with (using) mysql-client library. Then all gone well again. I was very worry by that, all my website were down. It seems like an incompatibility somewhere in the libraries. Guillermo

...

thanks,

-- === Ioan Vancea http://www.vioan.ro

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ionut Vancea

07:43

hello, On 10/9/07, Guillermo Ballester Valor wrote:

...

I had the same problem than you, i.e, mysql was continuosly restarting after select after upgrading to 10.3 . The logs were showing crashes. My solution was to recompile the binaries linked with (using) mysql-client library. Then all gone well again. I was very worry by that, all my website were down.

thank you, I don't understand exactly, do you want to say that I need to recompile mysql server package? /Ionut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Guillermo Ballester Valor

12:47

El Tuesday 09 October 2007 07:43:56 Ionut Vancea escribió:

...

hello,

On 10/9/07, Guillermo Ballester Valor wrote:

...
I had the same problem than you, i.e, mysql was continuosly restarting after select after upgrading to 10.3 . The logs were showing crashes. My solution was to recompile the binaries linked with (using) mysql-client library. Then all gone well again. I was very worry by that, all my website were down.

thank you, I don't understand exactly, do you want to say that I need to recompile mysql server package?

Sorry, I meant that I had to compile again my local projects linked against mysqlclient library. After a new make and 'make install' for those projects all gone well. These are not rpms, are local projects. Guillermo

...

/Ionut

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michal Marek

11:18

Ionut Vancea wrote:

...

hello,

On 10/5/07, G T Smith wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

SuSE 10.2

Did an update today including MySQL security updates.

yes, I have something similar. After I did the update from 10.2 to 10.3 mysql doesn't work.

That must be something different, but please file a bugreport (https://bugzilla.novell.com/) as well. Michal

...

It seems that the databases and the tables are ok, the mysql is starting, but when I tried wordpress, mambo, mysql.log tells me that mysql restarted during a SELECT. I tried this SELECT command also in mysql command line, also in phpmyadmin, but I got the same error and mysqld restarted. I don't know how to fix that.

thanks,

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

6050

Age (days ago)

6055

Last active (days ago)

List overview

Download

12 comments

5 participants

participants (5)

G T Smith
Guillermo Ballester Valor
Ionut Vancea
J Sloan
Michal Marek