10th November 2008 at 1:27 pm #2696
I’ve used mt-daapd in the past, on a freebsd box with no problems, used it briefly on windows too, so I’m somewhat familiar with how to set up and configure it, but I have this issue where it seems to be working, I can stream to any of my laptops on the network, but then suddenly after about an hour or so it will stop working.
The log never shows anything more than something like this:
2008-11-09 18:41:19: Rescanning database
2008-11-09 18:43:57: Session 0: Streaming file '05-gza-cold_world-www.bizzydownload.tk.mp3' to 192.168.1.42 (offset 0)
2008-11-09 18:46:22: Rescanning database
2008-11-09 18:49:27: Session 0: Streaming file '15 - Young Jeezy - Trap or Die ft. Bun B.mp3' to 192.168.1.42 (offset 0)
2008-11-09 18:51:24: Rescanning database
2008-11-09 18:53:28: Session 0: Streaming file '14 The Faces.mp3' to 192.168.1.42 (offset 0)
2008-11-09 18:56:14: Client 192.168.1.42 disconnected
So that hasn’t been any help – it just stops showing up in my itunes libraries. According to /sbin/service status, the web admin panel, and everything else I know to check mt-daapd is still running and broadcasting, it just cant be seen on the network.
Here’s my set up:
MacBook Pro, OS X 10.5.5
Fedora 9 2.6.25-14.fc9.i686
mt-daapd Version 0.2.4.2
Network Adapter: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express
/sbin/ifconfig eth0 returns:
eth0 Link encap:Ethernet HWaddr 00:0D:56:DA:F6:18
inet addr:192.168.1.47 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::20d:56ff:feda:f618/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1550112 errors:0 dropped:0 overruns:0 frame:0
TX packets:2045914 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:817154180 (779.2 MiB) TX bytes:2054908531 (1.9 GiB)
Router: Westell Versalink 327w (supports multicast)
Any ideas as to how I could fix this?10th November 2008 at 4:59 pm #17869
The server is connected (wired) to the router?
And the client is/was streaming wireless?
Try connecting your client wired to see if it has anything to do with wireless problems.
Next to that, try raising the debuglevel up to level 9 to find more info in the logfile.
You must be logged in to reply to this topic.