You are here: Home » Topic » Pinnacle Soundbridge – MSS installation problems

Pinnacle Soundbridge – MSS installation problems

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server General Discussion Pinnacle Soundbridge – MSS installation problems

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #1068
    rojbalc
    Participant

    Hi there,

    I am about to follow the Wiki for Firefly installation on MSS+ (as soon as http://www.openmss.org is up and running again so I can get the Firmware 🙁 ). I’ve had a brief look at the walkthrough and was wondering about the version of Firefly that is telnetted over and installed on the MSS – I’m running a Pinnacle Soundbridge (M1001) and couldn’t get the official Firefly version to work with it on my PC – I’ve got the nightly version 1376 running…

    So, will my Pinnacle still work with the Firefly version from the Wiki on my MSS+, or will I have the same problems I had on my PC? Should I telnet a nightly over instead? If so, how (I’m no Linux programmer…)?

    I thought I’d ask first before finding out later that I’d installed the wrong version on the MSS+ and had to go about uninstalling it etc…

    Thanks in advance for the help,
    roj.

    #8971
    rojbalc
    Participant

    OK, I couldn’t wait any longer and went ahead with the walkthrough…

    Firefly now appears to be working on the mss, and I just need to tell it where to look for my music. The only problem is, I can’t access the http://[mss]:3689 web interface config page – I get a ‘page not found’ message. I don’t really know why – even with my firewall turned off I have the problem…

    Anyone have any ideas?

    The only thing that occurs to me is that in the Wiki, it say you can delete 4 lines of the file that controls bonjour advertising and that you should “Find the group of lines mentioning “_tcp._daap” and delete them using the CTRL-K key. ” In the file, “_tcp._daap” wasn’t actually mentioned, but “_daap._tcp” was. The last 4 lines looked something like this:

    MSS-018AB9 Music Server
    _daap._tcp
    none
    [some number I don’t remember]

    I presumed these were the lines that were meant and that it was just a typo in the Wiki so I deleted these. Could this be the problem – have I deleted the wrong thing?

    As you can see, I don’t have much of a clue. Any help appreciated!

    Thanks,
    roj.

    #8972
    rpedde
    Participant

    @rojbalc wrote:

    The only thing that occurs to me is that in the Wiki, it say you can delete 4 lines of the file that controls bonjour advertising and that you should “Find the group of lines mentioning “_tcp._daap” and delete them using the CTRL-K key. ” In the file, “_tcp._daap” wasn’t actually mentioned, but “_daap._tcp” was.

    Oops! Typo. Fixed it in the wiki.

    With regard to not being able to get to the web page, that sounds like the server didn’t start for some reason. Do you get any error messages when you start it?

    Try this, while telnetted in:


    # /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf -f

    It should spew out a bunch of junk and then exit. See what the last thing is it said when it exited. That might help track down what its problem is.

    — Ron

    #8973
    rojbalc
    Participant

    OK, next update: I’m still not up and running.

    I still can’t access the web interface http://[mss]:3689, although I suspect that’s because I still have Firefly running on my PC, which uses the same port… Anyway, that isn’t a huge problem, I can deal with that later – in the meantime I’ve edited mt-daapd.conf with this:
    mp3_dir = /Admin1/My Music

    Hope the syntax is right (and that it doesn’t require Server name and allows blanks…)

    I think I may have found the cause of my woes though – I bought my MSS second hand and it looks like the previous owner had Twonky media running on it – my Soundbridge shows not the name I gave my server, but ‘Twonky MSS’ and this guy’s config. So he’s wiped the media files but not the config in the background.

    In any case, the problem seems to be that Twonky is starting on the MSS first or taking priority over mt-daapd, or mt-daapd just isn’t starting at all. And I don’t know why. Yet. Any suggestions?

    Can anyone tell me if I can format the MSS completely and start over again? This may be easiest…

    #8974
    rojbalc
    Participant

    Thanks Ron – not much came out though:

    Firefly Version svn-1498: Starting with debuglevel 2
    SIGSEV

    That’s all…

    #8975
    rpedde
    Participant

    @rojbalc wrote:

    Thanks Ron – not much came out though:

    Firefly Version svn-1498: Starting with debuglevel 2
    SIGSEV

    That’s all…

    Ah. Is it possible you forgot to change the line in /opt/etc/init.d/S60mt-daapd to read like this:

    /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf

    That kind of sounds like it might be it. If that isn’t it, then try this:



    # /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf -f -d9

    to run with a higher debug level.

    — Ron

    #8976
    rojbalc
    Participant

    Ah. Is it possible you forgot to change the line in /opt/etc/init.d/S60mt-daapd to read like this:

    /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf

    Er – no, I did that. However, that line of the file now has ‘sleep 2’ in front of it for some reason. It now reads:


    sleep 2 /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c
    /opt/etc/mt-daapd/mt-daapd.conf

    That can’t be right, can it? I don’t remember it being like that…

    roj.

    #8977
    rpedde
    Participant

    @rojbalc wrote:

    for some reason. It now reads:


    sleep 2 /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c
    /opt/etc/mt-daapd/mt-daapd.conf

    That can’t be right, can it? I don’t remember it being like that…

    roj.

    Nope, should be


    sleep 2
    /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf

    What do you get with the -d9 from the foreground?

    #8978
    rojbalc
    Participant

    Nope, should be


    sleep 2
    /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf

    Right, will sort that.

    What do you get with the -d9 from the foreground?

    This:


    Found 1 Tokens in /AdminMy Music
    Token 1: /Admin/My Music
    Expanding precomments to 2048
    Expanding precomments to 4096
    Found 2 tokens in rsp.so,ssc-script.so
    Token 1: rsp.so
    Token 2: ssc-script.so
    Checking existence of /opt/share/mt-daapd/admin-root
    Checking existence of /opt/share/mt-daapd/admin-root
    Checking existence of /opt/var/mt-daapd
    Checking existence of /opt/var/mt-daapd
    Checking existence of /opt/share/mt-daapd/plugins
    Checking existence of /opt/share/mt-daapd/plugins
    Loading new config file.
    Firefly Version svn-1498: Starting with debuglevel 9
    Attempting to load plugin /shares/mss-hdd/__opt/share/mt-daapd/plugins/out-daap.so
    SIGSEGV
    #8979
    rpedde
    Participant

    @rojbalc wrote:


    Found 1 Tokens in /AdminMy Music
    Token 1: /Admin/My Music
    Expanding precomments to 2048
    Expanding precomments to 4096
    Found 2 tokens in rsp.so,ssc-script.so
    Token 1: rsp.so
    Token 2: ssc-script.so
    Checking existence of /opt/share/mt-daapd/admin-root
    Checking existence of /opt/share/mt-daapd/admin-root
    Checking existence of /opt/var/mt-daapd
    Checking existence of /opt/var/mt-daapd
    Checking existence of /opt/share/mt-daapd/plugins
    Checking existence of /opt/share/mt-daapd/plugins
    Loading new config file.
    Firefly Version svn-1498: Starting with debuglevel 9
    Attempting to load plugin /shares/mss-hdd/__opt/share/mt-daapd/plugins/out-daap.so
    SIGSEGV

    Oh. Yeah. Duh. try:


    # /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf -f -d9

    Sorry. My bad.

    #8980
    rojbalc
    Participant

    @rpedde wrote:


    # /opt/lib/ld.so.1 /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf -f -d9

    Sorry. My bad.

    No probs:


    Probing for MSS Music._http._tcp.local. (SRV) complete
    ServiceCallback: MSS Music._http._tcp.local. (SRV) Name Registered (0)
    Callback: Name Registered
    Probing for MSS Music._rsp._tcp.local. (SRV) complete
    ServiceCallback: MSS Music._rsp._tcp.local. (SRV) Name Registered (0)
    Callback: Name Registered
    Probing for MSS Music._daap._tcp.local. (SRV) complete
    ServiceCallback: MSS Music._daap._tcp.local. (SRV) Name Registered (0)
    Callback: Name Registered
    Announcing MSS Music._http._tcp.local. (SRV) 9
    Announcing MSS Music._http._tcp.local. (TXT) 9
    Announcing _services._dns-sd._udp.local. (PTR) 9
    Announcing _http._tcp.local. (PTR) 9
    Announcing MSS Music._rsp._tcp.local. (SRV) 9
    Announcing MSS Music._rsp._tcp.local. (TXT) 9
    Announcing _services._dns-sd._udp.local. (PTR) 9
    Announcing _rsp._tcp.local. (PTR) 9
    Announcing MSS Music._daap._tcp.local. (SRV) 9
    Announcing MSS Music._daap._tcp.local. (TXT) 9
    Announcing _services._dns-sd._udp.local. (PTR) 9
    Announcing _daap._tcp.local. (PTR) 9
    SendResponses: Sending 0 Deregistrations, 12 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 768 ticks
    select(5, 0.097656)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 12 Answers, 0 Authorities, 0 Additionals
    select(5, 0.096679)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 0.639648)
    mDNS_Execute
    Announcing (none).local. (Addr) 8
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 8
    Announcing MSS Music._http._tcp.local. (SRV) 8
    Announcing MSS Music._http._tcp.local. (TXT) 8
    Announcing _services._dns-sd._udp.local. (PTR) 8
    Announcing _http._tcp.local. (PTR) 8
    Announcing MSS Music._rsp._tcp.local. (SRV) 8
    Announcing MSS Music._rsp._tcp.local. (TXT) 8
    Announcing _services._dns-sd._udp.local. (PTR) 8
    Announcing _rsp._tcp.local. (PTR) 8
    Announcing MSS Music._daap._tcp.local. (SRV) 8
    Announcing MSS Music._daap._tcp.local. (TXT) 8
    Announcing _services._dns-sd._udp.local. (PTR) 8
    Announcing _daap._tcp.local. (PTR) 8
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 2048 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 1.889648)
    mDNS_Execute
    Announcing (none).local. (Addr) 7
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 7
    Announcing MSS Music._http._tcp.local. (SRV) 7
    Announcing MSS Music._http._tcp.local. (TXT) 7
    Announcing _services._dns-sd._udp.local. (PTR) 7
    Announcing _http._tcp.local. (PTR) 7
    Announcing MSS Music._rsp._tcp.local. (SRV) 7
    Announcing MSS Music._rsp._tcp.local. (TXT) 7
    Announcing _services._dns-sd._udp.local. (PTR) 7
    Announcing _rsp._tcp.local. (PTR) 7
    Announcing MSS Music._daap._tcp.local. (SRV) 7
    Announcing MSS Music._daap._tcp.local. (TXT) 7
    Announcing _services._dns-sd._udp.local. (PTR) 7
    Announcing _daap._tcp.local. (PTR) 7
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 4096 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 3.889648)
    mDNS_Execute
    Announcing (none).local. (Addr) 6
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 6
    Announcing MSS Music._http._tcp.local. (SRV) 6
    Announcing MSS Music._http._tcp.local. (TXT) 6
    Announcing _services._dns-sd._udp.local. (PTR) 6
    Announcing _http._tcp.local. (PTR) 6
    Announcing MSS Music._rsp._tcp.local. (SRV) 6
    Announcing MSS Music._rsp._tcp.local. (TXT) 6
    Announcing _services._dns-sd._udp.local. (PTR) 6
    Announcing _rsp._tcp.local. (PTR) 6
    Announcing MSS Music._daap._tcp.local. (SRV) 6
    Announcing MSS Music._daap._tcp.local. (TXT) 6
    Announcing _services._dns-sd._udp.local. (PTR) 6
    Announcing _daap._tcp.local. (PTR) 6
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 8192 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 7.889648)
    mDNS_Execute
    Announcing (none).local. (Addr) 5
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 5
    Announcing MSS Music._http._tcp.local. (SRV) 5
    Announcing MSS Music._http._tcp.local. (TXT) 5
    Announcing _services._dns-sd._udp.local. (PTR) 5
    Announcing _http._tcp.local. (PTR) 5
    Announcing MSS Music._rsp._tcp.local. (SRV) 5
    Announcing MSS Music._rsp._tcp.local. (TXT) 5
    Announcing _services._dns-sd._udp.local. (PTR) 5
    Announcing _rsp._tcp.local. (PTR) 5
    Announcing MSS Music._daap._tcp.local. (SRV) 5
    Announcing MSS Music._daap._tcp.local. (TXT) 5
    Announcing _services._dns-sd._udp.local. (PTR) 5
    Announcing _daap._tcp.local. (PTR) 5
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 16384 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 15.889648)
    mDNS_Execute
    Announcing (none).local. (Addr) 4
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 4
    Announcing MSS Music._http._tcp.local. (SRV) 4
    Announcing MSS Music._http._tcp.local. (TXT) 4
    Announcing _services._dns-sd._udp.local. (PTR) 4
    Announcing _http._tcp.local. (PTR) 4
    Announcing MSS Music._rsp._tcp.local. (SRV) 4
    Announcing MSS Music._rsp._tcp.local. (TXT) 4
    Announcing _services._dns-sd._udp.local. (PTR) 4
    Announcing _rsp._tcp.local. (PTR) 4
    Announcing MSS Music._daap._tcp.local. (SRV) 4
    Announcing MSS Music._daap._tcp.local. (TXT) 4
    Announcing _services._dns-sd._udp.local. (PTR) 4
    Announcing _daap._tcp.local. (PTR) 4
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 32768 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 31.889648)
    mDNS_Execute
    Announcing (none).local. (Addr) 3
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 3
    Announcing MSS Music._http._tcp.local. (SRV) 3
    Announcing MSS Music._http._tcp.local. (TXT) 3
    Announcing _services._dns-sd._udp.local. (PTR) 3
    Announcing _http._tcp.local. (PTR) 3
    Announcing MSS Music._rsp._tcp.local. (SRV) 3
    Announcing MSS Music._rsp._tcp.local. (TXT) 3
    Announcing _services._dns-sd._udp.local. (PTR) 3
    Announcing _rsp._tcp.local. (PTR) 3
    Announcing MSS Music._daap._tcp.local. (SRV) 3
    Announcing MSS Music._daap._tcp.local. (TXT) 3
    Announcing _services._dns-sd._udp.local. (PTR) 3
    Announcing _daap._tcp.local. (PTR) 3
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 65536 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 63.889648)
    mDNS_Execute
    Announcing (none).local. (Addr) 0
    Announcing 5.1.168.192.in-addr.arpa. (PTR) 0
    Announcing MSS Music._http._tcp.local. (SRV) 0
    Announcing MSS Music._http._tcp.local. (TXT) 0
    Announcing _services._dns-sd._udp.local. (PTR) 2
    Announcing _http._tcp.local. (PTR) 2
    Announcing MSS Music._rsp._tcp.local. (SRV) 0
    Announcing MSS Music._rsp._tcp.local. (TXT) 0
    Announcing _services._dns-sd._udp.local. (PTR) 2
    Announcing _rsp._tcp.local. (PTR) 2
    Announcing MSS Music._daap._tcp.local. (SRV) 0
    Announcing MSS Music._daap._tcp.local. (TXT) 0
    Announcing _services._dns-sd._udp.local. (PTR) 2
    Announcing _daap._tcp.local. (PTR) 2
    SendResponses: Sending 0 Deregistrations, 14 Announcements, 0 Answers, 0 Additio nals on 555E2188
    SendResponses: Next in 131072 ticks
    select(5, 0.098632)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.16 8.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 14 Answers, 0 Authorities, 0 Additionals
    select(5, 0.097656)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 127.889648)
    mDNS_Execute
    Announcing _services._dns-sd._udp.local. (PTR) 1
    Announcing _http._tcp.local. (PTR) 1
    Announcing _services._dns-sd._udp.local. (PTR) 1
    Announcing _rsp._tcp.local. (PTR) 1
    Announcing _services._dns-sd._udp.local. (PTR) 1
    Announcing _daap._tcp.local. (PTR) 1
    SendResponses: Sending 0 Deregistrations, 6 Announcements, 0 Answers, 0 Additionals on 555E2188
    SendResponses: Next in 262144 ticks
    select(5, 0.099609)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.168.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 6 Answers, 0 Authorities, 0 Additionals
    select(5, 0.098632)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 255.889648)
    mDNS_Execute
    Announcing _services._dns-sd._udp.local. (PTR) 0
    Announcing _http._tcp.local. (PTR) 0
    Announcing _services._dns-sd._udp.local. (PTR) 0
    Announcing _rsp._tcp.local. (PTR) 0
    Announcing _services._dns-sd._udp.local. (PTR) 0
    Announcing _daap._tcp.local. (PTR) 0
    SendResponses: Sending 0 Deregistrations, 6 Announcements, 0 Answers, 0 Additionals on 555E2188
    SendResponses: Next in 2013265920 ticks
    select(5, 0.099609)
    SocketDataReady got a packet from 192.168.1.5 to 224.0.0.251 on interface 192.168.1.5/eth0/2
    Received Response from 192.168.1.5 addressed to 224.0.0.251 on 555E2188 TTL 255 with 0 Questions, 6 Answers, 0 Authorities, 0 Additionals
    select(5, 0.098632)
    select(5, 0.000976)
    mDNS_Execute
    select(5, 1965567.832031)
    Skipped bground scan... no users

    #8981
    rojbalc
    Participant

    1. it still can’t find my music. Can my syntax be wrong?


    mp3_dir = /Admin1/My Music

    Probably isn’t a valid directory. I’m assuming you made a new share called “Admin1” and that the music sits in a directory under that share called “My Music”, right? If so, the path is probably:

    /shares/mss-hdd/Admin1/My Music

    But I’m not sure. You might telnet into the box and explore with “ls” and “cd” to see if you can find the right path. I’d guess it’s the one above, though.

    2. how can I get rid of that bloody Twonky MSS stuff that’s still showing up on my Soundbridge?!

    Not sure. Turns out I don’t run Twonky. Go figure. 🙂

    Is there an uninstaller? Could you reverse the process that you used to install it?

    Might be that the twonky forums would have more info in that regard.

    — Ron

    #8982
    rojbalc
    Participant

    Thanks for the help Ron, even though you appear to have posted as me just to confuse…(!)

    @rojbalc wrote:

    Probably isn’t a valid directory. I’m assuming you made a new share called “Admin1” and that the music sits in a directory under that share called “My Music”, right? If so, the path is probably:

    /shares/mss-hdd/Admin1/My Music

    But I’m not sure. You might telnet into the box and explore with “ls” and “cd” to see if you can find the right path. I’d guess it’s the one above, though.

    Exactly. Schoolboy error!

    Anyway, I’m up and running now – unbelievably I actually managed to sort the main problem out myself in the end too:

    As I mentioned, the Server had been up and running, but then it suddenly disappeared again and I didn’t know why. I assumed this was to do with the rendezvous.conf file – that it was no longer advertising mt-daapd to my Soundbridge. Given that I had re-entered the last 4 lines of the file from memory and previously had no experience with Linux, it was likely I’d got it wrong… After playing around with this for a while I realised this wasn’t the case – no matter what I did, the MSS wasn’t visible.

    Next I tried to start the process manually with


    # /opt/sbin/mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf

    This worked – the Server was visible again. It just wasn’t starting automatically. I thought the “/opt/lib/ld.so.1” part of the S60mt-daapd file wasn’t working properly and that my libraries weren’t up to date or something. Unlikely though, as they’d downloaded without any problems.

    Eventually I found a thread where someone had posted the entire contents of the S60mt-daapd file and by comparing the 2, it turned out that in mine, the line “export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/lib” had been justified during text editing so it was directly behind the line “# can be removed”, so the line read


    # can be removed export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/lib

    and the library wasn’t be exported/loaded properly… Aaarrggghh! I knew the text editing would be my downfall!

    Anyway, after remedying that, everything was fine and the processes started automatically. Result!

    3 minor things to sort out still (ok, 2 minor and 1 major pain in the @rse that is Zonealarm):

    1. The Twonky stuff. (It wasn’t me who originally installed it – I bought my MSS second hand). The processes were still running on the MSS and being displayed on my Soundbridge. In the end I took the rather rudimentary step of simply deleting the server file. This meant that it was no longer displayed on my Soundbridge, but I don’t think the MSS was very happy about it and was whirring and clicking (to use the technical jargon) rather a lot after a reboot and took ages to come online again. Thanks for the tip though – I’ll have a look on the Twonky forums to see about deleting the rest.

    2. The MSS does not like shutting down while mt-daapd is running. The usual tap of the on/off button and it took between 30-60 seconds to shut down as opposed to the usual 5-10. Simply leaving the MSS on would be the simple solution, but I did plan to turn it off at night… I could always shut the server down via the web GUI, but that kind of defeats the object of a pc-independent NAS solution… I’ll have another go tonight and see if it improves. I’ve heard of such problems with the Slug, but not on MSS. Anyone had a similar experience?

    3. New firewall software – I HATE ZONEALARM!! It doesn’t even let me see the MSS as a drive on my pc unless I restart the firewall. Not a great solution for an always-on internet connection… Anyone have any (software) suggestions/recommendations?

    Other than that – very happy! (Donation to the Soundforge cause has already been made…)

    Now to start looking for a new sibling for my Soundbridge…

    Thanks again,
    roj.

    #8983
    rpedde
    Participant

    @rojbalc wrote:

    Thanks for the help Ron, even though you appear to have posted as me just to confuse…(!)

    Too many buttons on this interface. Oops!

    2. The MSS does not like shutting down while mt-daapd is running. The usual tap of the on/off button and it took between 30-60 seconds to shut down as opposed to the usual 5-10. Simply leaving the MSS on would be the simple solution, but I did plan to turn it off at night… I could always shut the server down via the web GUI, but that kind of defeats the object of a pc-independent NAS solution… I’ll have another go tonight and see if it improves. I’ve heard of such problems with the Slug, but not on MSS. Anyone had a similar experience?

    If you kill mt-daapd first, then shut it down, it’s okay?

    If so, it’s probably a signal handling problem. In the very very latests nightlies, the signal handling should be right — a SIGTERM should shut it down gracefully fairly quickly.

    Did you say what version you had? (a /opt/sbin/mt-daapd -V in a relatively recent version should display version info).

    3. New firewall software – I HATE ZONEALARM!! It doesn’t even let me see the MSS as a drive on my pc unless I restart the firewall. Not a great solution for an always-on internet connection… Anyone have any (software) suggestions/recommendations?

    Are you using the PC for connection sharing? Or are you behind a router with NAT?

    If so, you could always loosen up your rules a bit — allow stuff to and from the local network, but only prompt for non-local traffic.

    Other than that – very happy! (Donation to the Soundforge cause has already been made…)

    Woohoo! Probably about time to get that other nslu2 so I can start dropping other-endian arm binaries for nightlies.

    Anyway, thanks, and good luck.

    — Ron

    #8984
    rojbalc
    Participant

    @rpedde wrote:

    If you kill mt-daapd first, then shut it down, it’s okay?

    Yeah, it just seems to be when mt-daapd is running…

    If so, it’s probably a signal handling problem. In the very very latests nightlies, the signal handling should be right — a SIGTERM should shut it down gracefully fairly quickly.

    Exactly, but the reason I bought the MSS was so I could have it running without needing to have the pc on… Ah well, as I say, shutdown does work, just takes a while.

    Did you say what version you had? (a /opt/sbin/mt-daapd -V in a relatively recent version should display version info).

    Pretty up to date: svn-1498

    Are you using the PC for connection sharing? Or are you behind a router with NAT?

    No, nothing like that, unfortunately… Mind you, I am still running Windows 2000, so I’ve probably only got myself to blame…

    Woohoo! Probably about time to get that other nslu2 so I can start dropping other-endian arm binaries for nightlies.

    Ahem… don’t get too excited – I didn’t say I’d clicked the 250$ donation button 😛 Not quite that rich…

    roj.

Viewing 15 posts - 1 through 15 (of 15 total)
  • The forum ‘General Discussion’ is closed to new topics and replies.