Xrdp sesman error problem connecting

I am running into another issue where the XRDP is not working. I have been at it for quite some time now and I think that I need help. I believe that it is an issue of the Ubuntu machine not listen...

It’s not worth it — there is a better & less painful solution:

X11VNC

I spent at least 8 hours fighting the battle to connect from Windows 10 to Ubuntu 16 via xrpd and Windows rdp. I tried endless «solutions» that I found posted all over the web. I made progress, but never managed to fully solve it. Even if I had, though, it seems that this is weak setup anyway, because:

  • You can’t use the Unity Desktop, so your rdp has connect you to a completely different OS UI than what you would use as the Ubuntu standard.
  • You can’t be logged on already with that account. So if you were have a scenerio where sometimes you work directly on the Ubuntu machine, and sometimes you connect remotely, you’d have to be sure to log out to allow for that remote connection.
  • From what’ve read, once you have this, you have also fight a battle to get a «re-connection» mechanism working to re-enter an rdp session you left.
  • You have to manually enter credentials every time you log on. There is no way to save them on the client end and just connect instantly.

I’ve used a pile of different remote connection interfaces, and overall nothing beats the ease and quality of Windows RDP yet to my mind. A such, I was pretty fixated on using that. After fighting this long enough though, and finally throwing in the towel, I found that VNC pretty much works just as well in this context.

As I said initially, on the Ubuntu side I used «x11vnc». Refer to these directions for details on getting that fully setup:

How to setup x11vnc to access with graphical login screen?

On the Windows side, I used RealVNC Viewer: https://www.realvnc.com/en/connect/download/viewer/, which I already had installed and setup for a remote connection to a Mac on my LAN as well.

With this setup, I have NONE of the weaknesses outlined above. Further, in full screen mode, the display is just as good as it would be naturally. I see 0 lag, 0 blurring. I have a bi-directional clipboard working without any effort to get that…

In theory, you are supposed to be able to stack xrpd and x11vnc. See: http://c-nergy.be/blog/?p=5956
I tried that too, just to see if I could get it to work. I had no luck with that either. So I just said the hell with xrpd in the end, uninstalled it, and rolled back all the changes I made to my machine fighting with it (or least so of them).

Unless you have a major reason that you NEED RDP instead of VNC, I strongly recommend going this route I’ve described instead.

Источник

It’s not worth it — there is a better & less painful solution:

X11VNC

I spent at least 8 hours fighting the battle to connect from Windows 10 to Ubuntu 16 via xrpd and Windows rdp. I tried endless «solutions» that I found posted all over the web. I made progress, but never managed to fully solve it. Even if I had, though, it seems that this is weak setup anyway, because:

  • You can’t use the Unity Desktop, so your rdp has connect you to a completely different OS UI than what you would use as the Ubuntu standard.
  • You can’t be logged on already with that account. So if you were have a scenerio where sometimes you work directly on the Ubuntu machine, and sometimes you connect remotely, you’d have to be sure to log out to allow for that remote connection.
  • From what’ve read, once you have this, you have also fight a battle to get a «re-connection» mechanism working to re-enter an rdp session you left.
  • You have to manually enter credentials every time you log on. There is no way to save them on the client end and just connect instantly.

I’ve used a pile of different remote connection interfaces, and overall nothing beats the ease and quality of Windows RDP yet to my mind. A such, I was pretty fixated on using that. After fighting this long enough though, and finally throwing in the towel, I found that VNC pretty much works just as well in this context.

As I said initially, on the Ubuntu side I used «x11vnc». Refer to these directions for details on getting that fully setup:

How to setup x11vnc to access with graphical login screen?

On the Windows side, I used RealVNC Viewer: https://www.realvnc.com/en/connect/download/viewer/, which I already had installed and setup for a remote connection to a Mac on my LAN as well.

With this setup, I have NONE of the weaknesses outlined above. Further, in full screen mode, the display is just as good as it would be naturally. I see 0 lag, 0 blurring. I have a bi-directional clipboard working without any effort to get that…

In theory, you are supposed to be able to stack xrpd and x11vnc. See: http://c-nergy.be/blog/?p=5956
I tried that too, just to see if I could get it to work. I had no luck with that either. So I just said the hell with xrpd in the end, uninstalled it, and rolled back all the changes I made to my machine fighting with it (or least so of them).

Unless you have a major reason that you NEED RDP instead of VNC, I strongly recommend going this route I’ve described instead.

Источник

I’m using Ubuntu 18.04 (GNOME desktop,Version 3.28.2)
xRDP is installed throng apt (Version 0.9.5).
But I found I can’t connect my remote computer.I checked the logs and they says I am failing to connect sesman.

This is the output of the xrdp.log

[20190428-19:52:47] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:10.28.195.65 port 43588
[20190428-19:52:47] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:10.108.117.111 port 3389)
[20190428-19:52:47] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20190428-19:52:47] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20190428-19:52:47] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20190428-19:52:47] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20190428-19:52:47] [DEBUG] TLSv1.2 enabled
[20190428-19:52:47] [DEBUG] TLSv1.1 enabled
[20190428-19:52:47] [DEBUG] TLSv1 enabled
[20190428-19:52:47] [DEBUG] Security layer: requested 3, selected 0
[20190428-19:52:47] [INFO ] connected client computer name: xiayu-XPS-13-93
[20190428-19:52:47] [INFO ] Non-TLS connection established from ::ffff:10.28.195.65 port 43588: encrypted with standard RDP security
[20190428-19:52:47] [DEBUG] xrdp_0000326e_wm_login_mode_event_00000001
[20190428-19:52:47] [INFO ] Cannot find keymap file /etc/xrdp/km-e0010404.ini
[20190428-19:52:47] [INFO ] Cannot find keymap file /etc/xrdp/km-00000404.ini
[20190428-19:52:47] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20190428-19:52:47] [WARN ] local keymap file for 0xe0010404 found and doesn't match built in keymap, using local keymap file
[20190428-19:52:59] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20190428-19:53:03] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53904)
[20190428-19:53:07] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53906)
[20190428-19:53:11] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53908)
[20190428-19:53:15] [ERROR] xrdp_wm_log_msg: Error connecting to sesman: 127.0.0.1 port: 3350
[20190428-19:53:15] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53910)
[20190428-19:53:15] [DEBUG] return value from xrdp_mm_connect 1
[20190428-19:53:15] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20190428-19:53:19] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53912)
[20190428-19:53:23] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53914)
[20190428-19:53:27] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53916)
[20190428-19:53:31] [ERROR] xrdp_wm_log_msg: Error connecting to sesman: 127.0.0.1 port: 3350
[20190428-19:53:31] [DEBUG] Closed socket 16 (AF_INET6 fe80::5a75:489:3f49:e3e5 port 53918)
[20190428-19:53:31] [DEBUG] return value from xrdp_mm_connect 1

There isn’t much output in the xrdp-sesman.log:

[20190428-17:24:00] [DEBUG] libscp initialized
[20190428-17:24:00] [DEBUG] Testing if xrdp-sesman can listen on 127.0.0.1 port 3350.
[20190428-17:24:00] [INFO ] starting xrdp-sesman with pid 7991
[20190428-17:24:00] [DEBUG] Closed socket 5 (AF_INET6 ::ffff:127.0.0.1 port 3350)
[20190428-17:24:00] [INFO ] listening to port 3350 on 127.0.0.1

