FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › General Discussion › Pinnacle Soundbridge – MSS installation problems
- This topic has 14 replies, 2 voices, and was last updated 17 years, 9 months ago by rojbalc.
-
AuthorPosts
-
04/02/2007 at 11:52 PM #8980rojbalcParticipant
@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
05/02/2007 at 12:07 AM #8981rojbalcParticipant1. 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
06/02/2007 at 9:56 AM #8982rojbalcParticipantThanks 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.07/02/2007 at 12:01 AM #8983rpeddeParticipant@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
07/02/2007 at 10:07 PM #8984rojbalcParticipant@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.
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.