It seems like the last step in the refresh takes a bit more time than I
would like (135 seconds), so for now you probably want to keep the
"Startup refresh" option disable. If you don't it will take at least a
2.5 minutes until SlimServer is accessible after a restart.
The delete operation doesn't seem to be a problem.
If we can trust the MySQL message, the tables seems to get corrupted as
they where when you run this last time a few days back. It seems to
happen when the Custom Tag information shall be merged into the Mixed
Tag data. The first steps seems to work that merges standard SlimServer
data, but the last step that should merge the custom tags fails.
I could think of a few reasons why this could happend:
- The disk where the database files or it temporary files is stored
gets full.
- MySQL runs out of memory and that corrupts the table, but in that
case I would really have expected some error regarding out of memory
instead.
I would suggest the following:
1.
Check if any of the disks on the NAS is full, you should be able to see
this if you just login to the NAS and in a shell prompt runs: df
2.
If there are no full disks, I would suggest that you restore the
database backup you took earlier as this is a good starting point.
3.
The SQL statements that causes everything to fail looks as follows:
Code:
--------------------
INSERT INTO customscan_track_attributes
(track,url,musicbrainz_id,module,attr,value,valuesort,extravalue) SELECT
tracks.id,tracks.url,case when tracks.musicbrainz_id regexp '.+-.+'>0 then
tracks.musicbrainz_id else null
end,'mixedtag',customscan_track_attributes.attr,customscan_track_attributes.value,customscan_track_attributes.valuesort,customscan_track_attributes.value
from tracks,customscan_track_attributes where tracks.audio=1 and
tracks.id=customscan_track_attributes.track and
customscan_track_attributes.module='customtag'
--------------------
When you have restored the backup you can connect with a standard SQL
client of your choice and run this statement and see if the behaviour
is reproducable this way. If the problem is reproducable this way, you
might want to check the memory and diskusage during the operation.
4.
If you couldn't reproduce the problem in step 3, I would suggest that
you restore the backup again. Then disable the "Include custom tags"
option in the Mixed Tag scanning module and click the "Scan" button
besides the "Mixed Tag" module again. This scanning should successfully
be able to complete, but it won't store any custom tags. If it succeeds,
make a new backup of the database in this state and after this execute
the SQL statement mentioned in step 3 again and see if you can
reproduce the problem. Try to check the memory and diskusage during the
operation.
Other things to look for:
- I'm not sure if the MySQL instance which is executed through
SlimServer puts additional log files somewhere, if it does you might
want to look for further error messages there which might show you more
detailed errors.
- The standard log files usually stored in /var/log might also be a
good place to look for additional error information.
--
erland
Erland Isaksson
'My homepage' (http://erland.homeip.net) 'My download page'
(http://erland.homeip.net/download)
(Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse,
Custom Scan, Custom Skip, Multi Library and Database Query plugins'
(http://wiki.erland.homeip.net/index.php/Category:SlimServer))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=38256
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins
