FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › Anyone have a Kurobox step by step?
- This topic has 14 replies, 3 voices, and was last updated 17 years, 10 months ago by Digital Larry.
-
AuthorPosts
-
18/01/2007 at 6:23 PM #8104Digital LarryParticipant
Was gonna put up a screenshot but don’t have handy hosting service available. Anyway what it says is:
========================================
ConfigurationNote that the following fields will only be editable if the configuration file itself is writable by the mt-daapd server. If you make changes to these settings, they will not be reflected in the running server. The server must be restarted for these values to take effect.
========================================
So I cannot change any of the settings in this screen is what I meant.Anyway I need to get more current on the server, then let’s proceed.
Thx so much.
DL
18/01/2007 at 8:39 PM #8105CCRDudeParticipantYeah, you should definitively get a newer version π
Take a look at nightlies.mt-daapd.org, the version ending in …powerpc.deb should be the right one (powerpc for the processor thats in the Kurobox, deb for standard debian package).Not sure how the old one was made part of that image, you may be able to use aptitude remove mt-daapd to remove the old one, then install the new one (aptitude install mt-daapd_0.9-svn-1489_sarge_powerpc.deb). I’m not quite sure about those two commands from memory though π
An alternative would be to download the tar.gz package, then do in its folder:
tar -xzvf mt-daapd-svn-1489.tar.gz
cd mt-daapd-svn-1489
./configure --enable-oggvorbis --enable-flac --enable-musepack --enable-sqlite3
make
make installThe parameters behind configure are my preferences, not necessary if you don’t have oggs, flacs or musepack audio files, or are satisfied with whatever the default database is π
To the problem you have though, you can fix that even with the old version, just do a
chmod +w /etc/mt-daapd.conf
Would probably be better to give only the user that runs mt-daapd write access, but I don’t know which one that is in the Sylver version π
Finally, about screenshots: ImageShack does that for free, I use a plugin named ImageBot for Firefox, which is able to upload any image from the clipboard to ImageShack, and give you the links needed to post that on forums etc.
22/01/2007 at 6:20 AM #8106Digital LarryParticipantOK, well I had to take out flac support, and used sqlite instead of sqlite3, and ran these commands you gave me, and a whole bunch of stuff happened…
So how do I know if it worked or not?
PS my existing mt-daapd was running at the time, I did shut it down, but of course now it’s shut down and nobody home at port 3689.
Rebooted box, and… it’s gone. Old one isn’t working any more.
ps -aux shows no mt-daapd processes.
README indicates need for distro-specific startup scripts.
I tried running “mt-daapd start” in /etc/init.d, but nothing happened. No console feedback nor any mt-daapd processes showing up.
Here’s what’s in the log:
2007-01-22 08:08:03 (00000400): Firefly Version svn-1489: Starting with debuglevel 2
2007-01-22 08:08:03 (00000400): Starting rendezvous daemon
2007-01-22 08:08:03 (00000400): Starting signal handler
2007-01-22 08:08:03 (00000400): Old database version: 6, expecting 13
2007-01-22 08:08:03 (00000400): Upgrading db: 6 –> 7
2007-01-22 08:08:03 (00000400): Upgrading db: 7 –> 8
2007-01-22 08:08:03 (00000400): Query: create index idx_songid on playlistitems(songid)
create index idx_playlistid on playlistitems(playlistid)
update config set value=8 where term=’version’;2007-01-22 08:08:03 (00000400): Error: near “create”: syntax error
2007-01-22 08:08:03 (00000400): Error upgrading db: Misc SQL Error: near “create”: syntax error
2007-01-22 08:08:03 (00000400): Error opening db: Misc SQL Error: near “create”: syntax error(which is at least something)
Any clue?
23/01/2007 at 9:13 AM #8107CCRDudeParticipantNo answer yet? Damn π
Well, yesterday I wasn’t too sure since this looked like a problem with converting an old database format to a new one, and I have no real insight into that…
But this morning I remembered that you have nothing important in the database yet, right? No special playlists etc., so: just delete the playlist file! It’s probably at /var/cache/mt-daapd/songs.db . If you delete that, Firefly can create a fresh new database instead of trying to do half a dozen update steps to get from the old format to the new one.23/01/2007 at 10:25 PM #8108Digital LarryParticipantI did get an answer, but I’ve adopted a new strategy of starting a new thread when the topic changes enough from the original! So it’s off somewhere else.
Apparently deleting the old songs.db will force the creation of a new one. Also I had the ancient mt-daapd.conf file still around and just need to go thru the steps of getting that right. I’ll probably have time for that in a few days.
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.