mt-daapd : ogg tagn: 8 Starting signal handler ogg tags

@conreyt wrote:

I’m not sure really where to begin. I’ve installed mt-daapd on my debian server. I can see the share on my ubuntu notebook running banshee-daap. My question is this. When I look at my mp3s that I’ve got shared, I see all the id3tag data, however I’m not seeing it with any of my oggs. The only thing that shows up is the filename. They play fine, however I can’t sort by artist / album /genre. I’ve verified that the tag info on my oggs is correct. Any thoughts?

You’ll need to have nightlies rather than stable, and you’ll have to build it with –enable-oggvorbis in order to see ogg metadata.

I think svn-1379 is in debian unstable. You might be able to use the packaging info for that to backport to your platform.

@conreyt wrote:

@rpedde wrote:

@conreyt wrote:

I’m not sure really where to begin. I’ve installed mt-daapd on my debian server. I can see the share on my ubuntu notebook running banshee-daap. My question is this. When I look at my mp3s that I’ve got shared, I see all the id3tag data, however I’m not seeing it with any of my oggs. The only thing that shows up is the filename. They play fine, however I can’t sort by artist / album /genre. I’ve verified that the tag info on my oggs is correct. Any thoughts?

You’ll need to have nightlies rather than stable, and you’ll have to build it with –enable-oggvorbis in order to see ogg metadata.

I think svn-1379 is in debian unstable. You might be able to use the packaging info for that to backport to your platform.

Will do thanks.

If you hit a stumbling block, let me know. If you are feeling gutsy, I have an x86 sarge package that just came out of the latest build. I haven’t tested it. Might not work at all…

it’s here if you are interested in crash-testing it. And I really do mean crash-testing. It might not work at all. Might just make fire shoot out of the back of your box. I literally have not installed it on an actual x86 debian machine.

…. but if you tested it and it seemed to work, then it would be easier for me to go ahead and start dumping debian packages as part of my regular nightly builds.

Think of all the good karma… 🙂

— Ron

@conreyt wrote:

I’ve gone ahead and installed the .deb linked above. output from /var/log/mt-daapd.log

2006-10-24 17:49:27 (a7da8aa0): Starting with debuglevel 2
2006-10-24 17:49:27 (a7da8aa0): Starting rendezvous daemon
2006-10-24 17:49:27 (a7da8aa0): Starting signal handler
2006-10-24 17:49:27 (a7d5ebb0): Signal handler started
2006-10-24 17:49:28 (a7da8aa0): db_sqlite2_open: unable to open database: /var/cache/mt-daapd/songs.db (/var/cache/mt-daapd/songs.db)
2006-10-24 17:49:28 (a7da8aa0): Error opening db: Misc SQL Error: unable to open database: /var/cache/mt-daapd/songs.db
2006-10-24 17:49:28 (a7da8aa0): Stopping signal handler
2006-10-24 17:49:28 (a7d5ebb0): Got shutdown signal. Notifying daap server.

I’ve gone back and verified that the /var/cache/mt-daapd dir is empty.

Looks the same on sarge and etch. (thought I’d break out my other server to check as well)

Make that directory writable by the runas user (nobody).

I’ll fix that on the package.

— Ron

@conreyt wrote:

Make that directory writable by the runas user (nobody).
I’ll fix that on the package.
— Ron

I did a dpkg –purge mt-daapd, set nobody as dir owner, (rwxr-xr-x) and reinstalled (dpkg -i mt-daa*.deb) and the db still didn’t show up. I went ahead and set the dir 777 uninstalled and reinstalled. still no love.

Theron

kk. thanks. I’ll see what else I can figure on that. (did I forget to configure a database backend?)

Hrm.

— Ron

@conreyt wrote:

The current stable .deb release on sourceforge dosen’t designate the database type (in the mt-daapd.conf) however it creates a /var/cache/mt-daap/songs.gdb I noticed that your package is designating sqlite3. What are they using in the stable package?

the old deb used gdbm, which isn’t supported any more.

Ready for a new .deb 🙂

Okay. http://www.mt-daapd.org/mt-daapd_0.9-svn-1412_i386.deb. You’ll want to “apt-get remove –purge mt-daapd”, along with a “rm -rf /var/cache/mt-daapd” for good measure.

a dpkg -i, followed by “/etc/init.d/mt-daapd start” ought to fire right up.

— Ron