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.
Main pipe closed errors
Re: Main pipe closed errors
Remove "sound=on, hw:1:0" line. There is no hw:1 device.
Re: Main pipe closed errors
Can we keep simply sound=on so that it could potentially play through a usb headset?
Re: Main pipe closed errors
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
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.
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.