the network information is here

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.108.117.111  netmask 255.255.252.0  broadcast 10.108.119.255
        inet6 fe80::5a75:489:3f49:e3e5  prefixlen 64  scopeid 0x20<link>
        inet6 2001:da8:215:81d:cdad:bf36:a2e1:a235  prefixlen 64  scopeid 0x0<global>
        inet6 2001:da8:215:81d:4f45:757a:b58f:d4f8  prefixlen 64  scopeid 0x0<global>
        ether 64:00:6a:86:13:b3  txqueuelen 1000  (以太网)
        RX packets 77669  bytes 36956095 (36.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36428  bytes 6539713 (6.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7f00000-f7f20000

I tried to disable firewall, but it doesn’t helps.

I checked the sesman and it is active

● xrdp-sesman.service - xrdp session manager
   Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-04-28 18:13:26 CST; 1h 50min ago
     Docs: man:xrdp-sesman(8)
           man:sesman.ini(5)
 Main PID: 21122 (xrdp-sesman)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/xrdp-sesman.service
           └─21122 /usr/sbin/xrdp-sesman

I use google to seach the same error but there is not much information about it .

blow is the detail of config files

Here is the information of xrdp.ini

[Globals]
ini_version=1

fork=true
port=3389
use_vsock=false
tcp_nodelay=true
tcp_keepalive=true
security_layer=negotiate
crypt_level=high
certificate=
key_file=
ssl_protocols=TLSv1, TLSv1.1, TLSv1.2
autorun=

allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
max_bpp=32
new_cursors=true

use_fastpath=both

blue=009cb5
grey=dedede

ls_top_window_bg_color=009cb5

ls_width=350
ls_height=430

ls_bg_color=dedede

ls_logo_filename=
ls_logo_x_pos=55
ls_logo_y_pos=50

ls_label_x_pos=30
ls_label_width=60

ls_input_x_pos=110
ls_input_width=210

ls_input_y_pos=220

ls_btn_ok_x_pos=142
ls_btn_ok_y_pos=370
ls_btn_ok_width=85
ls_btn_ok_height=30

ls_btn_cancel_x_pos=237
ls_btn_cancel_y_pos=370
ls_btn_cancel_width=85
ls_btn_cancel_height=30

[Logging]
LogFile=xrdp.log
LogLevel=DEBUG
EnableSyslog=true
SyslogLevel=DEBUG

[Channels]
rdpdr=true
rdpsnd=true
drdynvc=true
cliprdr=true
rail=true
xrdpvr=true
tcutils=true

[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
code=20

[X11rdp]
name=X11rdp
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
xserverbpp=24
code=10

[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask
ip=127.0.0.1
port=-1

[console]
name=console
lib=libvnc.so
ip=127.0.0.1
port=5900
username=na
password=ask

[vnc-any]
name=vnc-any
lib=libvnc.so
ip=ask
port=ask5900
username=na
password=ask

[sesman-any]
name=sesman-any
lib=libvnc.so
ip=ask
port=-1
username=ask
password=ask
#delay_ms=2000

[neutrinordp-any]
name=neutrinordp-any
lib=libxrdpneutrinordp.so
ip=ask
port=ask3389
username=ask
password=ask

and here is the sesman.ini

[Globals]
ListenAddress=127.0.0.1
ListenPort=3350
EnableUserWindowManager=true
UserWindowManager=startwm.sh
DefaultWindowManager=startwm.sh

[Security]
AllowRootLogin=true
MaxLoginRetry=4
TerminalServerUsers=tsusers
TerminalServerAdmins=tsadmins
AlwaysGroupCheck=false

[Sessions]
X11DisplayOffset=10


MaxSessions=50

KillDisconnected=false
DisconnectedTimeLimit=0
Policy=Default

[Logging]
LogFile=xrdp-sesman.log
LogLevel=DEBUG
EnableSyslog=1
SyslogLevel=DEBUG



param=/usr/lib/xorg/Xorg
param=-config
param=xrdp/xorg.conf
param=-noreset
param=-nolisten
param=tcp
param=-logfile
param=.xorgxrdp.%s.log

[Xvnc]
param=Xvnc
param=-bs
param=-nolisten
param=tcp
param=-localhost
param=-dpi
param=96

[Chansrv]
FuseMountName=thinclient_drives

[SessionVariables]
PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
Источник

Содержание

  1. CentOS
  2. Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  3. Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  4. Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  5. Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  6. Vnc Error — Problem Connecting #2086
  7. Comments
  8. login successful for display 10. VNC error — problem connecting some problem #1459
  9. Comments

CentOS

The Community ENTerprise Operating System

Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by BGood » 2017/01/08 20:00:10

With the help of Centos forum resources, I added GUI (MATE Desktop) support to a dedicated Centos 7 web server (Centos 7 Live DVD — Can Gnome/GUI be installed later? viewtopic.php?f=47&t=60762).

While the MATE desktop is a convenient addition to the main server console, I would also like to provide remote GUI capability to my main workstation which is a Windows 7 desktop. I am trying to connect remotely to the MATE desktop using a Windows Remote Desktop client on the Windows side and xrdp on the Centos side, but am encountering a «some problem» VNC connection error which I think is coming from the Centos side:

Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by BGood » 2017/01/09 17:21:48

Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by FAB5FLAVE » 2017/08/23 15:19:27

Installed xdrp and tigervnc windows RDP connected no problem.

Installed MATE Desktop got the same «some problem» error when trying to connect.

Tried numerous things to get this working like changing port number, reinstalling xdrp and tigervnc etc.

Eventually resolved the issue by removing xrdp and tigervnc and reinstalling

yum remove xrdp
yum remove tigervnc-server.x86_64
yum remove tigervnc-server-minimal.x86_64
reboot

systemctl start xrdp

Didn’t start
systemd[1]: Started xrdp daemon.
systemd[1]: Starting xrdp daemon.
systemd[3144]: Failed at step EXEC spawning /usr/sbin/xrdp: Permission denied
systemd[1]: xrdp.service: main process exited, code=exited, status=203/EXEC
systemd[1]: Unit xrdp.service entered failed state.
systemd[1]: xrdp.service failed.

So ran the following
chcon -t bin_t /usr/sbin/xrdp
chcon -t bin_t /usr/sbin/xrdp-sesman

Источник

Vnc Error — Problem Connecting #2086

Im experiencing the following error with the tool xrdp in a suse 15 sp1 machine in azure, I just wanna know is someone has seen it before.

Please wait, we now perform access control.
Reply from access control: Sucess
connecting to sesman ip 127.0.0.01 port 3350
seman connect ok
sending login info to session manager, please wait.
login successful for display 201
VNC started connecting
waiting 2000 ms for VNC to start.
VNC connecting to 127.0.0.1 6101
VNC error — problem connecting
some problem

The text was updated successfully, but these errors were encountered:

@jsanchezzz — these two lines look odd:-

Have you changed the X11DisplayOffset=10 setting in sesman.ini? It looks like it’s set to around 200, which probably won’t work.

@jsanchezzz — do you need any more help with this?

@matt335672 yes, I reinstalled the xrdp, but it showing the same error. Also I did not change the X11DisplayOffset=10, how can i see if the X11DisplayOffset has changed somehow?

It’s in /etc/xrdp/sesman.ini :-

Hello as you said the X11DisplayOffset is set to 200, and we dont know why? could you tell us how to change it to 10, please? see the image attached.

Well, you seem to have two problems here

The first problem is solved by editing /etc/xrdp/sesman.ini , correcting the value, and restarting the xrdp-sesman service.

The second and more serious problem is that you’ve got a file on your system which needs privilege to change and something unknown has changed it. That’s not a good position to be in. Not only do we not know what else might have changed in the xrdp configuration, but there might be other files which have changed that could affect system operation. So I think it’s worth trying to figure out how this file could have changed.

We changed the parameter but it did not work, We did a deeper investigation to know why the rdp is not working and we entered the logs, we saw something about a certificate, I would like to know if you have any knowledge, because the certificate is installed but the vm does not find it.

see the images attached and the notepad.
log JS.txt

If you don’t have a certificate, xrdp will fall back on a less secure connection method, so I’d expect it still to work. I think you should leave that for now.

A couple of questions for you:-

  • What version of xrdp is installed?
  • What desktop have you installed on the machine?

What version of xrdp is installed?

What desktop have you installed on the machine?

linux suse 15 sp1

«Linux SuSE 15 sp 1» isn’t what I’d call a desktop. I mean, are you running GNOME or KDE (or similar)? You’ll need a desktop installed for xrdp to start. Do you have one installed?

As far as the certificate error goes

I’ve checked the sources for 0.9.6 and it’s telling me that either /etc/xrdp doesn’t exist on that machine, or /etc/xrdp/cert.pem doesn’t exist on that machine. What do you get on the machine for these two command when logged in as root:-

We solved the problem:

1 — Performing a clean installation of patterns-gnome-gnome_basic
2 — Allowing remote sesion with remote manager
3 — Installing xrdp xorgxrdp
4 — enabling the vm firewall and open the port 3389 ( systemctl enable firewalld, systemctl startd firewalld firewall-cmd —permanent —zone=public —add-port=3389/tcp )

Thanks for you support, it was rellay heplful to solve the issue.

Thanks for letting us know.

Did you get your certificate problem sorted out too?

Jumping into this conversation 3 years later.

I’m not asking a question here, but trying to add something to the quoted observation below:

The second and more serious problem is that you’ve got a file on your system which needs privilege to change and something unknown has changed it. That’s not a good position to be in. Not only do we not know what else might have changed in the xrdp configuration, but there might be other files which have changed that could affect system operation. So I think it’s worth trying to figure out how this file could have changed.
— matt335672

I’ve observed the same issue. The configuration at /etc/xrdp/sesman.ini says that the default is 10 but I see 200.
I’m not sure what changed this configuration.

However, I’ve observed something peculiar:

I’m running OpenSUSE Tumbleweed in a VM under Hyper-V under Windows11. Unfortunately I have to use Windows 🙁

I have GWSL, which is a Xserver with some tweaks intended to make life easier if you are using WSL. But I’m not using OpenSUSE under WSL; I’m using OpenSUSE under a VM, under Hyper-V.

Then I have two choices for opening a RDP session: (a) using GWSL or (b) using Remote Desktop Connection, which is native to Windows11.

I’ve discovered that GWSL employs/requires DISPLAY=:10.0 whilst Windows Remote Desktop Connection employs/requires DISPLAY=:200.0

I can open KDE full screen using GWSL, but I have to open first a ssh session and then run startplasma-x11 from it, which is inconvenient, but works.

However, I cannot open KDE full screen using Windows Remote Desktop Connection. But I’ve discovered that it starts to work fine if I first open a GWSL connection. In other words: if I open first a window with KDE in it via GWSL, after that, I can open another window running KDE in it via Windows Remote Desktop Connection. In this case, applications running in the first window employ DISPLAY=:10.0 whilst application in the second window employ DISPLAY=:200.0 .

Needless to say that I don’t understand why it behaves this way.

Seems like the RDP server for display 10 works like a transport layer for the RDP server for display 200. The evidence is: if I close the RDP server for display 10 (i.e.: I close GWSL), the window containing applications associated to display 200 stop working after 10 seconds and the entire KDE session dies.

I would prefer to use WIndow Remote Desktop Server, since it performs better. But, as explained, it will require GWSL for some unknown reason. which forces me to use GWSL anyway.

Trying to answer the question «who changed X11DisplayOffset=10 to X11DisplayOffset=200». my guess is package hyper-v , installed automatically on OpenSUSE when the VM is first installed. I’m not sure though. Just a guess.

Источник

login successful for display 10. VNC error — problem connecting some problem #1459

I have installed and used xrdp on a centos 7.0 + gnome. I used this resource https://draculaservers.com/tutorials/install-xrdp-centos/ for install xrdp.
I always used session Xorg for login because of xrdp never worked with Xvnc session

A few days ago I have updated a linux with command sudo yum update
After the update, the menu Xorg disappeared from Session list and when I used Xvnc session I get an error — Login successful for display 10. VNC error — problem connecting some problem

I googled a lot and read and tried a lot of solutions for the fix issue but without success.

The text was updated successfully, but these errors were encountered:

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.

I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.

I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

The issue was not solved.

]# rpm -q centos-release
centos-release-7-7.1908.0.el7.centos.x86_64

]# getenforce
Enforcing
[root@localhost

]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31
[root@localhost

I have installed:
xrdp-selinux.x86_64 1:0.9.11-5.el7

I have added the sesman.ini file to this post.
sesman.txt

Output for Xvnc :10
[root@localhost

Xvnc TigerVNC 1.8.0 — built Aug 9 2019 03:04:19
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12001000, The X.Org Foundation

Tue Dec 17 11:24:38 2019
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5910
vncext: created VNC server for screen 0

Where and how can I change the colour depth?

Xorg still is not available in the session list.

I’m using Mate desktop. Gnome desktop worked under root account without any issue till yum update.

I just realized I gave you some duff info about the session list — apologies. The session list is stored in /etc/xrdp/xrdp.ini , and not /etc/xrdp/sesman.ini .

If you look in xrdp.ini at around line 181, you should find the following commented-out section:-

Remove the ‘#’ line prefixes and restart the xrdp service. That should give you your Xorg session back.

To run Xorg, you’ll need xorgxrdp installed, but you probably already have that if it was working before.

Colour depth is available (in the Windows client) on the ‘Display’ tab:-

Let us know if that’s useful.

  1. I have edit the /etc/xrdp/xrdp.ini and uncommented this strings
    #[Xorg]
    #name=Xorg
    #lib=libxup.so
    #username=ask
    #password=ask
    #ip=127.0.0.1
    #port=-1
    #code=20

I have restarted the server

When I’m trying connect by rdp — I see an only a black screen. Doesn’t matter which color I use -15 or 32 bits.

  1. I have added the new logs.
    Xorg.0.log
    xrdp.log
    xrdp-sesman.log
    yum.log

I wasn’t familiar with MATE, so I’ve gone away and had a look at it.

Can you try the following:-

  • Make sure the whole MATE desktop is installed with yum groupinstall «MATE Desktop» . It’s possible you’ve only got the mate-desktop RPM installed which isn’t enough.
  • Issue this command as the user you’re trying to log in as to set your default session.

Then have another go.

If you’re still having problems, post the output of the file

/.xsession-errors. This file is (or should be) created when the user logs on and runs the session.

Let us know how it goes.

We have a small progress.

List of installed Groups
Installed Environment Groups:
MATE Desktop
Available Environment Groups:
Minimal Install
Compute Node
Infrastructure Server
File and Print Server
Cinnamon Desktop
Basic Web Server
Virtualization Host
Server with GUI
GNOME Desktop
KDE Plasma Workspaces
Development and Creative Workstation
Installed Groups:
MATE
Available Groups:
Cinnamon
Compatibility Libraries
Console Internet Tools
Development Tools
Educational Software
Electronic Lab
Fedora Packager
General Purpose Desktop
Graphical Administration Tools
Haskell
LXQt Desktop
Legacy UNIX Compatibility
Milkymist
PostgreSQL Database Server 10 PGDG
PostgreSQL Database Server 11 PGDG
PostgreSQL Database Server 12 PGDG
PostgreSQL Database Server 9.4 PGDG
PostgreSQL Database Server 9.5 PGDG
PostgreSQL Database Server 9.6 PGDG
Scientific Support
Security Tools
Smart Card Support
System Administration Tools
System Management
TurboGears application framework
Xfce

Sessions files
-rwxr-xr-x. 1 root root 13 Dec 18 09:42 /root/.Xclients


-rwxr-xr-x. 1 root root 13 Dec 18 09:43 /root/.xsession

After run command bellow I saw the normal RDP screen with Xvnc, Xorg. I tried to login, but the login process stuck. After a few minutes the rdp returned the error

ln -sf /usr/bin/mate-session

  1. Xsession log files
    xsession-errors.txt

The session log shows the desktop is starting. The RDP log shows that XRDP is unable to connect to the X server.

  • Does the same thing happen with both Xvnc and Xorg back ends?
  • For Xorg, have you definitely got the xorgxrdp RPM installed?
  • Xorg generates a log file in

/.xorgxrdp. .log . So for the above example where display 11 is being used, the log file is in

/.xorgxrdp.11.log . If you’re having problems with Xorg, please post the contents of this file.
On CentOS 7, the Xvnc log is stored by journalctl along with stderr from xrdp-sesman (which is not the same as /var/log/xrdp-sesman.log ). If you’re having problems with Xvnc, please post the output of the following command (run as root), which displays the last 3 minutes of this output:-

I have installed xorgxrdp and now everything works properly .
Thank you for your attention and support.

Thanks for letting us know — I’m glad we got there between us.

I’ll just summarize and expand on this thread for anyone else reading this, who is trying to get an alternative desktop working on a fresh install of the latest CentOS 7. The webpage you linked to is pretty good, but it’s missing some small details like SELinux support and the need for xorgxrdp . I’ve also added some of my own sysadmin experiences.

At the time of writing, the following versions apply:-

Software Version
CentOS 7.7
xrdp RPM 0.9.11-5
xorgxrdp RPM 0.2.11-1

Ensure the OS is up to date with sudo yum update

Install EPEL repository with sudo yum install epel-release

Install and enable XRDP with:-

If you’re using the firewall, allow external access to TCP port 3389 with:-

If you’re using SELinux, sudo yum install xrdp-selinux

If you want to use the Xorg backend in addition to (or instead of) the Xvnc backend, do the following. The differences between the two backends are covered elsewhere.

  • sudo yum install xorgxrdp
  • Edit /etc/xrdp/xrdp.ini . If the [Xorg] section is commented out, uncomment it.
  • If you changed xrdp.ini , sudo systemctl restart xrdp to pick up the changes.

Install your desktop(s), making sure that you use a command to install the whole desktop rather than a subset of it. This will probably be a yum groupinstall command. For example, for MATE, use sudo yum groupinstall «MATE Desktop» .

The default desktop for XRDP on CentOS 7 is GNOME. If you want the default desktop for all XRDP users to be something else, create the file /etc/sysconfig/desktop and set the PREFERRED variable to the command to start the desktop. For example, this /etc/sysconfig/desktop sets the default desktop to MATE for all XRDP users:-

XRDP users who want to use a desktop other than the default will need to soft-link the command to start the correct session in to

/.Xclients . For MATE, this command is adequate:-

As an aside, some websites suggest creating a vanilla file

/.xsession containing the command to start the desktop. That’s OK too, but you have to remember to make the file executable. The soft-link method avoids this pitfall.

That should get the desktop running. Here are a couple of gotchas:-

    Some desktops expect GDM to be running to provide some of their functionality over DBUS. For example, the GNOME lock screen is implemented in GDM. If you’re using one of these desktops you may need to enable GDM on the machine console (if it isn’t enabled already):-

I think that’s it, but please let me know if I’ve left anything out.

Does anyone think this would be useful as a Wiki page by the way?

What if you add this instruction into Readme file — at the paragraph troubleshooting?

I see what you mean — there are very brief instructions in the README.md which appears on the front page on Github.

What might make more sense is to link from the README.md to the Wiki, as the Wiki can be updated more easily than README.md. I’ll do some more research (after Xmas probably) and try to get something together which has instructions for all desktops.

Maybe it is interesting, but on Fedora 30/31, I am facing the same issue (exact same displayed message), but only for corporate users.
With local created users, it works.
I am using Xvnc.

Hello,
I had the same situation, Xvnc broken when rendering NVIDIA didn’t work through VNC for old technology.
I installed tigerVnc and running this command:
tigervncserver -localhost no
Viewer Vnc:
vncviewer ip:1
e.g. 192.168.1.1:1

Hello, I am facing a RDP issue from Windows 10 to RHEL8 trying both Xvnc and Xorg. Using either option, after entering credentials and selecting OK, the RDP session immediately closes. For users who were on the system previously and had their sessions time out, they can still RDP into the machine, but all other users can not start a RDP session successfully. Any ideas?

@rja1972 — please start a new thread. I can’t see any similarities between this issue and what you are describing.

Knowing what OS you are on, and what your xrdp version is would be useful.

I’m closing this thread now, as the issue raised by the OP was addressed. Please feel free to raise a new issue if you’ve posted above and you still need help getting something working.

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

  • When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.
  • I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.
  • I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

You are right. I am running CentOS Stream 9 and encounter the same problem. Able to connect after setting the depth to 32 in my RDP client despite the fact that I am connecting as root.

Источник

Источник

Я на компьютере с Windows 7 пытаюсь получить доступ к системе RHEL7 через удаленный рабочий стол Windows.

До сегодняшнего дня я (и другие в моем отделе) был в состоянии войти в систему RHEL, используя xrdp.

Сегодня внезапно xrdp начал отклонять соединения. Я вижу зеленый фоновый экран входа в систему, но он отклоняет учетные данные (и это нормально).

Я могу пропинговать сервер, подключиться через putty и использовать filezilla, но подключение к удаленному рабочему столу отклоняет вход в сеанс.

Я также попытался подключиться через удаленный рабочий стол к другому компьютеру CENTOS, и он работает нормально.

Есть идеи?

РЕДАКТИРОВАТЬ:

~/.xsession-errors :

gnome-session-is-accelerated: llvmpipe detected.

/var/log/xrdp.log:

[20171031-13:55:53] [DEBUG] TLSv1.2 enabled
[20171031-13:55:53] [DEBUG] TLSv1.1 enabled
[20171031-13:55:53] [DEBUG] TLSv1 enabled
[20171031-13:55:53] [DEBUG] Security layer: requested 3, selected 1
[20171031-13:55:53] [INFO ] connected client computer name: SPENATE7
[20171031-13:55:53] [INFO ] TLS connection established from 192.168.197.176 port 51321: TLSv1.2 with cipher AES256-GCM-SHA384
[20171031-13:55:53] [DEBUG] xrdp_00007c0e_wm_login_mode_event_00000001
[20171031-13:55:53] [INFO ] Loading keymap file /etc/xrdp/km-0000040a.ini
[20171031-13:55:53] [WARN ] local keymap file for 0x0000040a found and doesn't match built in keymap, using local keymap file
[20171031-13:55:58] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20171031-13:55:59] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20171031-13:55:59] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20171031-13:55:59] [DEBUG] return value from xrdp_mm_connect 0
[20171031-13:56:05] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20171031-13:56:05] [DEBUG] xrdp_mm_module_cleanup
[20171031-13:56:05] [DEBUG] Closed socket 18 (AF_INET 127.0.0.1:46890)

