Page 1 of 1

Main pipe closed errors

Posted: Tue Sep 10, 2019 12:43 am
by onatam
We have been seeing a large influx of "Main Pipe Closed" errors in our WTWare environment in one of our sites.

Our environment is two locations which connect to a gateway and the terminal servers are spread across the two sites. We have seen the issue come up in a rare occurrence but now it is happening often throughout the day. Please advise.

See attached for logs.
terminallog.txt
(52.7 KiB) Downloaded 91 times

Re: Main pipe closed errors

Posted: Tue Sep 10, 2019 8:47 am
by akatik
Remove "sound=on, hw:1:0" line. There is no hw:1 device.

Re: Main pipe closed errors

Posted: Tue Sep 10, 2019 5:19 pm
by onatam
Can we keep simply sound=on so that it could potentially play through a usb headset?

Re: Main pipe closed errors

Posted: Wed Sep 11, 2019 9:05 pm
by Webjom
yes it goes but you have to enter the jack 3.5 parameter and plug it into them " sound=on, amixet:cset numid=3 1

Re: Main pipe closed errors

Posted: Sat Sep 14, 2019 11:32 am
by akatik
On Raspberry, "sound=on" is for onboard sound via HDMI.
For USB headset, "sound=on, hw:1:0". But you should connect USB headset. With ""sound=on, hw:1:0"" and without USB headset wtware will crush trying to play sound on nonexisting device.