Hej, <div><br></div><div> Skulle ni kunna ta bort mig från mailinglistan också, tack.</div><div><br></div><div>--------------------------------------------------------<br>Best regards / Med vänlig hälsning<br>Håkan Andersson | CEO & Cloud Architect<br>
Cloud Solutions AB | <a href="http://www.cloudsolutions.se/" target="_blank">www.cloudsolutions.se</a><div><span style="font-family: Arial, Helvetica, 'Nimbus Sans L', sans-serif; font-size: 13px; line-height: 15px; ">LinkedIn: <a href="http://se.linkedin.com/in/sapcloudhosting" title="View public profile" name="SafeHtmlFilter_webProfileURL" target="_blank" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; outline-width: initial; outline-style: none; outline-color: initial; font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit; vertical-align: baseline; text-decoration: none; color: rgb(0, 102, 153); ">http://se.linkedin.com/in/sapcloudhosting</a></span><br>
Hammarby fabriksväg 23 | SE-120 33 Stockholm<br><a href="mailto:ha@cloudsolutions.se" target="_blank">ha@cloudsolutions.se</a> | +46 708 200 366</div><div><br></div><br><div class="gmail_quote">2011/1/18 h zerbes <span dir="ltr"><<a href="mailto:heze54@gmail.com">heze54@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">First, my apologies to Rudi and Wesley for getting these emails! Looks like the<br>
mailing list got mixed up somehow and I'm sure Peter will be able to sort it<br>
out. For the record, I didn't sent the mails to you directly, gents, just cc'ed<br>
<a href="mailto:thinlinc-technical@lists.cendio.se">thinlinc-technical@lists.cendio.se</a>.<br>
<br>
And if you gents have never heard of thinlinc, feel free to check it out! :-|<br>
<br>
I only came about it a few days ago while researching different VDI solutions<br>
for our IT security consultancy here at <a href="http://surecity.com.au" target="_blank">surecity.com.au</a> and already think it's a<br>
great product. (And I'm not even related to Peter...;-) )<br>
<br>
Follow-up mails from me will go to Peter directly unless he objects.<br>
<div class="im"><br>
On 18/01/11 21:14, Peter Åstrand wrote:<br>
><br>
> I've done some testing on a Ubuntu 10.04 machine. I've also noticed that<br>
> connections to the sound tunnel happens every 2 seconds or so. There are two<br>
> processes responsible for this:<br>
<br>
</div>Thanks a lot for your testing and verification of the issue, Peter!<br>
<br>
It's true that sound is not working while using the thinlinc client.<br>
<br>
The ssh client seems to use a whole stack (read: 6) of redirects on the remote<br>
server:<br>
<div class="im"><br>
$ pgrep -l -f /opt/thinlinc/lib/tlclient/ssh<br>
</div>14757 /opt/thinlinc/lib/tlclient/ssh -N -o PubkeyAuthentication=no -o<br>
CheckHostIP=no -o NumberOfPasswordPrompts=1 <a href="mailto:guest@172.27.26.205">guest@172.27.26.205</a> -p 22 -L<br>
36488:<a href="http://127.0.0.1:5901" target="_blank">127.0.0.1:5901</a> -R 4910:<a href="http://127.0.0.1:34438" target="_blank">127.0.0.1:34438</a> -R 4915:<a href="http://127.0.0.1:35093" target="_blank">127.0.0.1:35093</a> -R<br>
4916:<a href="http://127.0.0.1:54180" target="_blank">127.0.0.1:54180</a> -R 4914:<a href="http://127.0.0.1:39659" target="_blank">127.0.0.1:39659</a> -R 4913:<a href="http://127.0.0.1:37192" target="_blank">127.0.0.1:37192</a><br>
<br>
whereas the server has these ports open:<br>
<br>
root@srv205:~# netstat -atn | grep LIST<br>
tcp 0 0 <a href="http://127.0.0.1:4910" target="_blank">127.0.0.1:4910</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:10000" target="_blank">0.0.0.0:10000</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:80" target="_blank">0.0.0.0:80</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:4913" target="_blank">127.0.0.1:4913</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:4914" target="_blank">127.0.0.1:4914</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:1010" target="_blank">0.0.0.0:1010</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:4915" target="_blank">127.0.0.1:4915</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:4916" target="_blank">127.0.0.1:4916</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:22" target="_blank">0.0.0.0:22</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:631" target="_blank">127.0.0.1:631</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:6010" target="_blank">127.0.0.1:6010</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:6011" target="_blank">127.0.0.1:6011</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:443" target="_blank">0.0.0.0:443</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:9000" target="_blank">0.0.0.0:9000</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://0.0.0.0:904" target="_blank">0.0.0.0:904</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:5901" target="_blank">127.0.0.1:5901</a> 0.0.0.0:* LISTEN<br>
<br>
<br>
the client, OTOH, is missing two of them (34438,35093):<br>
<br>
$ netstat -atn | grep LIST | egrep "36488|34438|35093|54180|39659|37192"<br>
tcp 0 0 <a href="http://127.0.0.1:54180" target="_blank">127.0.0.1:54180</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:37192" target="_blank">127.0.0.1:37192</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:36488" target="_blank">127.0.0.1:36488</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 <a href="http://127.0.0.1:39659" target="_blank">127.0.0.1:39659</a> 0.0.0.0:* LISTEN<br>
tcp6 0 0 ::1:36488 :::* LISTEN<br>
<div class="im"><br>
<br>
<br>
><br>
> /usr/lib/gnome-settings-daemon/gnome-settings-daemon<br>
> /usr/lib/indicator-sound/indicator-sound-service<br>
><br>
> This is probably normal behaviour.<br>
<br>
</div>"Sound" and "normal" don't go well together recently on Ubuntu, I have to admin :-(<br>
<br>
But yes, if I turn off sound on the thinlinc client, I don't get the error msgs<br>
anymore.<br>
<div class="im"><br>
> I've also managed to reproduce the "connect failed: Connection refused" error.<br>
> It happens if you have requested Sound redirection in the client, but the<br>
> client side sound server (PulseAudio) is not running. I can reproduce this<br>
> problem by killing it manually.<br>
><br>
> Probably, you get this error because PulseAudio on the client side fails or<br>
> crashes. You should be able to see this in tlclient.log.<br>
<br>
</div>Hmm, seems like there is only the current and one old log being kept? Just as<br>
well the .old.log one still contained the error as you predicted:<br>
<br>
2011-01-18T22:08:55: VNC command: /opt/thinlinc/lib/tlclient/vncviewer<br>
-FullColour=1 -LowColourLevel=2 -AutoSelect=1 -CustomCompressLevel=0<br>
-CompressLevel=6 -QualityLevel=8 -PasswordFile=/tmp/vncvi<br>
ewerYgkyVy -Shared=1 -DesktopSize=1280x900 127.0.0.1::36488<br>
2011-01-18T22:08:55: PulseAudio command: /opt/thinlinc/lib/tlclient/pulseaudio<br>
-n --use-pid-file=false -L "module-esound-protocol-tcp listen=127.0.0.1<br>
port=34438 cookie='/tmp/esdLehWxT'" -L "module<br>
-native-protocol-tcp listen=127.0.0.1 port=35093 cookie='/tmp/pulseaudionIOkae'"<br>
--fail=false -L module-alsa-sink -L module-alsa-source -L module-oss<br>
--log-level=notice<br>
2011-01-18T22:08:55: PulseAudio pid is 14758<br>
2011-01-18T22:08:55: Smart card daemon command:<br>
/opt/thinlinc/lib/tlclient/pcsctun -b 127.0.0.1 -p 54180 -c /tmp/pcsctundngaOy<br>
2011-01-18T22:08:55: smart card daemon pid is 14759<br>
2011-01-18T22:08:55: unfsd command: /opt/thinlinc/lib/tlclient/unfsd -d -e<br>
/tmp/unfsdtJL8sT -n 39659 -m 39659 -l 127.0.0.1 -t -p -s<br>
2011-01-18T22:08:55: unfsd pid is 14760<br>
2011-01-18T22:08:56: vncviewer pid is 14761<br>
2011-01-18T22:08:56: unfsd: UNFS3 unfsd 0.9.20 (C) 2006, Pascal Schmidt<br>
<<a href="mailto:unfs3-server@ewetel.net">unfs3-server@ewetel.net</a>><br>
2011-01-18T22:08:56: unfsd: /media/cdrom: ip 127.0.0.1 mask 255.255.255.255<br>
options 24<br>
2011-01-18T22:08:56: unfsd: /media/floppy: ip 127.0.0.1 mask 255.255.255.255<br>
options 28<br>
2011-01-18T22:08:56: vncviewer:<br>
2011-01-18T22:08:56: vncviewer: ThinLinc Client for X - built Oct 15 2010 01:27:54<br>
2011-01-18T22:08:56: vncviewer: Based on TigerVNC viewer - see<br>
<a href="http://www.tigervnc.org" target="_blank">http://www.tigervnc.org</a><br>
2011-01-18T22:08:56: vncviewer: Copyright (C) 2002-2005 RealVNC Ltd.<br>
2011-01-18T22:08:56: vncviewer: Copyright (C) 2000-2006 TightVNC Group<br>
2011-01-18T22:08:56: vncviewer: Copyright (C) 2004-2009 Peter Astrand for Cendio AB<br>
2011-01-18T22:08:56: vncviewer: See included EULA.txt for licensing details.<br>
2011-01-18T22:08:56: vncviewer: See <a href="http://www.cendio.com" target="_blank">http://www.cendio.com</a> for information on<br>
ThinLinc.<br>
2011-01-18T22:08:56: pulseaudio: pulseaudio: pulsecore/pdispatch.c:136:<br>
pa_pdispatch_new: Assertion `(entries && table) || (!entries && !table)' failed.<br>
2011-01-18T22:08:56: vncviewer:<br>
2011-01-18T22:08:56: vncviewer: Tue Jan 18 22:08:56 2011<br>
2011-01-18T22:08:56: vncviewer: CConn: connected to host 127.0.0.1 port 36488<br>
2011-01-18T22:08:56: vncviewer: CConnection: Server supports RFB protocol<br>
version 3.8<br>
2011-01-18T22:08:56: vncviewer: CConnection: Using RFB protocol version 3.8<br>
2011-01-18T22:08:56: vncviewer: TXImage: Using default colormap and visual,<br>
TrueColor, depth 24.<br>
2011-01-18T22:08:56: vncviewer: CConn: Using pixel format depth 24<br>
(32bpp) little-endian rgb888<br>
2011-01-18T22:08:56: vncviewer: CConn: Using Tight encoding<br>
2011-01-18T22:08:56: Process 14758 killed by signal 6<br>
2011-01-18T22:16:26: vncviewer:<br>
2011-01-18T22:16:26: vncviewer: Tue Jan 18 22:16:26 2011<br>
2011-01-18T22:16:26: vncviewer: main: End of stream<br>
2011-01-18T22:16:26: Process 14761 exited with code 0<br>
2011-01-18T22:16:27: Log file ended<br>
<div class="im"><br>
<br>
><br>
> We have a known issue with the PulseAudio included with our client: It fails<br>
> on system with the Alsa PulseAudio plugin. On Fedora, you can work around the<br>
> problem by uninstalling the package alsa-plugins-pulseaudio. On Ubuntu 9.04,<br>
> you must instead change the configuration. For example, you can rename<br>
> /usr/share/alsa/pulse-alsa.conf. We haven't verified if this also works on 10.04.<br>
><br>
> This problem will be fixed in the next release.<br>
><br>
> If you don't need sound, you can also just clear the Sound checkbox in the<br>
> client GUI. That should get rid of these messages.<br>
<br>
<br>
</div>It did, thanks a lot for that, Peter! Who doesn't want to have a happy UNIX<br>
system under his shell?<br>
Sound works in general on the client machine and pulse-audio is running on both,<br>
client and server.<br>
<br>
Well, as mentioned, I've only started looking thinlinc and sound would certainly<br>
be a "nice to have" for me and a "must have" for potential customers, if they<br>
were to migrate completely to thinlinc. This was the first problem I noticed<br>
while test driving it. I'd still have to read up a bit more in the manual and<br>
check out some of the other thinlinc features.<br>
<br>
All the best, Peter, thanks again for the quick help and keep up the good work!<br>
<br>
I'd like to be able to introduce thinlinc here in Australia in the future.<br>
heinz<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Thinlinc-technical mailing list<br>
<a href="mailto:Thinlinc-technical@lists.cendio.se">Thinlinc-technical@lists.cendio.se</a><br>
<a href="http://lists.cendio.se/mailman/listinfo/thinlinc-technical" target="_blank">http://lists.cendio.se/mailman/listinfo/thinlinc-technical</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-<br><br>
</div>