/var/log/xrdp-sesman.log :

[20171031-12:58:20] [ERROR] X server -- no display in range is available
[20171031-12:58:20] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350)
[20171031-13:01:28] [INFO ] shutting down sesman 1
[20171031-13:01:28] [DEBUG] Closed socket 7 (AF_INET 127.0.0.1:3350)
[20171031-13:01:29] [CORE ] shutting down log subsystem...
[20171031-13:01:29] [DEBUG] libscp initialized
[20171031-13:01:29] [INFO ] starting xrdp-sesman with pid 14292
[20171031-13:01:29] [INFO ] listening to port 3350 on 127.0.0.1
[20171031-13:01:41] [INFO ] A connection received from 127.0.0.1 port 35854
[20171031-13:01:41] [INFO ] ++ created session (access granted): username sanpen, ip 192.168.197.176:60904 - socket: 12
[20171031-13:01:41] [INFO ] starting Xvnc session...
[20171031-13:01:41] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910)
[20171031-13:01:41] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6010)
[20171031-13:01:42] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6210)
[20171031-13:01:42] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5911)
[20171031-13:01:42] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6011)
[20171031-13:01:42] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6211)

Источник

  • Summary

  • Files

  • Reviews

  • Support

  • Wiki

  • Tickets ▾

    • Feature Requests
    • Bugs
    • Support Requests
    • Patches

  • Discussion

  • Donate

  • Code

