You are here: Home » Topic » Problem with Pinnacle Soundbridge when reconnecting

Problem with Pinnacle Soundbridge when reconnecting

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server Nightlies Feedback Problem with Pinnacle Soundbridge when reconnecting

This topic contains 6 replies, has 3 voices, and was last updated by  kreutzman 10 years, 11 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #725

    kreutzman
    Participant

    Hello,

    sorry for my bad English, I’m german.

    I have a Claxan NAS with a running Debian Vserver. I installed the Packet “mt-daapd_0.2.4+r1376-1_mipsel.deb”. I use the mDNS avahi-daemon.

    The first time, when I turned on the Soundbridge everything works gerat. But when I turn the Soundbridge in standby-mode and after that again on, the Soundbridge can’t find the mt-daapd-Server.

    In the log-file is nothing to see:

    2006-10-28 17:53:16 (00004000): Starting with debuglevel 2
    2006-10-28 17:53:16 (00004000): Starting rendezvous daemon
    2006-10-28 17:53:16 (00004000): Starting signal handler
    2006-10-28 17:53:16 (00004002): Signal handler started
    2006-10-28 17:53:17 (00004000): Initializing database
    2006-10-28 17:53:35 (00004000): Starting web server from /usr/share/mt-daapd/adm
    in-root on port 3689
    2006-10-28 17:53:35 (00004000): Registering rendezvous names
    2006-10-28 17:53:35 (00004000): Serving 10036 songs. Startup complete in 19 sec
    onds
    2006-10-28 17:56:56 (00038004): Session 0: Streaming file '01 - Bap - Wie, Wo U
    n Wann_.mp3' to 192.168.0.54 (offset 0)
    2006-10-28 17:57:12 (00040005): Session 0: Streaming file '02 - Bap - Jedenfall
    s Vermess.mp3' to 192.168.0.54 (offset 0)
    2006-10-28 17:58:08 (00048004): Session 0: Streaming file '03 - Bap - Roevver N
    oh Tanger.mp3' to 192.168.0.54 (offset 0)
    2006-10-28 17:58:11 (00050005): Session 0: Streaming file '04 - Bap - Fuer Mari
    a.mp3' to 192.168.0.54 (offset 0)
    2006-10-28 17:58:14 (00058004): Session 0: Streaming file '05 - Bap - Ich Wuens
    ch Mir, Du Woehrs He.mp3' to 192.168.0.54 (offset 0)
    2006-10-28 18:01:43 (00078004): Session 0: Streaming file '06 - Bap - Wann Imme
    r Du Nit Wiggerweis.mp3' to 192.168.0.54 (offset 0)

    During playing the last song, I turned off the SB. When I turned on the SB again, nothing is logged.

    Only a restarting of mt-daapd made possible a connection of the Soundbridge. But only one time…

    #7041

    fizze
    Participant

    @all:

    try to use a more recent version of mt-daapd. 0.2.4 is considered (ancient) 😉
    http://nightlies.mt-daapd.org
    ron promised debian packages to be present shortly.
    what firmware is your soundbridge? roku or pinnacle?
    did you try to reboot the soundbridge? did you try any other clients?
    you might also try firefly on your PC, to see if you have the same issues.

    @ kreutzmann:

    moinmoin.
    Hol dir mal neuere nightlies auf http://nightlies.mt-daapd.org, debian pakete sollten bald folgen.
    Ansonsten hast andere clients probiert? Hast die Soundbridge neu gestartet?
    Isses ne roku oder pinnacle soundbridge?

    probier mal firefly/mt-daapd auf deinem PC, nur so als vergleich, wenn alles nix hilft. 😉

    #7042

    rpedde
    Participant

    @fizze wrote:

    try to use a more recent version of mt-daapd. 0.2.4 is considered (ancient) 😉

    I think 0.2.4+r1376 is the official debian “etch” package.

    what firmware is your soundbridge? roku or pinnacle?
    did you try to reboot the soundbridge? did you try any other clients?
    you might also try firefly on your PC, to see if you have the same issues.

    All good questions.

    Also sounds suspiciously like a firewall issue on the NAS box.

    #7043

    kreutzman
    Participant

    @fizze wrote:

    what firmware is your soundbridge?

    My SB say it’s the newest.

    roku or pinnacle?

    Pinnacle (see Threadheader 😀 )

    did you try to reboot the soundbridge?

    Oh yes, I did! But nothing is better

    did you try any other clients?

    No, I didnt. Wich client is good for trying?

    you might also try firefly on your PC, to see if you have the same issues.

    Yes, I’ll do that and post the result

    @rpedde wrote:

    Also sounds suspiciously like a firewall issue on the NAS box.

    No, there isn’t any firewall! It works fine, but only one time.

    #7044

    rpedde
    Participant

    @kreutzman wrote:

    @fizze wrote:

    what firmware is your soundbridge?

    My SB say it’s the newest.

    Newest, or newest beta? What version is it? 2.5.174?

    did you try any other clients?

    No, I didnt. Wich client is good for trying?

    iTunes is a good place to start. See if it shows up as a shared library in iTunes. That will give a good data point.

    No, there isn’t any firewall! It works fine, but only one time.

    If you stop and start the mt-daapd server, does it appear on the soundbridge? If so, that’s a sure sign that the server isn’t getting mdns queries. You would see them on the local interface to 224.0.0.251 on port 5353 udp.

    When you say that there isn’t a firewall, do you mean that there literally is no firewall, or that your firewall is set up to allow all connections from your local network? Because lots of times when you think there is no firewall, multicast addresses like 224.0.0.0/4 are still firewalled as martians (incorrectly, obviously).

    I’d double check to make sure you literally have no iptables rules laying around and default accepts.

    —-

    Ack… wait. I just re-read that. vserver has well known problems with multicast, that’s probably what you are running into. On the host box, is it possible you could run mdns on *that*, instead of in the vserver? Then you could proxy advertise for the vserver’d host.

    #7045

    fizze
    Participant

    well if you run debian of any flavour, are you sure you dont run any ipchains, or ip whatever /rule based firewalls?

    well since its a pinnacle SB, you might not even have the daap plugin loaded. however, the 1376 in the title is misleading, is that actually N1376 or is it 0.2.4? 🙄

    #7046

    kreutzman
    Participant

    Hello,

    Newest, or newest beta? What version is it? 2.5.174?

    Softwareversion 2.5.171

    Ack… wait. I just re-read that. vserver has well known problems with multicast, that’s probably what you are running into. On the host box, is it possible you could run mdns on *that*, instead of in the vserver? Then you could proxy advertise for the vserver’d host.

    I don’t think that I can compile a howl for my NAS host. And I don’t know how to proxy advertise for the vserver’d host.

    But I tried the new version of mt-daapd (svn-1417). But the mDNS aborted with the following message:

    2006-10-31 18:25:18 (00004000): Starting with debuglevel 2
    2006-10-31 18:25:18 (00004000): Error loading plugin /usr/local/share/mt-daapd/plugins/ssc-script.so: plugin declined to load
    2006-10-31 18:25:18 (00004000): Starting rendezvous daemon
    2006-10-31 18:25:18 (00004000): mDNS Error -65537
    2006-10-31 18:25:18: Aborting
    2006-10-31 18:25:18 (00004000): Starting signal handler
    2006-10-31 18:25:18 (00004002): Signal handler started
    2006-10-31 18:25:19 (00004000): Initializing database
    2006-10-31 18:25:35 (00004000): Starting web server from /usr/local/share/mt-daapd/admin-root on port 3689
    2006-10-31 18:25:35 (00004000): Registering rendezvous names
    2006-10-31 18:25:35 (00004000): Serving 10036 songs. Startup complete in 17 seconds

    I think that is a problem of the vservers “virtual interface”.

    Now, I’ll trying to copy the binary to the vservers host. Perhabs it may working…
    —-
    Edit:
    Don’t work

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.