FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › 1249 – crashes on DB insert
- This topic has 7 replies, 4 voices, and was last updated 18 years, 6 months ago by rpedde.
-
AuthorPosts
-
21/06/2006 at 8:13 PM #380MCFHParticipant
Ron,
My 1249 build crashes with:
2006-06-20 : Error inserting file (null) in database
I haven’t got debugging on at the moment – so will switch it on and see if I can give you more data!
Regards
Mark21/06/2006 at 8:36 PM #5183MCFHParticipantLog extract at level 9…
22/06/2006 at 2:37 AM #5184rpeddeParticipant@MCFH wrote:
Log extract at level 9…
Yeah, crap. I forgot to mention that you have to delete your songs.db and let it create a new one. Plus, I forgot to increment the db version.
22/06/2006 at 2:37 AM #5185rpeddeParticipant@MCFH wrote:
Log extract at level 9…
Yeah, crap. I forgot to mention that you have to delete your songs.db and let it create a new one. Plus, I forgot to increment the db version.
26/06/2006 at 2:12 AM #5186jloiselleGuestin this same build, when i try to run the daemon, it fails with this:
2006-06-25 22:07:42: Starting mp3 scan
2006-06-25 22:07:42: Error inserting file Coldplay – Everything’s Not Lost.mp3 in database
2006-06-25 22:07:42: Abortingi have sqlite3 and am running this on:
Linux particle 2.6.12-gentoo-r6 #2 SMP Sat Oct 1 04:43:09 EDT 2005 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz GenuineIntel GNU/Linux
what can i do to fix this?
26/06/2006 at 2:31 PM #5187jloiselleGuestactually.. now i set the mp3_dir to a directory without any files.. then i deleted songs3.db and now i get this…
2006-06-26 10:26:18: Starting mp3 scan
2006-06-26 10:26:18: Query: create index idx_path on songs(path)
2006-06-26 10:26:18: Error: no such table: main.songs
2006-06-26 10:26:18: Abortingit creates the songs3.db file but it has zero size.
26/06/2006 at 11:58 PM #5188Ted HarperParticipant@rpedde wrote:
I forgot to mention that you have to delete your songs.db and let it create a new one. Plus, I forgot to increment the db version.
I missed this earlier; should _ALL_ users (eg on my NSLU2) have deleted songs.db and forced a full rescanning when updating Firefly from svn-1236 to svn-1249?
I didn’t do that and I haven’t had a crash of Firefly, but then again I haven’t bought any new CDs and added any new music to the Firefly library since upating to svn-1249 either.
If I do need to delete and rescan the library, I assume the procedure on the NSLU2 is to killall the mt-daapd processes, then delete the library file, then run the init.d script to fire it up again? Is that correct? Can the installer perhaps in the future delete (or at least prompt for deletion) the songs library when an upgrade is installed that needs a new database schema element that can’t otherwise be done on the fly?
ted.h.
27/06/2006 at 5:20 AM #5189rpeddeParticipant@Ted Harper wrote:
I missed this earlier; should _ALL_ users (eg on my NSLU2) have deleted songs.db and forced a full rescanning when updating Firefly from svn-1236 to svn-1249?
If you aren’t having a problem, don’t worry about it. It will fix itself next drop.
— Ron
-
AuthorPosts
- The forum ‘Nightlies Feedback’ is closed to new topics and replies.