Menu
▾
▴

error — problem connecting


Created:

2006-02-23

Updated:

2013-06-05

  • BriggsBFC

    The Connection Log in the rdesktop window on the client shows:

    :
    receiving sesman data
    sesman started a session
    connecting to 127.0.0.1 5910
    error — problem connecting

    Can anyone give me a pointer?

    Thanks,

    BriggsBFC

    • John Chajecki

      Yep! Getting exactly the same. Was going to post but yopu beat me to it!

      If anyone could give us a pointer it would be appreciated.

      John.

    • John Chajecki

      PS, I can connect to my Linux desktop using VNC using ip.ip.ip.ip:1.

      When I try to connect using sesman or sesman-xrdp I get:

      started connecting
      connecting to sesman
      sending login info to sesman
      receiving sesman header
      receiving sesman data
      error — sesman returned no
      error — connection failed

      Does this indicate a problem with pam?
      Do I need to set up a pam config file for xrdp?

    • Jay Sorg

      When sessman returns no, it means the accout is disabled or some pam problem.

      xrdp should install a pam file /etc/pam.d/sesman

      When you get the problem connecting error it useually mean you need to edit startwm.sh

      Jay

    • John Chajecki

      Jay,

      Thanks. It was a pam issue. There was no sesman in /etc/pam.d/. You see I had a problem compiling sesman. I was able to compile each other module individually. I eventually solved the sesman issue by installing the pam-devel library corresponding to the pam version I had on my system.

      Reading your comments, I ran male install from the top level source directory and hey presto, a sesman file was indeed created in /etc/pam.d by the installer.

      Everything now works.

      One question: whats the difference between using sesman and sesman-xdrp? The later does not work and returns ‘some error’.

      • Jay Sorg

        sesman starts a Xvnc session

        sesman-Xrdp starts a Xrdp sesion.
        Xrdp is an rdp specific X server.  Still in testing.

        Jay

    • BriggsBFC

      My problem was a little bit different, it was VNC related.

      I changed an entry in the /etc/xrdp.ini file under [xrdp1]

      from:
      port=-1

      to:
      port=5901

      This solved my problem, though I must admit I don’t know exactly why!

    • Richard Ward

      I get the:
      receiving sesman data
      sesman started a session
      connecting to 127.0.0.1 5910
      error — problem connecting

      error. I tried changing the startwm.sh to just say
      #!/bin/bash
      gnome-session

      and I tried changing port to 5910 in xrdp.ini (under xrdp1). still not working (I’m on ubuntu dapper btw).

    • Jay Sorg

      Ubuntu usually has a problem starting the Xvnc.
      To see if this is your problem go to a command prompt and type ‘Xvnc :10’
      See if erros out.

      Jay

    • Cris

      Jay

      Ubuntu does have this problem as stated in bug 3593
      https://launchpad.net/distros/ubuntu/+source/vnc4/+bug/3593

      When i launch Xvnc with the option -fp /usr/share/fonts/X11/misc/ it works properly for me. for my personal purposes i would like to change the source code to launch the VNC server with this option. Unfortunately i am not a programmer, and after flipping through the code, i was unable to find where i would change this. Could you, our someone else point me in the right direction?

      Again, i just want to change my copy and recompile, not the CVS version. I am excited about the idea of connecting to my Ubuntu box with mstsc, and i am unwilling to change distros. 

      knowing enough to be dangerous..

      Cris

    • Jay Sorg

      I think you can just create a symolic link to fix this problem.

      Jay

    • Robert Citek

      I’ve tried every one of the above suggestions and in various combinations, yet still no luck connecting using Terminal Server Client 0.140 and xrdp-0.3.2 on Ubuntu 6.06.1 (dapper).  The client and server are running on the same machine (localhost).

      I’m starting xrdp with ‘/usr/local/xrdp/xrdp_control.sh start’ which creates two processes: xrdp and sesman.  When I connect I use Applications > Internet > Terminal Server Client with the following setings: computer -> localhost, protocol -> RDP, username -> foobar.  All other fields are blank.  When I click connect I’m presented with a login window (module -> sesman, username -> foobar) at which I type my password.  A «Connection Log» window appears and I hear the familiar Ubuntu login sounds.  In the login are these lines:

      started connecting
      connecting to sesman
      sending login info to sesman
      receiving sesman header
      receiving sesman data
      sesman started a session
      connecting to 127.0.0.1 5910
      error — problem connecting

      How should I be thinking about trouble shooting the problem?  For example, what logs should I be looking at?  What tests can I run to verify that any settings I have are correct?  What tests can I run to be sure any dependent programs are installed and configured correctly, e.g. Xvnc?

      Regards,
      — Robert

      • Robert Citek

        I failed to mentioned that my original /usr/local/xrdp/startwm.sh file looked like this:

        #!/bin/bash
        # gnome
        if [ «‘which gnome-session'» != «» ]; then
          gnome-session
          exit 0
        fi

        When I changed it to this:

        #!/bin/bash
        # fall back on xterm
        if [ «‘which xterm'» != «» ]; then
          xterm
          exit 0
        fi

        I was able to connect, although the only window displaying was an xterm.

        How can I troubleshoot why gnome-session is not starting?

        Regards,
        — Robert

        • Robert Citek

          From within the xterm I thought I’d try starting a gnome-session:

          ( gnome-session ) >& rdp.err.log

          Here’s the contents from rdp.err.log:

          Bonobo accessibility support initialized
          GTK Accessibility Module initialized
          SESSION_MANAGER=local/foobar:/tmp/.ICE-unix/7311
          GTK Accessibility Module initialized
          Bonobo accessibility support initialized
          GTK Accessibility Module initialized
          GTK Accessibility Module initialized
          The program ‘gnome_segv2’ received an X Window System error.
          This probably reflects a bug in the program.
          The error was ‘BadMatch (invalid parameter attributes)’.
            (Details: serial 500 error_code 8 request_code 72 minor_code 0)
            (Note to programmers: normally, X errors are reported asynchronously;
             that is, you will receive the error a while after causing it.
             To debug your program, run it with the —sync command line
             option to change this behavior. You can then get a meaningful
             backtrace from your debugger if you break on the gdk_x_error() function.)
          Window manager warning: Log level 32: could not find XKB extension.

          (gok:7327): GnomeUI-WARNING **: While connecting to session manager:
          IO error occured opening connection.
          Bonobo accessibility support initialized

          ** (gok:7327): WARNING **: Xkb extension could not be initialized! (error code 3)

          ** (gok:7327): WARNING **: keyboard description not available!

          I seem to be out of my league now.   Any pointers greatly appreciated.

          Regards,
          — Robert

    • Dan1K

      >The Connection Log in the rdesktop window on the client shows:
      >
      >:
      >receiving sesman data
      >sesman started a session
      >connecting to 127.0.0.1 5910
      >error — problem connecting
      >
      >Can anyone give me a pointer?
      >
      >Thanks,
      >
      >BriggsBFC

      Same problem with my Kubuntu7.04.
      try «sudo apt-get install vncserver», then «sudo /…/…/xrdp_control.sh restart» and problem solved.
      hope help.

      Thanks again for this great project ;)

Log in to post a comment.

Источник

Hi,

Im trying to connect to my Debian machine from my Windows host but I cant get it to work, I have installed both xrdp and x11vnc. I don’t know the reason as to why I can’t connect. The machine is listening on the TCP ports.

xrdp.log:

Code: Select all

dave@hal9000:/var/log$ sudo cat xrdp.log
[20180219-19:34:37] [INFO ] starting xrdp with pid 2189
[20180219-19:34:37] [INFO ] listening to port 3389 on 0.0.0.0
[20180219-19:34:52] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55533
[20180219-19:34:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:34:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:34:53] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:34:53] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:34:53] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:53] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:34:54] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55534
[20180219-19:34:54] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:54] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:34:54] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:34:54] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:34:54] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:34:54] [DEBUG] xrdp_000009d7_wm_login_mode_event_00000001
[20180219-19:34:54] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:34:54] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:35:08] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:35:08] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:35:08] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: started connecting
[20180219-19:35:12] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:19] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:26] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:33] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:40] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:44] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:47] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:51] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:54] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:58] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:01] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:05] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:08] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:12] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:19] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:26] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:33] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:40] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:43] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:47] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:50] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:54] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:57] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:01] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:04] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:08] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:11] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:18] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:25] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:32] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:39] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55550
[20180219-19:37:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:39] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:37:39] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:37:39] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:37:39] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:37:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:39] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:37:39] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:41] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55551
[20180219-19:37:41] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:41] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:37:41] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:37:41] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:37:41] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:37:41] [DEBUG] xrdp_00000a3a_wm_login_mode_event_00000001
[20180219-19:37:41] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:37:41] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:37:43] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:46] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:50] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:53] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:57] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:00] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:04] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:07] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:11] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:18] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:25] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:32] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:35] [INFO ] A connection received from: ::ffff:172.10.88.6 port 57082
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:35] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:35] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:35] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:38:35] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:35] [DEBUG] Closed socket 16 (AF_INET6 ::ffff:172.10.88.6 port 57082)
[20180219-19:38:35] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:35] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:39] [DEBUG] xrdp_wm_log_msg: connection problem, giving up
[20180219-19:38:39] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:39] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:38:39] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:39] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51520)
[20180219-19:38:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:39] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:39] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:52] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55557
[20180219-19:38:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:52] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:52] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:38:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:52] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:53] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55558
[20180219-19:38:53] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:53] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:53] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:53] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:53] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:38:53] [DEBUG] xrdp_00000a62_wm_login_mode_event_00000001
[20180219-19:38:53] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:38:53] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:43:56] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:43:57] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:43:57] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:43:57] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180219-19:44:00] [DEBUG] VNC error 1 after security negotiation
[20180219-19:44:00] [DEBUG] VNC error before sending share flag
[20180219-19:44:00] [DEBUG] VNC error before receiving server init
[20180219-19:44:00] [DEBUG] VNC error before receiving pixel format
[20180219-19:44:00] [DEBUG] VNC error before receiving name length
[20180219-19:44:00] [DEBUG] VNC error before receiving name
[20180219-19:44:00] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:44:00] [DEBUG] Closed socket 17 (AF_INET6 :: port 40824)
[20180219-19:44:00] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:44:00] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:44:00] [DEBUG] VNC mod_exit
[20180219-19:44:00] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51526)
[20180219-19:47:42] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:47:42] [DEBUG] xrdp_wm_log_msg: VNC connecting to 172.10.88.6 3350
[20180219-19:47:45] [DEBUG] VNC error 1 after security negotiation
[20180219-19:47:45] [DEBUG] VNC error before sending share flag
[20180219-19:47:45] [DEBUG] VNC error before receiving server init
[20180219-19:47:45] [DEBUG] VNC error before receiving pixel format
[20180219-19:47:45] [DEBUG] VNC error before receiving name length
[20180219-19:47:45] [DEBUG] VNC error before receiving name
[20180219-19:47:45] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:47:45] [DEBUG] Closed socket 16 (AF_INET6 :: port 57536)
[20180219-19:47:45] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:47:45] [ERROR] xrdp_wm_log_msg: Error connecting to: 172.10.88.6
[20180219-19:47:45] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:47:45] [DEBUG] VNC mod_exit
[20180219-19:47:45] [DEBUG] return value from xrdp_mm_connect 1
[20180219-19:47:51] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:47:51] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:47:51] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:48:07] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55674
[20180219-19:48:07] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:07] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:48:07] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:48:07] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:48:07] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:48:07] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:07] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:48:08] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55675
[20180219-19:48:08] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:08] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:48:08] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:48:08] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:48:08] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:48:08] [DEBUG] xrdp_00000cbd_wm_login_mode_event_00000001
[20180219-19:48:08] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:48:08] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:48:30] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:48:31] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:48:31] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:48:31] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:48:32] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20180219-19:48:32] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:48:32] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51540)
[20180219-19:48:56] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:56] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:48:56] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:49:01] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:24] [INFO ] starting xrdp with pid 654
[20180219-19:50:24] [INFO ] listening to port 3389 on 0.0.0.0
[20180219-19:50:34] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55696
[20180219-19:50:34] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:34] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:34] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:50:34] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:50:34] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:50:34] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:34] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:50:35] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55697
[20180219-19:50:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:35] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:35] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:50:35] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:50:35] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:50:35] [DEBUG] xrdp_000004aa_wm_login_mode_event_00000001
[20180219-19:50:35] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:50:35] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:50:51] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:50:52] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:50:52] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:50:52] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:50:54] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20180219-19:50:54] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:50:54] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 34254)
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:51:32] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:51:32] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:51:32] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180219-19:51:35] [DEBUG] VNC error 1 after security negotiation
[20180219-19:51:35] [DEBUG] VNC error before sending share flag
[20180219-19:51:36] [DEBUG] VNC error before receiving server init
[20180219-19:51:36] [DEBUG] VNC error before receiving pixel format
[20180219-19:51:36] [DEBUG] VNC error before receiving name length
[20180219-19:51:36] [DEBUG] VNC error before receiving name
[20180219-19:51:36] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:51:36] [DEBUG] Closed socket 17 (AF_INET6 :: port 43916)
[20180219-19:51:36] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:51:36] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:51:36] [DEBUG] VNC mod_exit
[20180219-19:51:36] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 34268)

