FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Setup Issues › FireFly keeps stopping
- This topic has 7 replies, 4 voices, and was last updated 16 years, 2 months ago by Anonymous.
-
AuthorPosts
-
19/11/2007 at 7:35 AM #1961AnonymousInactive
…saying:
2007-11-19 07:09:25 (49534c08): Error: unable to open database file
2007-11-19 07:09:25: AbortingWhen I start it again it starts fine. So what can be so wrong about the database file that it cannot open it?
I have tried deleting the database file, but that didn’t help.
21/11/2007 at 4:21 AM #14619rpeddeParticipant@Franc wrote:
…saying:
2007-11-19 07:09:25 (49534c08): Error: unable to open database file
2007-11-19 07:09:25: AbortingWhen I start it again it starts fine. So what can be so wrong about the database file that it cannot open it?
I have tried deleting the database file, but that didn’t help.
Appears to be a bug in the windows port. Right now I’m working on re-doing the database, so we’ll see if that helps. Hopefully done by the end of the eekend.
— Ron
17/12/2007 at 3:34 AM #14620AnonymousInactiveHi,
I’m running Firefly Service 1.0 svn-1359
on a WinXP system, SP2, WMP11. My music is on my F: (second physical HDD)Every so often, Firefly shuts down. Log says “Error: unable to open database file”.
If I restart it manually, I am good for some amount of time, maybe a day, maybe a few hours. Then it dies again.
Help?
17/12/2007 at 3:54 AM #14621AnonymousInactiveOK, I downloaded latest nightly build, we’ll see how it goes.
@blood_donor wrote:
Hi,
I’m running Firefly Service 1.0 svn-1359
on a WinXP system, SP2, WMP11. My music is on my F: (second physical HDD)Every so often, Firefly shuts down. Log says “Error: unable to open database file”.
If I restart it manually, I am good for some amount of time, maybe a day, maybe a few hours. Then it dies again.
Help?
08/03/2008 at 11:29 PM #14622AnonymousInactiveHi – got the same problem – here’s what my logfile says, can anyone help?
Thnks!2008-03-08 22:27:27 (00004000): Firefly Version svn-1696: Starting with debuglevel 2
2008-03-08 22:27:27 (00004000): Plugin loaded: rsp/svn-1696
2008-03-08 22:27:27 (00004000): Plugin loaded: daap/svn-1696
2008-03-08 22:27:27 (00004000): Plugin loaded: ssc-script/svn-1696
2008-03-08 22:27:27 (00004000): Starting rendezvous daemon
2008-03-08 22:27:27 (00004000): Starting signal handler
2008-03-08 22:27:27 (00004000): Initializing database
2008-03-08 22:27:47 (00004000): Starting web server from /opt/local/mt-daapd/share/mt-daapd/admin-root on port 3689
2008-03-08 22:27:47 (00004000): Registering rendezvous names
2008-03-08 22:27:47 (00004000): Serving 237 songs. Startup complete in 20 seconds
2008-03-08 22:27:52 (00010003): Thread 0: Entering ws_returnerror (302: Moved)
2008-03-08 22:38:18 (00004000): Got HUP signal.
2008-03-08 22:38:18 (00004000): Error opening config file: No such file or directory
2008-03-08 22:38:20 (00004000): Rendezvous socket closed (daap server crashed?) Aborting.
2008-03-08 22:38:20: Abortingcheers, Mc
12/03/2008 at 12:09 PM #14623AnonymousInactiveHi there – this issue is keeping me busy long times – anybody who can possibly help?
thanks – Marcus
12/03/2008 at 7:37 PM #14624AnonymousInactiveAfter limitless tries I finally found the below thread
http://forums.fireflymediaserver.org/viewtopic.php?p=17598Suggests to kill or even rename the Synology indexing process, as follows:
Ron said
Ah, the hup thing. yeah. On non-nptl pthreads machines (or maybe it’s ulibc machines, not sure) a sighup makes it crash. The thing is, the synology has a disk indexer that indexes any new media on the file system, and then HUPs mt-daapd to make it reindex. Sadly, that makes it die.
The workaround is to kill the synology indexer thing.
and then SydneyGuy suggested
What I did to get around the dreaded HUP problem was to rename /usr/syno/bin/synoindex to synoindex.old
It’s a heavy handed approach but it stopped the damned indexing and the HUP problems haven’t been seen since.
Will try now, and let you know if it worked.
NB – feels pretty lonely here, being the only one to reply to my own replies … 🙄
bye – Marcus
13/09/2008 at 9:14 PM #14625AnonymousInactiveUPDATE:
– renaming the synoindex to synoindex.old was the final cure;
– after a major update from the Synology firmware 0590 to 0637, firefly did not work at all (maybe I messed around with it too much 😉 )
– finally, I reinstalled lately the old firefly/mt-daapd server svn-1696 using the instruction from jchris below. Now the DS-207+ runs on the 0637 firmware flawlessly.
http://forums.fireflymediaserver.org/viewtopic.php?t=7793&postdays=0&postorder=asc&start=0Good luck to you all!
Marcus
-
AuthorPosts
- The forum ‘Setup Issues’ is closed to new topics and replies.