Jack broken pipe error

  • socphoenix
Posted: Tue, 06/10/2008 - 14:45
Jack has been shutting down on my sound card saying that it has run into a broken pipe. The full error message is as follows: 10:26:41.969 Patchbay deactivated. 10:26:42.019 Statistics reset. 10:26:42.119 MIDI connection graph change. JACK tmpdir identified as [/dev/shm] 10:26:42.261 MIDI connection change. 10:26:44.284 Startup script... 10:26:44.284 artsshell -q terminate JACK tmpdir identified as [/dev/shm] can't create mcop directory Creating link /home/michael/.kde/socket-64studio. 10:26:44.821 Startup script terminated with exit status=256. 10:26:44.822 JACK is starting... 10:26:44.824 /usr/bin/jackd -R -p512 -dalsa -r48000 -p512 -n4 -D -Chw:0 -Phw:0,0 -S 10:26:44.828 JACK was started with PID=5071 (0x13cf). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Enhanced3DNow! detected SSE2 detected apparent rate = 48000 creating alsa driver ... hw:0,0|hw:0|512|4|48000|0|0|nomon|swmeter|-|16bit control device hw:0 configuring for 48000Hz, period = 512 frames, buffer = 4 periods ALSA: final selected sample format for capture: 16bit little-endian ALSA: use 4 periods for capture ALSA: final selected sample format for playback: 16bit little-endian ALSA: use 4 periods for playback 10:26:45.843 Server configuration saved to "/home/michael/.jackdrc". 10:26:45.845 Statistics reset. 10:26:46.053 Client activated. 10:26:46.055 Audio connection change. 10:26:46.059 Audio connection graph change. JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected 10:26:52.249 Audio connection graph change. 10:26:52.283 Audio connection change. 10:26:52.289 Audio connection graph change. 10:26:52.293 MIDI connection graph change. 10:26:52.486 MIDI connection change. 10:27:05.573 MIDI connection graph change. 10:27:05.578 MIDI connection change. 10:27:06.889 Audio connection graph change. 10:27:11.455 Audio connection graph change. 10:27:11.606 Audio connection change. 10:27:19.620 Audio connection graph change. 10:27:20.456 Audio connection graph change. 10:27:20.809 Audio connection graph change. 10:30:48.653 Audio connection graph change. 10:30:48.783 Audio connection change. 10:30:55.047 Audio connection graph change. 10:30:55.523 Audio connection graph change. 10:30:55.809 Audio connection graph change. jackd watchdog: timeout - killing jackd 10:36:50.115 Shutdown notification. 10:36:50.117 Client deactivated. 10:36:50.119 JACK was stopped successfully. 10:36:50.120 Post-shutdown script... 10:36:50.120 killall jackd zombified - calling shutdown handler cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) 10:36:50.143 MIDI connection graph change. jackd: no process killed 10:36:50.341 Post-shutdown script terminated with exit status=256. 10:37:32.763 Startup script... 10:37:32.763 artsshell -q terminate JACK tmpdir identified as [/dev/shm] can't create mcop directory Creating link /home/michael/.kde/socket-64studio. 10:37:33.042 Startup script terminated with exit status=256. 10:37:33.042 JACK is starting... 10:37:33.042 /usr/bin/jackd -R -p512 -dalsa -r48000 -p512 -n4 -D -Chw:0 -Phw:0,0 -S 10:37:33.044 JACK was started with PID=5237 (0x1475). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Enhanced3DNow! detected SSE2 detected apparent rate = 48000 creating alsa driver ... hw:0,0|hw:0|512|4|48000|0|0|nomon|swmeter|-|16bit control device hw:0 configuring for 48000Hz, period = 512 frames, buffer = 4 periods ALSA: final selected sample format for capture: 16bit little-endian ALSA: use 4 periods for capture ALSA: final selected sample format for playback: 16bit little-endian ALSA: use 4 periods for playback 10:37:34.061 Server configuration saved to "/home/michael/.jackdrc". 10:37:34.062 Statistics reset. 10:37:34.069 Client activated. 10:37:34.070 Audio connection change. 10:37:34.086 Audio connection graph change. JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected 10:37:37.417 Audio connection graph change. unknown source port in attempted connection [ZynAddSubFX:out_1] unknown source port in attempted connection [ZynAddSubFX:out_2] unknown source port in attempted connection [ZynAddSubFX:out_1] unknown source port in attempted connection [ZynAddSubFX:out_2] 10:37:37.488 Audio connection change. jackd watchdog: timeout - killing jackd zombified - calling shutdown handler 10:37:38.125 Shutdown notification. 10:37:38.125 Client deactivated. 10:37:38.126 JACK was stopped successfully. 10:37:38.126 Post-shutdown script... 10:37:38.126 killall jackd cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) jackd: no process killed 10:37:38.340 Post-shutdown script terminated with exit status=256. It runs ok originally, but after about 10 minutes it gives me that errors, and continues with them until the machine is power cycled. I am using the built in Realtek HD card (I know a piece of junk), and it will do this whether i am doing anything or not. In this case I was using Ardour to record a midi application that came with 64 Studio. Any advice as to what a broken pipe is exactly, or how to fix such a problem would be very much appreciated.