xrdp-sesman.log:

Code: Select all

dave@hal9000:/var/log$ sudo cat xrdp-sesman.log
[20180219-19:34:35] [DEBUG] libscp initialized
[20180219-19:34:35] [INFO ] starting xrdp-sesman with pid 2177
[20180219-19:34:35] [INFO ] listening to port 3350 on 127.0.0.1
[20180219-19:35:08] [INFO ] A connection received from ::1 port 51520
[20180219-19:35:08] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55534 - socket: 12
[20180219-19:35:08] [INFO ] starting Xorg session...
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:35:08] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:35:08] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:35:08] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
[20180219-19:35:18] [ERROR] X server for display 10 startup timeout
[20180219-19:35:18] [INFO ] starting xrdp-sessvc - xpid=2534 - wmpid=2533
[20180219-19:35:18] [ERROR] X server for display 10 startup timeout
[20180219-19:35:18] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:35:18] [DEBUG] aborting connection...
[20180219-19:35:18] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 2532, ip 0.0.0.0:55534 - socket: 12
[20180219-19:43:56] [INFO ] A connection received from ::1 port 51526
[20180219-19:43:57] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55558 - socket: 12
[20180219-19:43:57] [INFO ] starting Xvnc session...
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:43:57] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:43:57] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:43:57] [INFO ] Xvnc :10 -auth .Xauthority -geometry 3440x1440 -depth 32 -rfbauth /home/dave/.vnc/sesman_dave_passwd:10 -bs -nolisten tcp -localhost -dpi 96
[20180219-19:43:57] [CORE ] error starting X server - user dave - pid 3131
[20180219-19:43:57] [DEBUG] errno: 2, description: No such file or directory
[20180219-19:43:57] [DEBUG] execve parameter list size: 17
[20180219-19:43:57] [DEBUG]         argv[0] = Xvnc
[20180219-19:43:57] [DEBUG]         argv[1] = :10
[20180219-19:43:57] [DEBUG]         argv[2] = -auth
[20180219-19:43:57] [DEBUG]         argv[3] = .Xauthority
[20180219-19:43:57] [DEBUG]         argv[4] = -geometry
[20180219-19:43:57] [DEBUG]         argv[5] = 3440x1440
[20180219-19:43:57] [DEBUG]         argv[6] = -depth
[20180219-19:43:57] [DEBUG]         argv[7] = 32
[20180219-19:43:57] [DEBUG]         argv[8] = -rfbauth
[20180219-19:43:57] [DEBUG]         argv[9] = /home/dave/.vnc/sesman_dave_passwd:10
[20180219-19:43:57] [DEBUG]         argv[10] = -bs
[20180219-19:43:57] [DEBUG]         argv[11] = -nolisten
[20180219-19:43:57] [DEBUG]         argv[12] = tcp
[20180219-19:43:57] [DEBUG]         argv[13] = -localhost
[20180219-19:43:57] [DEBUG]         argv[14] = -dpi
[20180219-19:43:57] [DEBUG]         argv[15] = 96
[20180219-19:43:57] [DEBUG]         argv[16] = (null)
[20180219-19:44:07] [ERROR] X server for display 10 startup timeout
[20180219-19:44:07] [INFO ] starting xrdp-sessvc - xpid=3131 - wmpid=3130
[20180219-19:44:07] [ERROR] X server for display 10 startup timeout
[20180219-19:44:07] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:44:07] [DEBUG] aborting connection...
[20180219-19:44:07] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 3129, ip 0.0.0.0:55558 - socket: 12
[20180219-19:48:30] [INFO ] A connection received from ::1 port 51540
[20180219-19:48:32] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:49:01] [INFO ] shutting down sesman 1
[20180219-19:49:01] [WARN ] receiving SIGHUP 1
[20180219-19:49:01] [CORE ] shutting down log subsystem...
[20180219-19:49:01] [INFO ] configuration reloaded, log subsystem restarted
[20180219-19:49:01] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:50:22] [DEBUG] libscp initialized
[20180219-19:50:22] [INFO ] starting xrdp-sesman with pid 627
[20180219-19:50:22] [INFO ] listening to port 3350 on 127.0.0.1
[20180219-19:50:51] [INFO ] A connection received from ::1 port 34254
[20180219-19:50:54] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [INFO ] A connection received from ::1 port 34268
[20180219-19:51:32] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55697 - socket: 12
[20180219-19:51:32] [INFO ] starting Xvnc session...
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:51:32] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [INFO ] Xvnc :10 -auth .Xauthority -geometry 3440x1440 -depth 32 -rfbauth /home/dave/.vnc/sesman_dave_passwd:10 -bs -nolisten tcp -localhost -dpi 96
[20180219-19:51:32] [CORE ] error starting X server - user dave - pid 1600
[20180219-19:51:33] [DEBUG] errno: 2, description: No such file or directory
[20180219-19:51:33] [DEBUG] execve parameter list size: 17
[20180219-19:51:33] [DEBUG]         argv[0] = Xvnc
[20180219-19:51:33] [DEBUG]         argv[1] = :10
[20180219-19:51:33] [DEBUG]         argv[2] = -auth
[20180219-19:51:33] [DEBUG]         argv[3] = .Xauthority
[20180219-19:51:33] [DEBUG]         argv[4] = -geometry
[20180219-19:51:33] [DEBUG]         argv[5] = 3440x1440
[20180219-19:51:33] [DEBUG]         argv[6] = -depth
[20180219-19:51:33] [DEBUG]         argv[7] = 32
[20180219-19:51:33] [DEBUG]         argv[8] = -rfbauth
[20180219-19:51:33] [DEBUG]         argv[9] = /home/dave/.vnc/sesman_dave_passwd:10
[20180219-19:51:33] [DEBUG]         argv[10] = -bs
[20180219-19:51:33] [DEBUG]         argv[11] = -nolisten
[20180219-19:51:33] [DEBUG]         argv[12] = tcp
[20180219-19:51:33] [DEBUG]         argv[13] = -localhost
[20180219-19:51:33] [DEBUG]         argv[14] = -dpi
[20180219-19:51:33] [DEBUG]         argv[15] = 96
[20180219-19:51:33] [DEBUG]         argv[16] = (null)
[20180219-19:51:43] [ERROR] X server for display 10 startup timeout
[20180219-19:51:43] [ERROR] X server for display 10 startup timeout
[20180219-19:51:43] [INFO ] starting xrdp-sessvc - xpid=1600 - wmpid=1599
[20180219-19:51:43] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:51:43] [DEBUG] aborting connection...
[20180219-19:51:43] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 1598, ip 0.0.0.0:55697 - socket: 12
dave@hal9000:/var/log$

