Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#840132: xrdp-sesman.service sometimes fails to start on boot

553 views
Skip to first unread message

Christian Pernegger

unread,
Oct 8, 2016, 12:40:02 PM10/8/16
to
Package: xrdp
Version: 0.9.0~20160601+git703fedd-3
Severity: normal

Hello,

since xrdp still doesn't work for me I've been doing a lot of
experiments to get it to cooperate, including a lot of rebooting to
get back to a clean slate.

I've noticed that sesman doesn't always start automatically on
boot. Symptom: xrdp login screen / session chooser comes up but
hitting enter after the password does nothing. systemctl status says:

● xrdp-sesman.service - xrdp (X Remote Desktop Protocol) session manager
Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sam 2016-10-08 18:25:37 CEST; 2min 3s ago
Docs: man:xrdp-sesman(8)
man:sesman.ini(5)
Process: 819 ExecStop=/usr/sbin/xrdp-sesman $SESMAN_OPTIONS --kill (code=exited, status=1/FAILURE)
Process: 817 ExecStart=/usr/sbin/xrdp-sesman $SESMAN_OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 818 (code=exited, status=0/SUCCESS)

Okt 08 18:25:37 fatbeard systemd[1]: Starting xrdp (X Remote Desktop Protocol) session manager...
Okt 08 18:25:37 fatbeard xrdp-sesman[817]: (817)(139868790023360)[WARN ] [init:46] libscp initialized
Okt 08 18:25:37 fatbeard xrdp-sesman[818]: (818)(139868790023360)[CORE ] starting sesman with pid 818
Okt 08 18:25:37 fatbeard systemd[1]: Started xrdp (X Remote Desktop Protocol) session manager.
Okt 08 18:25:37 fatbeard xrdp-sesman[818]: (818)(139868790023360)[INFO ] listening...
Okt 08 18:25:37 fatbeard xrdp-sesman[818]: (818)(139868790023360)[ERROR] bind error on port '3350': 22 (Invalid argument)
Okt 08 18:25:37 fatbeard xrdp-sesman[818]: (818)(139868790023360)[INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
Okt 08 18:25:37 fatbeard systemd[1]: xrdp-sesman.service: Control process exited, code=exited status=1
Okt 08 18:25:37 fatbeard systemd[1]: xrdp-sesman.service: Unit entered failed state.
Okt 08 18:25:37 fatbeard systemd[1]: xrdp-sesman.service: Failed with result 'exit-code'.

Cheers,
C.


-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xrdp depends on:
ii adduser 3.115
ii init-system-helpers 1.45
ii libc6 2.24-3
ii libfuse2 2.9.7-1
ii libjpeg62-turbo 1:1.5.0-1
ii libopus0 1.1.2-1
ii libpam0g 1.1.8-3.3
ii libssl1.0.2 1.0.2j-1
ii libx11-6 2:1.6.3-1
ii libxfixes3 1:5.0.2-1
ii libxrandr2 2:1.5.0-1

Versions of packages xrdp recommends:
ii xorgxrdp 0.9.0~20160601+git703fedd-3

xrdp suggests no packages.

Versions of packages xorgxrdp depends on:
ii libc6 2.24-3
pn xorg-input-abi-22 <none>
ii xserver-xorg-core [xorg-video-abi-20] 2:1.18.4-2

Versions of packages xorgxrdp recommends:
ii xorg 1:7.7+16

Versions of packages xrdp is related to:
ii tightvncserver [vnc-server] 1.3.9-8
ii vnc4server [vnc-server] 4.1.1+X4.3.0-39

-- Configuration Files:
/etc/xrdp/xrdp.ini changed [not included]

-- no debconf information

Dominik George

unread,
Oct 8, 2016, 1:50:02 PM10/8/16
to
Hi,

> Version: 0.9.0~20160601+git703fedd-3

Please try again with the current version 0.9.0~20161006+git132cc10-1. It
should at least give more conclusive logs.

Cheers,
Nik
signature.asc

Christian Pernegger

unread,
Oct 10, 2016, 4:10:02 AM10/10/16
to
Hello,

reportbug did notify me about a newer version, however the newest one to be downloaded via packages.debian.org (yes, for unstable) was still the one I had. I'll get around to testing newer versions eventually, but for now I'm back on 0.6.1. At least that one more or less works (w/ xfce) and when it fails it does so consistently.

Cheers,
C.

Frank-Christian Schröder

unread,
Oct 9, 2018, 12:30:04 PM10/9/18
to
Hi all,
thank you for your contributions.
I had experienced the same behavior of xrdp.service and xrdp-sesman.service.

In "/lib/systemd/system/xrdp-sesman.service"
and "/lib/systemd/system/xrdp.service"
I did this setting:
After=multi-user.target

That helped to start the two services automatically during boot.
Are there any concerns about this setting?

Thank you and kind regards
Frank-Christian
0 new messages