Basic: Fail to connect to mt-daapd server on OpenBSD 4.0

FireFly Media Server Firefly Media Server Forums Firefly Media Server Setup Issues Basic: Fail to connect to mt-daapd server on OpenBSD 4.0

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #965
    peter_ljung
    Participant

    The administrative UI works fine but the logfile indicates that I have some kind of problem. Rendezvous servers seems to fail to start which could explain why I can’t see the server.

    2007-01-06 19:58:14: Starting rendezvous daemon
    2007-01-06 19:58:14: mDNS Error -65537
    2007-01-06 19:58:14: Aborting
    2007-01-06 19:58:14: Starting signal handler
    2007-01-06 19:58:14: Loading playlists
    2007-01-06 19:58:14: Initializing database
    2007-01-06 19:58:14: Starting mp3 scan
    2007-01-06 19:58:14: Starting web server from /usr/local/share/mt-daapd/admin-root on port 3689
    2007-01-06 19:58:14: Registering rendezvous names
    2007-01-06 19:58:14: Scanned 13 songs in 0 seconds

    Setup:
    OS: OpenBSD 4.0
    package: mt-daapd-0.2.4

    Can this problem be fixed?

    Regards / Peter

    #8268
    rpedde
    Participant

    @peter_ljung wrote:

    The administrative UI works fine but the logfile indicates that I have some kind of problem. Rendezvous servers seems to fail to start which could explain why I can’t see the server.

    2007-01-06 19:58:14: Starting rendezvous daemon
    2007-01-06 19:58:14: mDNS Error -65537
    2007-01-06 19:58:14: Aborting
    2007-01-06 19:58:14: Starting signal handler
    2007-01-06 19:58:14: Loading playlists
    2007-01-06 19:58:14: Initializing database
    2007-01-06 19:58:14: Starting mp3 scan
    2007-01-06 19:58:14: Starting web server from /usr/local/share/mt-daapd/admin-root on port 3689
    2007-01-06 19:58:14: Registering rendezvous names
    2007-01-06 19:58:14: Scanned 13 songs in 0 seconds

    Setup:
    OS: OpenBSD 4.0
    package: mt-daapd-0.2.4

    Can this problem be fixed?

    Regards / Peter

    You can run it with “-m”, to turn off the rendezvous server, and use howl or avahi or another rendezvous daemon. You can use the configuration files of either of those daemons to always advertise mdns for mt-daapd, or let the server advertise and un-advertise when it starts and stops by using the “–enable-howl” configuration option, or the –enable-avahi (only on latest nightlies: http://nightlies.mt-daapd.org).

    — Ron

    #8269
    peter_ljung
    Participant

    Thanks for your quick reply. I didn’t know how Howl worked so it took me some time to set it up. I wrote a short description (mostly for personal use) but if anyone have the same problem on OpenBSD the description might be of some use.

    Install mt-daapd on OpenBSD

    Install mt-daapd package and “zeroconf”:http://www.zeroconf.org/ server Howl. Howl is not supported anymore, but it works fine for me and there is a ready to use OpenBSD package for it.


    pkg_add /mt-daapd-0.2.4
    pkg_add
    /howl-1.0.0p0

    Create a configuration file for Howl. The name of the Howl service is mDNSResponder so we create a /etc/mDNSResponder.conf file where the mt-daapd deamon is advertized.


    "Music Jukebox" _daap._tcp. local. 3689

    Edit mt-daapd configuration file _/etc/mt-daapd.conf_ with your specific installation parameters e.g. music library location.

    Start up mt-daapd and mDNSResponder. Add the lines to /etc/rc.local if you want them to be started at boot.


    mt-daapd -m
    mDNSResponder -f /etc/mDNSResponder.conf

    mt-daapd actually includes a zeroconf implementation (“Bonjour”:http://developer.apple.com/networking/bonjour/index.html) but currently there is a problem with it in OpenBSD. Check the logfile _/var/log/mt-daapd.log_ to see how it works in your version. If the internal mDNS server works you don’t have to use Howl.
    The -m option turns off the internal mDNS server in favour of Howl.

    Regards / Peter

Viewing 3 posts - 1 through 3 (of 3 total)
  • The forum ‘Setup Issues’ is closed to new topics and replies.