FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › daap service not correctly published
- This topic has 2 replies, 1 voice, and was last updated 15 years, 8 months ago by Anonymous.
-
AuthorPosts
-
26/08/2008 at 8:16 PM #2612AnonymousInactive
I installed mt-daapd svn-1696 on a Debian Linux server (this computer has no desktop enviroment, I access it via ssh). Then, on my notebook (with Ubuntu Linux 8.04) I go to the web interface of Firefly and I see this:
http://img528.imageshack.us/img528/4996/fireflymediaserver12197os4.png
But on Rhytmbox or Banshee I can’t see the media server. I launched avahi-browse and no _daap._tcp service is detected at all:
tm8204:~$ avahi-browse -a
+ eth0 IPv4 media [00:18:51:xx:xx:xx] Workstation local
+ eth0 IPv4 tm8204 [00:16:36:xx:xx:xx] Workstation local
On the server, the service is detected:
media:~$ avahi-browse -a
+ eth0 IPv6 tm8204 [00:16:36:xx:xx:xx] Workstation local
+ eth0 IPv4 media [00:18:51:xx:xx:xx] Workstation local
+ eth0 IPv4 Firefly svn-1696 on media iTunes Audio Access local
+ eth0 IPv4 Firefly svn-1696 on media _rsp._tcp local
+ eth0 IPv4 Firefly svn-1696 on media Web Site local
But… if I manually publish a service from the server
media:~$ avahi-publish -s Test _daap._tcp 1234
Established under name 'Test'
on my notebook is immediately detected:
tm8204:~$ avahi-browse -a
+ eth0 IPv4 media [00:18:51:xx:xx:xx] Workstation local
+ eth0 IPv4 tm8204 [00:16:36:xx:xx:xx] Workstation local
+ eth0 IPv4 Test iTunes Audio Access local
Notice that the server and the notebook are on two different subnets, but the router between them is configured as a reflector for mDNS (in fact the manually published service is reflected and detected).
26/08/2008 at 9:04 PM #17656AnonymousInactiveI tried to start mt-daapd from the command line with -f option to run in foreground:
media:~$ sudo mt-daapd -f
Firefly Version svn-1696: Starting with debuglevel 2
Error loading plugin /usr/lib/mt-daapd/plugins/ssc-script.so: plugin declined to load
Plugin loaded: rsp/svn-1696
Plugin loaded: daap/svn-1696
Plugin loaded: ssc-ffmpeg/svn-1696
Starting rendezvous daemon
*** WARNING *** The program 'mt-daapd' uses the HOWL compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see
Starting signal handler
Initializing database
Starting web server from /usr/share/mt-daapd/admin-root on port 3689
Registering rendezvous names
Serving 4499 songs. Startup complete in 1 seconds
Is it normal that Firefly uses the HOWL compatibility layer and not Avahi natively?
26/08/2008 at 10:21 PM #17657AnonymousInactiveRESOLVED! The Debian package was compiled with –enable-howl, so I recompiled it with –enable-avahi instead and this did the trick.
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.