Bug 402 - writing out cache db can stop the music.
: writing out cache db can stop the music.
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Audio
: 5.x or older
: Macintosh All
: P2 normal with 1 vote (vote)
: ---
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-06-23 15:17 UTC by Blackketter Dean
Modified: 2008-12-18 11:53 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2004-06-23 15:17:55 UTC
With the tag db caching turned on, about every hour or so of continuous
play, the music stops for about 3-4 seconds, then starts again where it left
off. This does NOT happen with the tag db caching turned off. Very strange.
Comment 1 KDF 2004-06-24 10:20:33 UTC
how big is the library/dbfile in this case?
is the dbfile stored on the same filesystem as the running server, or on a
network filesystem?
Comment 2 Michael Bird 2004-06-26 17:11:42 UTC
The db file is approx 38MB. The db file, slimserver and music library are all 
on the same system. The slimserver and db file are on the system drive, the 
music library is on a hardware RAID 5 array. The OS is Windows Server 2003 
running on an Intel 2GHz Celeron with 512MB RAM.
Comment 3 Andrew Prime 2004-06-28 07:00:30 UTC
I have the same problem. My db file is 11mb, I have around a 350gb library of, 
mostly, 320kbps MP3's with cuesheets. This is running on a P3-500, 384mb RAM. 
The db file is on the internal HD and the music files are on external usb2 HD's.
And the gaps happen almost exactly 1 hour apart.
Comment 4 Blackketter Dean 2004-08-12 09:08:43 UTC
vidur's database work should address this.
Comment 5 KDF 2005-03-05 03:16:30 UTC
this has been reported ok cleared up.
Comment 6 Chris Owens 2006-06-16 14:40:23 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Comment 7 Chris Owens 2008-12-18 11:53:32 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.