In the latest 7.9 nightlies (1400229154) I've added some more
information to the scanner.log file. At the end of a wipe rescan the
scanner will log some statistics about the indices used in the
underlying database:
[14-05-16 10:55:34.5177] Slim::Schema::optimizeDB (433)
albumsArtworkIndex:
I don't think I am able to assign a bug to you? But I added it in
bugs.slimdevices.com:
http://bugs.slimdevices.com/show_bug.cgi?id=18093
::Please vote:::
'::bug 1330:: New music should work on creation date'
(http://bugs.slimdevices.com/show_bug.cgi?id=1330)
'::bug 17542:: New and changed
bonze wrote:
The path for the Cache folder in server.prefs was incorrect, and I don't
know how it got in there
A relict of an XP installation?
reinholdk's Profile:
Code:
[14-05-16 07:08:07.4697] Slim::Schema::optimizeDB (433)
albumsArtworkIndex: 2280 2
[14-05-16 07:08:07.4700] Slim::Schema::optimizeDB (433)
albumsDiscCountIndex: 2280 326
[14-05-16 07:08:07.4702] Slim::Schema::optimizeDB (433)
Code:
[14-05-16 11:47:15.6428] main::main (202) Starting Logitech Media Server
scanner (v7.9.0, 1400229154, Fri May 16 08:52:23 CUT 2014) perl
5.014001[14-05-16 11:47:16.2318] Slim::Schema::forceCommit (2126) Warning:
Trying to commit transactions before DB is
mherger wrote:
Would the messages go away after a few minutes? I've seen similar issues
when I eg. left a web UI open when I restarted the server: the server
wouldn't know about the client the web UI was asking for information
for, yet, as the client had not connected yet. I could
Code:
[14-05-16 06:05:19.3367] main::main (202) Starting Logitech Media Server
scanner (v7.9.0, TRUNK, UNKNOWN) perl 5.014001
[14-05-16 06:05:19.9617] Slim::Schema::forceCommit (2126) Warning: Trying to
commit transactions before DB is initialized!
[14-05-16
Even if the cache pref points to the wrong folder, I don't see how
that in itself can cause a problem. As long as LMS can read and write to
the folder.
JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10
reinholdk wrote:
A relict of an XP installation?
WHS version 1 had a similar folder structure to XP I think, which is
where the server.prefs would have come from.
Although I upgraded to WHS2011 a while ago, and I can't remember having
problems at the time.
Thinking back I may have done a
bonze wrote:
Presumably because the folder didn't exist it wouldn't know where to
create the database.
LMS will create the cache folder if it doesn't exist. There's no
correct folder. That's what the pref is for ... so you can change it
if you like.
10 matches
Mail list logo
