svn-1696 on NSLU2 crashes when I have it start a scan

FireFly Media Server Firefly Media Server Forums Firefly Media Server Nightlies Feedback svn-1696 on NSLU2 crashes when I have it start a scan

Viewing 8 posts - 11 through 18 (of 18 total)
  • Author
    Posts
  • #14357
    dovad
    Participant

    I’m running a Linkstation LS1 PPC with Freelink and svn-1696. Every time I run a scan Firefly crashes. I stopped auto-scanning for this reason. Is there a work- around until time allows for a fix? Is it possible and sensible to delete the database and have a new one created when rebooting?

    #14358
    fizze
    Participant

    svn-1696 is horribly with sqlite2.
    I just migrated to sqlite3, which seems stabler. At least it scans, plus its faster than sqlite2.

    Here’s how to change to sqlite3 yourself:

    sqlite /path/to/songs.db .dump | sqlite3 /path/to/songs3.db 

    Make sure mt-daapd is stopped, albeit.

    Then change the db_type in mt-daapd.conf to sqlite3, and fire up mt-daapd.

    That’s it – on an unslung NSLU2 at least. 🙂

    #14359
    dovad
    Participant

    OK, I tried this but now Firefly will not start. The error log is as follows:

    2007-12-02 09:48:18 (3001f380): Firefly Version svn-1696: Starting with debuglevel 2
    2007-12-02 09:48:18 (3001f380): Plugin loaded: ssc-script/svn-1696
    2007-12-02 09:48:18 (3001f380): Plugin loaded: rsp/svn-1696
    2007-12-02 09:48:18 (3001f380): Plugin loaded: daap/svn-1696
    2007-12-02 09:48:18 (3001f380): Starting rendezvous daemon
    2007-12-02 09:48:18 (3001f380): Starting signal handler
    2007-12-02 09:48:18 (3001f380): Error opening db: No backend database support for type: sqlite3

    Note that I tried switching to Sqlite3 via the web interface a couple of days ago and could not start Firefly so this time I assumed that I did not have sqlite3 installed and had to:

    “apt-get install sqlite3” before I followed your instructions and did the install of sqlite3 first. I assume that I have to install something else because of the “Error opening db: No backend database support for type: sqlite3”? I did modify the config file specifying sqlite3 as the default database after your instructions but before trying to start Firefly.

    #14360
    fizze
    Participant

    You probably forgot to do

    ldconfig

    So the sqlite3 libs are not known to the rest of the system 😉

    If you sure you did, do a “which -a sqlite sqlite3” and see if the sqlite3 binary is present.

    #14361
    rpedde
    Participant

    @dovad wrote:

    OK, I tried this but now Firefly will not start. The error log is as follows:

    2007-12-02 09:48:18 (3001f380): Firefly Version svn-1696: Starting with debuglevel 2
    2007-12-02 09:48:18 (3001f380): Plugin loaded: ssc-script/svn-1696
    2007-12-02 09:48:18 (3001f380): Plugin loaded: rsp/svn-1696
    2007-12-02 09:48:18 (3001f380): Plugin loaded: daap/svn-1696
    2007-12-02 09:48:18 (3001f380): Starting rendezvous daemon
    2007-12-02 09:48:18 (3001f380): Starting signal handler
    2007-12-02 09:48:18 (3001f380): Error opening db: No backend database support for type: sqlite3

    Note that I tried switching to Sqlite3 via the web interface a couple of days ago and could not start Firefly so this time I assumed that I did not have sqlite3 installed and had to:

    “apt-get install sqlite3” before I followed your instructions and did the install of sqlite3 first. I assume that I have to install something else because of the “Error opening db: No backend database support for type: sqlite3”? I did modify the config file specifying sqlite3 as the default database after your instructions but before trying to start Firefly.

    That would mean that your version isn’t compiled with sqlite3. Where did you get the package?

    I hope not from, me, I thought I was compiling all mine with both. eek!

    — Ron

    #14362
    dovad
    Participant

    Ron,
    I got it from a “wget” link on nas-central.org. I also installed the package from instructions on a wiki on nas-central.

    I don’t mind reinstalling the whole mess however I’m an amateur at Linux/UNIX and could use some guidance.

    Dave

    #14363
    rpedde
    Participant

    @dovad wrote:

    Ron,
    I got it from a “wget” link on nas-central.org. I also installed the package from instructions on a wiki on nas-central.

    I don’t mind reinstalling the whole mess however I’m an amateur at Linux/UNIX and could use some guidance.

    Dave

    I think I don’t have a ppc ipkg build. I think that even the sqlite3 thing isn’t the real fix though — I think turning off background rescans is it, and manually rescanning when adding music (while *not* listening to music!)

    — Ron

    #14364
    dovad
    Participant

    Ron,

    As per your suggestion I rolled back to version “svn-1586”. The LinkStation is now working perfectly. I can even do an aggressive file scan while playing music and it literally doesn’t miss a beat!

    Perhaps (and this is totally guesswork on my part) the upgraded kernel helps as well with the scanning while playing music. My LinkStation is a PPC version LS1. I have Freelink 1.1 with the 2.6.23.9 kernel upgrade.

    Thanks….
    Dave

Viewing 8 posts - 11 through 18 (of 18 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.