Netstat -l:

Code: Select all

dave@hal9000:/var/log$ netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 localhost:smtp          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN
tcp6       0      0 localhost:smtp          [::]:*                  LISTEN
tcp6       0      0 [::]:3389               [::]:*                  LISTEN
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN
tcp6       0      0 localhost:3350          [::]:*                  LISTEN
udp        0      0 0.0.0.0:43335           0.0.0.0:*
udp        0      0 0.0.0.0:mdns            0.0.0.0:*
udp        0      0 0.0.0.0:bootpc          0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp6       0      0 [::]:53584              [::]:*
udp6       0      0 [::]:mdns               [::]:*
raw6       0      0 [::]:ipv6-icmp          [::]:*                  7
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     15104    /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     25192    /tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     22591    /tmp/.ICE-unix/693
unix  2      [ ACC ]     STREAM     LISTENING     18395    /tmp/.X11-unix/X1024
unix  2      [ ACC ]     STREAM     LISTENING     19220    /run/user/1000/pulse/native
unix  2      [ ACC ]     STREAM     LISTENING     11186    /tmp/ssh-FBYJ1rlvvmr2/agent.1241
unix  2      [ ACC ]     STREAM     LISTENING     25238    /tmp/.ICE-unix/1241
unix  2      [ ACC ]     STREAM     LISTENING     22551    /run/user/118/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     25237    @/tmp/.ICE-unix/1241
unix  2      [ ACC ]     STREAM     LISTENING     1307     /run/lvm/lvmetad.socket
unix  2      [ ACC ]     STREAM     LISTENING     22556    /run/user/118/pulse/native
unix  2      [ ACC ]     STREAM     LISTENING     1310     /run/systemd/journal/stdout
unix  2      [ ACC ]     STREAM     LISTENING     22559    /run/user/118/bus
unix  2      [ ACC ]     STREAM     LISTENING     25191    @/tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     22561    /run/user/118/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     22564    /run/user/118/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     22566    /run/user/118/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     22568    /run/user/118/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     25132    /var/run/minissdpd.sock
unix  2      [ ACC ]     STREAM     LISTENING     1330     /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     1332     /run/lvm/lvmpolld.socket
unix  2      [ ACC ]     STREAM     LISTENING     20320    @/tmp/dbus-UfzVMsQcvB
unix  2      [ ACC ]     SEQPACKET  LISTENING     1351     /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     25185    @/tmp/dbus-6ofjyHR1
unix  2      [ ACC ]     STREAM     LISTENING     18245    @/tmp/dbus-lxvYA6gm
unix  2      [ ACC ]     STREAM     LISTENING     11869    /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     11872    /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     23907    /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     18249    @/tmp/dbus-DUt4Gudv
unix  2      [ ACC ]     STREAM     LISTENING     23912    /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     23915    /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     13163    /var/run/bumblebee.socket
unix  2      [ ACC ]     STREAM     LISTENING     23917    /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     23919    /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     23921    /run/user/1000/bus
unix  2      [ ACC ]     STREAM     LISTENING     22590    @/tmp/.ICE-unix/693
unix  2      [ ACC ]     STREAM     LISTENING     22647    /run/user/118/wayland-0
unix  2      [ ACC ]     STREAM     LISTENING     11177    /run/user/1000/keyring/control
unix  2      [ ACC ]     STREAM     LISTENING     23750    /var/run/NetworkManager/private-dhcp
unix  2      [ ACC ]     STREAM     LISTENING     19850    @/tmp/dbus-hOFBHWJFqv
unix  2      [ ACC ]     STREAM     LISTENING     18248    @/tmp/dbus-N9OBLlTV
unix  2      [ ACC ]     STREAM     LISTENING     18394    @/tmp/.X11-unix/X1024
unix  2      [ ACC ]     STREAM     LISTENING     25186    @/tmp/dbus-7hAWJESu
unix  2      [ ACC ]     STREAM     LISTENING     22245    /run/user/1000/keyring/pkcs11
unix  2      [ ACC ]     STREAM     LISTENING     18246    @/tmp/dbus-EdXm47V8
unix  2      [ ACC ]     STREAM     LISTENING     22249    /run/user/1000/keyring/ssh

