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

[David Gilmour]

Package: xrdp
Followup-For: Bug #840132

Dear Maintainer,

I have two systems on which xrdp fails to start at boot. On both
systems, subsequently running "systemctl start xrdp" always succeeds,
and if it is followed by "systemctl start xrdp-sesman", xrdp functions
normally and accepts sessions.

The systemd error report immediately after boot (before the successful
manual start) is as follows:

● xrdp.service - xrdp (X Remote Desktop Protocol) protocol server
   Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor
preset: enabled)
   Active: inactive (dead) since Mon 2016-12-26 19:26:54 PST; 40min ago
     Docs: man:xrdp(8)
           man:xrdp.ini(5)
  Process: 1166 ExecStopPost=/bin/rm -rf /var/run/xrdp/sockdir
(code=exited, status=0/SUCCESS)
  Process: 1162 ExecStop=/usr/sbin/xrdp $XRDP_OPTIONS --kill
(code=exited, status=0/SUCCESS)
  Process: 856 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited,
status=0/SUCCESS)
  Process: 831 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup
(code=exited, status=0/SUCCESS)
 Main PID: 1100 (code=exited, status=0/SUCCESS)

Dec 26 19:26:51 pod systemd[1]: Starting xrdp (X Remote Desktop
Protocol) protocol server...
Dec 26 19:26:52 pod systemd[1]: xrdp.service: PID file
/run/xrdp/xrdp.pid not readable (yet?) after start: No such file or
directory
Dec 26 19:26:53 pod systemd[1]: Started xrdp (X Remote Desktop Protocol)
protocol server.
Dec 26 19:26:54 pod xrdp[1100]: (1100)(140648291601216)[INFO ] starting
xrdp with pid 1100
Dec 26 19:26:54 pod xrdp[1100]: (1100)(140648291601216)[ERROR]
xrdp_listen_main_loop: listen error, possible port already in use
Dec 26 19:26:54 pod xrdp[1100]: (1100)(140648291601216)[DEBUG] Closed
socket 11 (AF_INET6 :: port 0)

On the second system, the error message is different; the xrdp service
fails because of a timeout.  Both systems are on xrdp
0.9.1~2016121126+git5171fa7-1.

One thing possibly interesting about both systems is that they are both
kvm hosts.  After each system reaches network.target, the dependency for
starting xrdp in systemd, quite a bit of subsequent network
configuration takes place: virtual network interfaces, bridges,
wlan probing and more.  In other words, it's clear that xrdp is trying
to start in a system whose network configuration is still very much
underway.

Of course, in all cases, xrdp-sesman also fails to start, with the cause
being the failed dependency on xrdp.service.  For that reason I am
attaching to this bug.

- David

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.46
ii  libc6                2.24-8
ii  libfuse2             2.9.7-1
ii  libjpeg62-turbo      1:1.5.1-2
ii  libopus0             1.1.3-1
ii  libpam0g             1.1.8-3.3
ii  libssl1.1            1.1.0c-2
ii  libx11-6             2:1.6.4-2
ii  libxfixes3           1:5.0.3-1
ii  libxrandr2           2:1.5.1-1
ii  lsb-base             9.20161125

Versions of packages xrdp recommends:
ii  xorgxrdp  0.9.1~2016121126+git5171fa7-1

Versions of packages xrdp suggests:
pn  guacamole  <none>

Versions of packages xorgxrdp depends on:
ii  libc6                                  2.24-8
pn  xorg-input-abi-24                      <none>
ii  xserver-xorg-core [xorg-video-abi-23]  2:1.19.0-2

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

Versions of packages xrdp is related to:
pn  vnc-server  <none>

-- no debconf information