Date: Fri, 15 Feb 2019 11:31:36 -0700 From: "Janky Jay, III" <jankyj@unfs.us> To: meta@FreeBSD.org, freebsd-ports@freebsd.org Subject: net/xrdp: Issue(s) with Channels/Clipboard. Message-ID: <f95c8c0d-ce65-f98f-c65e-f7a6b98d3391@unfs.us>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Pjimh4grCba3BjyfNkW1QPVLtRO6rwNt2 Content-Type: multipart/mixed; boundary="WpiMZIvEHJnvgVFcsrcKDn71o8GsuOps6"; protected-headers="v1" From: "Janky Jay, III" <jankyj@unfs.us> To: meta@FreeBSD.org, freebsd-ports@freebsd.org Message-ID: <f95c8c0d-ce65-f98f-c65e-f7a6b98d3391@unfs.us> Subject: net/xrdp: Issue(s) with Channels/Clipboard. --WpiMZIvEHJnvgVFcsrcKDn71o8GsuOps6 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi All, So, I noticed this quite a while back but it didn't bother me too much. However, my curiosity has gotten the best of me and now I want to find out what's going on. I'm running net/xrdp (version 0.9.9,1 installed via pkg) on two different, headless FBSD 11.2-Rp9 systems and they're behaving differently with 100% identical configurations. On both, the xrdp and sesman services start without any errors at all. However, on one of the systems upon authentication during login, I get the below errors in the xrdp.log file: [DEBUG] xrdp_wm_log_msg: connected ok [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [DEBUG] Closed socket 20 (AF_UNIX) [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [DEBUG] Closed socket 20 (AF_UNIX) [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [DEBUG] Closed socket 20 (AF_UNIX) [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan This is very similar to the issue reported at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231210 but the issue was closed with "works as expected". Apparently, that's not the case on all systems? This also causes the connection to take 16 seconds to open XFCE4 once it finally gives up on channels. I see 4 errors so I'm guessing there's a 4 second timeout between attempts. Something similar to the issue/recommendation reported at https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the recommended disallowing of channels to see if it would connect faster but it does nothing. Still attempts the connections to "chansrv" and takes 16 seconds. What is even more strange is that for about 3-4 months or so, this system began connecting to channels like normal and and worked liked the other. Then, suddenly, stopped connecting one day (I'm not sure when it stopped but it would've been in the last 2 months or so?). On the system that works without any issues, I see the "chansrv" connection successful after authentication and login is immediate: [DEBUG] xrdp_wm_log_msg: connected ok [DEBUG] xrdp_mm_connect_chansrv: chansrv connect successful All software is up-to-date on both systems and, as mentioned before, configuration files are absolutely identical. So, I'm curious as to why one is able to connect to channels while the other is not? If anyone has any ideas or wants additional info/logs/etc... I'm all ears and will be more than happy to provide any additional details. Regards, Janky Jay, III --WpiMZIvEHJnvgVFcsrcKDn71o8GsuOps6-- --Pjimh4grCba3BjyfNkW1QPVLtRO6rwNt2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQT3labtx1DPvRcqv5cYrcyxRslmfgUCXGcFiAAKCRAYrcyxRslm fm1tAJwN7JPRHB6vpVhXI1y+bj5e37vebwCfU0SmmCYCToO3WubH4CiBuV/6Ros= =jlbZ -----END PGP SIGNATURE----- --Pjimh4grCba3BjyfNkW1QPVLtRO6rwNt2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f95c8c0d-ce65-f98f-c65e-f7a6b98d3391>