The error message upon connecting to the linux machine is just «some problem» :D

Источник

The messages

connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to sesman
login successful for display 10
started connecting
connecting to 127.0.0.1 5910
error — problem connecting

Printed in the dialog box when attempting to connect to an XRDP enabled system.

The latter problem implies a connectivity problem, which couldn’t be further from the cause.

Many sites insist that installing XRDP, vncserver (of some sort) in one order or another is the problem.  Also misleading.

Then you look in xrdp-sesman-log in /var/log, you will see this

[INFO ] starting Xvnc session...
[ERROR] X server for display 10 startup timeout
[INFO ] starting xrdp-sessvc - xpid=3531 - wmpid=3530
[ERROR] X server for display 10 startup timeout
[ERROR] another Xserver is already active on display 10
[DEBUG] aborting connection...[20130627-08:55:49]
[INFO ] ++ terminated session:  username root, display :10.0, session_pid 3529, 
      ip 192.168.0.227:59050 - socket: 7

Indicating that somehow your RDP session has two Xservers active.  What happens when you log in is that a login method is performed to authenticate, and the top dialog indicates the progress of that.

Then it will spawn some VNC server session for the X session (uses 10, 11, etc.) to connect.

If you read the symptoms here, there is already a session or server on 5910.  Completely wrong.

