Friday, September 13, 2013

X Server -- no display in range is available. xrdp_mm_process_login_response: login failed

 I was having this error xrdp_mm_process_login_response: login failed. I tried the solution from this blog entry, but the error remain xrdp_mm_process_login_response: login failed

When I look into the /var/log/ xrdp-sesman.log, the error is followed:
[20130913-14:11:00] [INFO ] starting Xvnc session...
[20130913-14:11:00] [ERROR] X server -- no display in range is available

 I managed to solve the issue by changing /etc/xrdp/sesmain.ini - MaxSessions from 10 to 100
[Security]
AllowRootLogin=1
MaxLoginRetry=4
#TerminalServerUsers=tsusers
#TerminalServerAdmins=tsadmins

[Sessions]
X11DisplayOffset=10
MaxSessions=100
KillDisconnected=0
IdleTimeLimit=0
DisconnectedTimeLimit=0

Restart the Service
# service xrdp restart


8 comments:

Ghebaru Ion said...

for me worked very well
...
thanks

Shrey Mehrotra said...

Thanks a lot....worked for me..

Iain Elder said...

I solved this by changing X11DisplayOffset to 1 instead.

Thanks for your posts!

DeePee said...

Worked for me too!!

Thanks!

Ole Thomsen said...

Me too.
Karma your way

NewAlphabet said...

Thanks for getting my problem fixed

Branko said...

Thanx for a fix

rk said...

This works only temporarily until you have 100 sessions in use according to xrdp.
What you need to do is remove old lock-files from sessions that have long ago disconnected.

To do this, you need to delete the corresponding lockfiles in the /tmp directory.
These files are hidden by default as they start with a .

so:
cd /tmp
ls -a

And you will see these files, for instand .X10-lock, .X11-lock etc.
Remove the ones that you are sure that are no longer in use, which is most likely all of them. Off course, after 10 bad disconnections (often a server reboot) you will have to repeat this exercise.

So using this in combination with setting the maximum allowed number of sessions to a higher number like 20 or 50 will help as well.