PDA

View Full Version : mysql charset errors since moving to 7.0



2eleven
2007-10-24, 16:38
Folks,

I've been getting some seemingly harmless but not very pretty errors to my screen on sqeezecenter startup ever since switching to 7.0. I'm using a linux box w/o mysql installed, but it seems that the slim-packaged mysql might be looking for some systemwide mysql charsets. The error messages are below.

I'm not a mysql expert, so I thought I'd see if I am an idiot before I file a bug. Am I missing anything obvious?

Cheers,

John


[16:28:03.5391] SqueezeCenter OSDetect init...
[16:28:03.6155] SqueezeCenter settings init...
[16:28:03.6201] main::init (283) SqueezeCenter OS Specific init...
[16:28:03.6206] main::init (303) SqueezeCenter daemonizing...
[16:28:03.6397] Slim::bootstrap::theEND (400) Got to the END

File '/usr/share/mysql/charsets/?.conf' not found (Errcode:
2)
Character set '#33' is not a compiled character set and is not specified in the
'/usr/share/mysql/charsets/Index' file
File '/usr/share/mysql/charsets/?.conf' not found (Errcode: 2)
Character set '#33' is not a compiled character set and is not specified in the
'/usr/share/mysql/charsets/Index' file
File '/usr/share/mysql/charsets/?.conf' not found (Errcode: 2)
Character set '#33' is not a compiled character set and is not specified in the
'/usr/share/mysql/charsets/Index' file
File '/usr/share/mysql/charsets/?.conf' not found (Errcode: 2)
Character set '#33' is not a compiled character set and is not specified in the
'/usr/share/mysql/charsets/Index' file
File '/usr/share/mysql/charsets/?.conf' not found (Errcode: 2)
Character set '#33' is not a compiled character set and is not specified in the
'/usr/share/mysql/charsets/Index' file

kdf
2007-10-24, 17:53
You'll find that these are files a few times in, now closed, bugs. It's a warning from mysql and not really SS/SC can do about it. They are, however, harmless. They are a result of a version mismatch between mysql provided by SS/SC and something else running on your system (often a system mysql)

-kdf

http://bugs.slimdevices.com/show_bug.cgi?id=3845
http://bugs.slimdevices.com/show_bug.cgi?id=5288

2eleven
2007-10-24, 18:29
You'll find that these are files a few times in, now closed, bugs. It's a warning from mysql and not really SS/SC can do about it. They are, however, harmless. They are a result of a version mismatch between mysql provided by SS/SC and something else running on your system (often a system mysql)

-kdf

http://bugs.slimdevices.com/show_bug.cgi?id=3845
http://bugs.slimdevices.com/show_bug.cgi?id=5288

I'm glad this is a known issue, but I wish there was a way to clean up the output so as not to alarm users. In my case, I would point out that a) this didn't happen with 6.x and b) I don't have mysql installed on my system so I wouldn't expect version mismatch issues.

Regardless of whether the issue is directly related to ss/sc or not, it doesn't add to the user friendliness of the product to have errors (harmless or not) spewed to the terminal. Maybe we should consider re-opening one of the bugs and finding a way to make this cleaner? At the very least we could have sc output a message saying that the mysql charset errors are harmless.

John

kdf
2007-10-24, 18:52
there is already one in there marked for "later" (just do a search,
because I only posted two of them)
please post there, and let ppl focus on one thing at a time.
-kdf