You are here: Home » Topic » malformed database

malformed database

This topic contains 2 replies, has 2 voices, and was last updated by  Anonymous 8 years, 10 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #2819

    Anonymous

    I had been successfully running Firefly on my computer (Windows XP pro)for months, with Firefly looking to my iTunes library. About a week ago, I stopped seeing it on my Roku, and realized that the server was not running. I get the following string of messages in the log:

    Log file: firefly.log

    2008-12-12 15:29:54 (702193b1): Firefly Version svn-1586: Starting with debuglevel 2
    2008-12-12 15:29:54 (702193b1): Plugin loaded: w32-event/svn-1586
    2008-12-12 15:29:54 (702193b1): Plugin loaded: ssc-wma/svn-1586
    2008-12-12 15:29:54 (702193b1): Plugin loaded: ssc-ffmpeg/svn-1586
    2008-12-12 15:29:54 (702193b1): Plugin loaded: rsp/svn-1586
    2008-12-12 15:29:54 (702193b1): Plugin loaded: daap/svn-1586
    2008-12-12 15:29:54 (702193b1): Starting rendezvous daemon
    2008-12-12 15:29:54 (702193b1): Building drive mapping table from C:Program FilesFirefly Media Servermapping.ini
    2008-12-12 15:29:54 (702193b1): Error: enum_begin failed (error 1): Misc SQL Error: database disk image is malformed
    2008-12-12 15:29:54 (702193b1): Can’t get db version. New database?
    2008-12-12 15:29:54 (702193b1): Initializing database
    2008-12-12 15:29:54 (702193b1): Error: enum_begin failed (error 1): ?
    2008-12-12 15:29:54 (702193b1): Error: enum_begin failed (error 1): ?
    2008-12-12 15:29:54 (702193b1): Full reload…
    2008-12-12 15:29:54 (702193b1): Starting web server from C:Program FilesFirefly Media Serveradmin-root on port 9999
    2008-12-12 15:29:54 (702193b1): Registering rendezvous names
    2008-12-12 15:29:54 (702193b1): Error: enum_begin failed (error 1): Misc SQL Error: database disk image is malformed
    2008-12-12 15:29:54 (702193b1): Error getting song count: Misc SQL Error: database disk image is malformed
    2008-12-12 15:29:54: Aborting

    Any ideas as to what might be going on and how to fix it? Thanks for your help.

    #18263

    stretch
    Participant

    delete the database file and restart. The file name will be either songs.db or songs3.db

    If it still crashes, increase error logging to level 9 for more information about what’s causing the crash.

    #18264

    Anonymous

    That worked perfectly! Thanks for your help.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.