Reply To: svn-1671 on Mac – Broken Pipe

  • Post date

FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › svn-1671 on Mac – Broken Pipe › Reply To: svn-1671 on Mac – Broken Pipe

14/10/2007 at 5:41 PM #12820
rpedde
Participant

@SunbeamGuy wrote:

I’ve just installed and updated ubuntu and am getting similar errors (broken pipe)… Not sure yet, but I think it happens when the song streaming is paused. I kill the process, start mt-daapd and resume listening. Here’s a snippet from my log:

2007-10-13 20:10:11 (b7cbda50): Scanned 7328 songs (was 7328) in 15 seconds
2007-10-13 20:11:40 (b6c62b90): Session 0: Streaming file ‘UB40 – The Very Best Of UB40 – 13 – Rat In Mi Kitchen – eac256cbr.mp3’ to 192.168.0.8 (offset 0)
2007-10-13 20:15:14 (b7cbda50): Rescanning database
2007-10-13 20:15:26 (b7cbda50): Starting playlist scan
2007-10-13 20:15:28 (b7cbda50): Updating playlists
2007-10-13 20:15:28 (b7cbda50): Scanned 7328 songs (was 7328) in 14 seconds
2007-10-13 20:16:03 (b6c62b90): Write error: Broken pipe
ps -aef |grep mt-daapd2007-10-13 21:17:39 (b7c1ca50): Firefly Version svn-1673: Starting with debuglevel 2
2007-10-13 21:17:39 (b7c1ca50): Plugin loaded: ssc-script/svn-1673
2007-10-13 21:17:39 (b7c1ca50): Plugin loaded: daap/svn-1673
2007-10-13 21:17:39 (b7c1ca50): Plugin loaded: rsp/svn-1673
2007-10-13 21:17:39 (b7c1ca50): Starting rendezvous daemon
2007-10-13 21:17:39 (b7c1ca50): Client registering
2007-10-13 21:17:39 (b7c1ca50): Starting signal handler
2007-10-13 21:17:39 (b7c1ca50): Initializing database
2007-10-13 21:17:45 (b7c1ca50): Starting web server from /usr/share/mt-daapd/admin-root on port 4001
2007-10-13 21:17:45 (b7c1ca50): Registering rendezvous names
2007-10-13 21:17:46 (b7c1ca50): Serving 7328 songs. Startup complete in 6 seconds
2007-10-13 21:17:46 (b7c1ca50): Rescanning database
2007-10-13 21:18:00 (b7c1ca50): Starting playlist scan
2007-10-13 21:18:02 (b7c1ca50): Updating playlists
2007-10-13 21:18:02 (b7c1ca50): Scanned 7328 songs (was 7328) in 16 seconds

Thanks!

Ya, that’s correct and normal. When you pause, the client actually ungracefully terminates the connection. Which generates the error in the log.

One could make the argument that the error shouldn’t be so high as to appear in the log, but I can’t tell “bad” connection drops from “good” connection drops, so it always logs connection drops.

— Ron