To find the problem, one has to try running the window manager.  I don’t know if this would happen for other than xfce4, which I use, but it produces the root problem.  run:

If you try running vncserver, you will see at the end of the startup this:

[dix] Could not init font path element /usr/share/fonts/default/Type1, removing from list!
[dix] Could not init font path element built-ins, removing from list!

Fatal server error:
could not open default font 'fixed'

Turns out that if any failure occurs in the chain of events between the authentication after the RDP login and getting the session going, you get the » Xserver is already active on display» message in the var log sesman log.

Other errors I suspect produce the same nonsense, someone reported when the vnc server and client couldn’t agree on a geometry, the same error occurred.

This is probably the solution to all the load order issues and which vnc server (real or tight) package you use.

quoting:
I have solved it by installing xfonts-base

This also solved my problem.

Источник

With the help of Centos forum resources, I added GUI (MATE Desktop) support to a dedicated Centos 7 web server (Centos 7 Live DVD — Can Gnome/GUI be installed later? viewtopic.php?f=47&t=60762).

While the MATE desktop is a convenient addition to the main server console, I would also like to provide remote GUI capability to my main workstation which is a Windows 7 desktop. I am trying to connect remotely to the MATE desktop using a Windows Remote Desktop client on the Windows side and xrdp on the Centos side, but am encountering a «some problem» VNC connection error which I think is coming from the Centos side:

xrdp screenshot.jpg
xrdp screenshot.jpg (72.36 KiB) Viewed 39473 times

The components I am using include:

Code: Select all

Windows:	Remote Desktop Connection Shell Version 6.3.9600 (Supports Network Level Authentication and RDP 8.1)
Linux:	CentOS Linux release 7.2.1511 (Core)
Linux:	xrdp.x86_64 version 1:0.9.0-4.el7 from @epel
Linux:	tigervnc.x86_64  version 1.3.1-9.el7  from @base
Linux:	tigervnc-server.x86_64 version 1.3.1-9.el7 from @base

My xdrp.log sequence for the failed session is as follows:

Code: Select all

[20170108-19:19:04] [INFO ] A connection received from: 10.0.0.154 port 51143
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 10.0.0.154:51143 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem
[20170108-19:19:04] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 8
[20170108-19:19:04] [ERROR] Listening socket is in wrong state we terminate listener
[20170108-19:19:04] [INFO ] A connection received from: 10.0.0.154 port 51144
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 10.0.0.154:51144 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem
[20170108-19:19:04] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem
[20170108-19:19:04] [DEBUG] xrdp_00001058_wm_login_mode_event_00000001
[20170108-19:19:04] [WARN ] local keymap file for 0x0409 found and dosen't match built in keymap, using local keymap file
[20170108-19:19:04] [DEBUG] returnvalue from xrdp_mm_connect 0
[20170108-19:19:07] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:08] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:09] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:10] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:11] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:12] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:13] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:14] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:15] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:16] [DEBUG] VNC Error after security negotiation
[20170108-19:19:16] [DEBUG] VNC error before sending share flag
[20170108-19:19:16] [DEBUG] VNC error before receiving server init
[20170108-19:19:16] [DEBUG] VNC error before receiving pixel format
[20170108-19:19:16] [DEBUG] VNC error before receiving name length
[20170108-19:19:16] [DEBUG] VNC error before receiving name
[20170108-19:19:16] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:16] [DEBUG] xrdp_mm_module_cleanup
[20170108-19:19:16] [DEBUG] VNC mod_exit
[20170108-19:19:16] [INFO ] An established connection closed to endpoint: 127.0.0.1:3350 - socket: 11

My xrdp-sesman.log sequence for the failed session is as follows:

Code: Select all

[20170108-19:17:18] [WARN ] [init:46] libscp initialized
[20170108-19:17:18] [CORE ] starting sesman with pid 4180
[20170108-19:17:18] [INFO ] listening...
[20170108-19:19:04] [INFO ] A connection received from: 127.0.0.1 port 38634
[20170108-19:19:04] [INFO ] scp thread on sck 8 started successfully
[20170108-19:19:04] [INFO ] ++ created session (access granted): username brian, ip 10.0.0.154:51144 - socket: 8
[20170108-19:19:04] [INFO ] starting Xvnc session...
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 127.0.0.1:38634 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 127.0.0.1:38634 - socket: 8
[20170108-19:19:04] [ERROR] env_set_user: error creating .vnc dir
[20170108-19:19:04] [INFO ] Xvnc :11 -geometry 1280x768 -depth 24 -rfbauth /home/brian/.vnc/sesman_brian_passwd -bs -nolisten tcp -localhost -dpi 96 -depth 24  
[20170108-19:19:05] [INFO ] starting xrdp-sessvc - xpid=4188 - wmpid=4187
[20170108-19:19:05] [INFO ] ++ terminated session:  username brian, display :11.0, session_pid 4186, ip 10.0.0.154:51144 - socket: 8

I would be grateful if a community member more skilled than I (which I suspect is just about everyone) could provide some guidance in resolving this connection problem. I can provide additional .ini configuration information if that would be helpful. Thanks!

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Xrdebugnew cpp как исправить ошибку
  • Xray ошибка p0504
  • Xray engine error report что это
  • Xrandr error of failed request badmatch
  • Xinit giving up xinit unable to connect to x server connection refused xinit server error

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии