Hi, Until this morning i had a nicely functioning firefly setup on an nslu2.
I decided to upgrade to the lastest nightly and now i am having problems with firefly crashing. At first i thought it was a bad music file crashing the system but after i increased the log level to 6 i couldnt find any specific file mentioned.

Below is the log i get with the tail -100 /var/log/messages command after a system restart and an attemted manual restart of firefly.

edit: I have tried this command and there seems to be not ipkg package for sqlite3

can anyone give me a clue to the easiest way to install sqlite3 on a nslu2?

I think you need to do “ipkg install sqlite2”, plus change your mt-daapd.conf file to say “db_type = sqlite3” and everything works, at least for me.

I don’t know why 2=3 🙂

rsl

actually, it’s “sqlite”. on the nslu2, sqlite is sqlite3, sqlite2 is sqlite2. Were it me, I would have made “sqlite” sqlite2, and sqlite3 sqlite3, but that’s me… someone had already checked in a 3 package as sqlite when I added sqlite2.

actually, it’s “sqlite”. on the nslu2, sqlite is sqlite3, sqlite2 is sqlite2. Were it me, I would have made “sqlite” sqlite2,
and sqlite3 sqlite3, but that’s me… someone had already checked in a 3 package as sqlite when I added sqlite2.

— Ron

sheesh, and people wonder why the public has trouble with computers……

It gets more interesting. There appear to be _two_ packages with the name “sqlite” on the ipkg system (for the NSLU2).
Both appear to be version 3, but different builds. (and I should have realized the version number was in the description…..)
This seems bogus to me.
With my NSLU2 I see:

Which version of three did you put up? Or more to the point, which one should we be using, and is it the one I’m running?
I cannot say how I got my particular versions of sqlite, as at this point I don’t recall if I loaded sqlite myself,
if it’s part of the basic package, or if it loaded autmagically as part of mt-daapd install.

actually, it’s “sqlite”. on the nslu2, sqlite is sqlite3, sqlite2 is sqlite2. Were it me, I would have made “sqlite” sqlite2,
and sqlite3 sqlite3, but that’s me… someone had already checked in a 3 package as sqlite when I added sqlite2.

— Ron

sheesh, and people wonder why the public has trouble with computers……

It gets more interesting. There appear to be _two_ packages with the name “sqlite” on the ipkg system (for the NSLU2).
Both appear to be version 3, but different builds. (and I should have realized the version number was in the description…..)
This seems bogus to me.
With my NSLU2 I see:

Which version of three did you put up? Or more to the point, which one should we be using, and is it the one I’m running?
I cannot say how I got my particular versions of sqlite, as at this point I don’t recall if I loaded sqlite myself,
if it’s part of the basic package, or if it loaded autmagically as part of mt-daapd install.

Anything I should try?

rsl[/quote

Hrm… I’d say whatever one comes down should be okay, but it might be that it won’t link to 3.5. I guess stick with 2. It works okay, so long as you turn off background rescans (scan_interval = 0).