FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › FIREFLY MEDIA SERVER KEEPS ON CRASHING DOWN
- This topic has 11 replies, 6 voices, and was last updated 16 years, 11 months ago by Anonymous.
-
AuthorPosts
-
20/12/2007 at 12:27 PM #2048AnonymousInactive
I am a proud user of a Roku Soudbridge for more than 3 months and I was always using it with the Firefly media server.
My computer runs on Windows XP
In the last week, I uploaded about 50 new cds up my drive, as always, with I-Tunes.
Now, the Firefly media server keeps on crashing down every time it starts to scan my external hd drive, where I keep my music.
I unistalled Firefly and installed it again. No result. I installed a nightly version but it won’t work on my pc. Now I installed the common version again. No result.
This is the latest log:
Log file: firefly.log
2007-12-20 13:09:11 (a8ca92bd): Starting with debuglevel 0
2007-12-20 13:09:12 (a8ca92bd): Starting rendezvous daemon
2007-12-20 13:09:12 (a8ca92bd): Initializing database
2007-12-20 13:09:12 (a8ca92bd): Full reload…
2007-12-20 13:09:12 (a8ca92bd): Starting mp3 scan
2007-12-20 13:09:23 (a8ca92bd): Error scanning MP3 files: The storage control block address is invalid.2007-12-20 13:09:23 (a8ca92bd): Starting web server from C:Program FilesFirefly Media Serveradmin-root on port 9999
2007-12-20 13:09:24 (a8ca92bd): Registering rendezvous names
2007-12-20 13:09:24 (a8ca92bd): Serving 708 songs. Startup complete in 12 seconds
2007-12-20 13:09:24 (a8ca92bd): Stopping gracefully
2007-12-20 13:09:24 (a8ca92bd): Stopping rendezvous daemon
2007-12-20 13:09:24 (a8ca92bd): Closing database
2007-12-20 13:09:24 (a8ca92bd): Done!Firefly Service 1.0 svn-1359 C:Program FilesFirefly Media Serverfirefly.exe
FireflyShell 1.0 svn-1359 C:Program FilesFirefly Media ServerFireflyShell.exe
RSP Output Plugin 1.0 svn-1359 C:Program FilesFirefly Media Serverpluginsrsp.dll
FFMPEG Transcoder Plugin 1.0 svn-1359 C:Program FilesFirefly Media Serverpluginsssc-ffmpeg.dll
WMA Transcoder Plugin 1.0 svn-1359 C:Program FilesFirefly Media Serverpluginsssc-wma.dll
Win32 Event Plugin 1.0 svn-1359 C:Program FilesFirefly Media Serverpluginsw32-event.dllPlease Help!
Thank
Tomaz20/12/2007 at 12:36 PM #15284sonichouseParticipantIt sounds as if your external disk may have a corruption.
From windows can you do a disk check on it ?
See http://support.microsoft.com/kb/315265 for details how to do it from explorer.
20/12/2007 at 1:17 PM #15285AnonymousInactiveok, i’m running a disk check and I let you know what happened.
but why wouldn’t the nightly version work?
greetings
tomaz20/12/2007 at 3:15 PM #15286EVILRipperParticipantHeh, ouch. Sounds familiar. My external HD recently died. This sounds like it is starting to give errors. If I was you, I’d backup your HD ASAP!
As you can see the log dies at a certain point. It does scan 708 songs. So this really does look like a dying harddisk…
20/12/2007 at 8:03 PM #15287AnonymousInactiveHMM, still a mystery, made all possible disc checks, from my computer and the command prompt. always the same result: WINDOWS FOUND NO PROBLEMS IN THE FILE SYSTEM (which is only 3 months old)
What now?
By the way, with I-tunes, the HD makes no problems, only firefly keeps crashing.
21/12/2007 at 3:27 AM #15288stretchParticipantDoes it crash on the same song every time?
If yes then that particular file may be corrupted in a way that causes Firefly to crash.
In this case all you have to do is fix the offending track. Often it’s just the ID tag that’s got corrupted data in it.21/12/2007 at 5:14 AM #15289rpeddeParticipant@stretch wrote:
Does it crash on the same song every time?
If yes then that particular file may be corrupted in a way that causes Firefly to crash.
In this case all you have to do is fix the offending track. Often it’s just the ID tag that’s got corrupted data in it.Best way to do that is to go into the advanced config option from start->program files->firefly media server and change the debuglevel to 5. Then start the server. When it crashes, look at the “log” tab on the tray icon and see what the last file it scanned was. Move that file out of he way and try again.
— Ron
21/12/2007 at 9:05 AM #15290AnonymousInactivethanks, i’ll do that.
21/12/2007 at 9:22 AM #15291AnonymousInactivePROBLEM HOW DO I CHANGE THE DEBUG LEVEL, WHERE DO I ENTER IT?
logfile (optional)
#
# This is the file to log to. If this is not configured,
# then it will log to the syslog.
#
# Not that the -d switch will control the log verbosity.
# By default, it runs at log level 1. Log level 9 will churn
# out scads of useless debugging information. Values in between
# will vary the amount of logging you get.
##logfile /var/log/mt-daapd.log
21/12/2007 at 9:38 AM #15292sonichouseParticipantYou need to add
debuglevel = 5
and set logfile /some/path/firefly.log.
I do not run on windows, but try
logfile = C:/temp/firefly.log
or another directory you want.
/Steve
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.