qjackctl

  • cinder
  • 10/20/08
  • Fri, 01/09/2009 - 11:41
Jack has been crashing with qlackctl. If I start jackd manualy, and then start qjackatl(I've unchecked the startup and shutdown scripts) it's OK. So once I'm all set up, I quit qjackctl, and let jack fly (saves 4% memory too:) Timing is Everything!

reported as a bug

  • lofty00
  • 08/14/08
  • Mon, 08/18/2008 - 15:13
see: http://trac.64studio.com/64studio/ticket/441

possible cure?

  • lofty00
  • 08/14/08
  • Mon, 08/18/2008 - 09:05
Having noticed that jackd seems to crash immediately after a MIDI connection graph change, with qjackctl the only midi application running, I think the problem may be a bug in qjackctl. I am testing this by running jackd standalone with the same options I was using under qjackctl. So far it's been running about five minutes without a problem, which is better than I've had it since this problem started. I'll leave it running as long as I can and report back.

confirmed ...

  • lofty00
  • 08/14/08
  • Mon, 08/18/2008 - 10:17
Jackd has now been running for an hour with no problems. When I start it again with qjackctl, the problem recurs almost straight away. If I downgrade qjackctl to version 0.2.21-1 from debian stable, it seems to run OK. (Though I haven't tested it yet for more than a couple of minutes.)

I'm getting the same problem

  • lofty00
  • 08/14/08
  • Mon, 08/18/2008 - 08:37
with an M-Audio firewire solo external soundcard. This is strange, because I've previously had jackd and ardour running beautifully for almost 12 hours with no xruns. My log looks like this: 09:05:33.631 JACK is starting... 09:05:33.632 jackd -R -P89 -t2000 -dfreebob -dhw:0 -r48000 -p256 -n3 -D 09:05:33.637 JACK was started with PID=4766 (0x129e). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Freebob using Firewire port 0, node -1 09:05:34.366 MIDI connection graph change. libiec61883 warning: Established connection on channel 0. You may need to manually set the channel on the receiving node. libiec61883 warning: Established connection on channel 1. You may need to manually set the channel on the transmitting node. 09:05:35.671 Server configuration saved to "/home/andy/.jackdrc". 09:05:35.673 Statistics reset. 09:05:35.674 Client activated. 09:05:35.676 Audio connection change. 09:05:35.682 Audio connection graph change. JACK tmpdir identified as [/dev/shm] 09:06:33.568 MIDI connection graph change. 09:06:33.763 MIDI connection change. 09:06:35.144 Audio connection graph change. 09:06:41.594 Audio connection graph change. 09:06:42.239 Audio connection graph change. unknown source port in attempted connection [jamin:out_L] unknown source port in attempted connection [jamin:out_R] unknown destination port in attempted connection [jamin:in_L] unknown destination port in attempted connection [jamin:in_R] unknown source port in attempted connection [jamin:out_L] unknown source port in attempted connection [jamin:out_R] 09:06:42.413 Audio connection change. 09:07:42.150 Audio connection change. 09:07:45.867 Audio connection change. 09:19:12.707 MIDI connection graph change. 09:19:12.708 Shutdown notification. 09:19:12.709 Client deactivated. 09:19:12.710 JACK was stopped successfully. zombified - calling shutdown handler cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe)

hmmm...I get a similar error

  • ethanay
  • 05/20/08
  • Thu, 06/12/2008 - 07:10
when trying to use a Windows programs through Wine with WineASIO running FFADO as a backend to JACK (that's a lot of acronyms!) -- it tries to open connections on more and more transmit channels (when it should only be 0 and 1, but goes up to 60+!!) and then crashes jack until reboot. It seems to open firewire connections unsuccessfully without closing them afterwards, leaving the firewire bus completely inaccessible....that's the best I can do. I need to find out how to contact the WineASIO developer as everything else seems to be ok... sorry I can't be of more help :-/ ethan