erland;564423 Wrote: > There was a lots of errors in that log, so I'm not really sure where to > start. If the logs looks like this log file, my experience is that the > system isn't working very well.
Thank you for your quick response! erland;564423 Wrote: > 1. > From all the "Illegal mix of collations" error you have in the log, I > suspect you have hit the following bug: > http://bugs.slimdevices.com/show_bug.cgi?id=15116 > If you keep getting this after SBS restart I'd try changing to English > as user interface language in SBS Settings to see if the server starts > without these errors. If you continue to get the illegal mix of > collations error at startup nothing is going to work with my plugins > when you are browsing or generating playlists. The Custom Scan data > might possibly work in some cases because it's mostly joined using > integer keys, but if you get this with TrackStat none of the queries > using TrackStat data is going to work. I had those messages on the old PC also and your plugins worked. I had to switch language from Swedish to English and then straight back to Swedish on the new PC because this old bug resurfaced http://bugs.slimdevices.com/show_bug.cgi?id=10114. At least CustomBrowse and TrackStat work on the new PC despite the error messages. I will try to switch to English and stick with English to see if the errors go away. erland;564423 Wrote: > 2. > The "Converting customscan_track_attributes to correct charset=utf8 > collate=utf8_swedish_ci" message indicates that it's converting the > character set in the database, basically it tries to fix the "illegal > mix of collations" problem. Normally it should only need to do this > when the tables are empty and then it should be really fast. However, > if I remember correctly, due to the above mentioned bug the database > can actually change collate when used if you change the language > setting. So if you change the language when the tables are filled with > data, it's probably going to take some time to do the conversion, still > an hour for converting some characters still sounds a bit much. The good > news is that as long as you haven't hit the bug in 1, it's only going to > happen once, after it has been converted it shouldn't need to convert > them at the next startup. Yes, it seems like a one time event. I just wanted to report the one hour delay with CustomScan. erland;564423 Wrote: > 3. > There was some "Can't connect to MySQL server on '127.0.0.1' " errors > in the log, this indicates that something is wrong with the MySQL > database. Either it's very busy or it hasn't started successfully. I've > no idea why unless it's caused by the conversion in point 2 above. OH, never mind those. They are from a couple of times when I thought that SBS had stalled completely and manually killed the relevant processes because SBS was totally unresponsive and could not be stopped the normal way. Finally I decided to wait out CustomScan's 1 hour converting. erland;564423 Wrote: > 4. > Errors like this: > "Can't create table '.\slimserver\#sql-4f0_2.frm' (errno: 121)" > Typically means that the disk is full or there are some antivirus > software which isn't configured to ignore the MySQL files. The disc is not full. I use Microsoft Security Essentials on the new PC. I have excluded .myd and .myi files as well as the processes SqueezeSvr.exe and Mysgld.exe. Should I exclude also .frm files? (There seems to be no way to temporarily disable Microsoft Security Essentials. I guess I could switch to Avast instead which worked on the old PC.) erland;564423 Wrote: > 5. > Errors like this: > "Query returned more than one row. SQL that returns multiple rows is > DEPRECATED for ->find and ->single at > /<C:\Program\SQUEEZ~1\server\SQUEEZ~3.EXE>Slim/Schema/Track.pm line > 248" > Is generally bad since it means that there are duplicate rows in the > database, I suspect it's caused if you run parallel works that's > supposed to be serialized. I think there are checks to avoid this in > most places but I know some users have reported there problems with > TrackStat so it might be possible to run duplicate restore operations > or something similar in TrackStat. For the TrackStat tables you can > usually, take a backup of the TrackStat data, in the TrackStat > interface select to delete all data and finally restore the backup to > get rid of this problem. If the problem is related to the Custom Scan > data, it will probably disappear after you have done the next rescan. I restored TrackStat data from the old PC just once, but I did not delete the existing TrackStat data first (there should not have been much data since I have only played a couple of tracks to try out the new setup). I will delete and then restore the TrackStat data from the old PC. -- vagskal 2 x SB3 (wired), Receiver (wireless), Boom (wireless), Controller, iPeng on iPod Touch, muso on remote computer running Win 7 | 7.5.2 on Win XP ------------------------------------------------------------------------ vagskal's Profile: http://forums.slimdevices.com/member.php?userid=20778 View this thread: http://forums.slimdevices.com/showthread.php?t=49483 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
