On Mon, Mar 06, 2017 at 06:06:19AM +0000, David Gilmour wrote: > On Tue, 28 Feb 2017 15:07:39 +0100 Paul van Tilburg <pau...@debian.org> wrote: > > I have updated the xrdp.service unit locally and that seems to fix it > > (see attached file). > > > > The changes are: > > > > --- /lib/systemd/system/xrdp.service 2017-01-25 18:10:11.000000000 > > +0100 > > +++ /etc/systemd/system/xrdp.service 2017-02-28 15:07:01.130060204 > > +0100 > > @@ -1,8 +1,7 @@ > > [Unit] > > Description=xrdp daemon > > Documentation=man:xrdp(8) man:xrdp.ini(5) > > -Requires=xrdp-sesman.service > > -After=network.target xrdp-sesman.service > > +After=network-online.target > > Paul, unfortunately it didn’t seem to work for me: > > root@pod:/home/david# systemctl status xrdp > > ● xrdp.service - xrdp daemon > > Loaded: loaded (/etc/systemd/system/xrdp.service; enabled; vendor preset: > enabled) > Active: failed (Result: resources) since Sun 2017-03-05 21:39:49 PST; 56s > ago > Docs: man:xrdp(8) > man:xrdp.ini(5) > Process: 873 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=0/ > SUCCESS) > Process: 849 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, > status=0/SUCCESS) > > Mar 05 21:39:46 pod systemd[1]: Starting xrdp daemon... > Mar 05 21:39:46 pod systemd[1]: xrdp.service: PID file /run/xrdp/xrdp.pid not > readable (yet?) after start: No such file or directory > Mar 05 21:39:48 pod xrdp[1119]: (1119)(139942974253888)[INFO ] starting xrdp > with pid 1119 > Mar 05 21:39:49 pod xrdp[1119]: (1119)(139942974253888)[ERROR] > xrdp_listen_main_loop: listen error, possible port already in use > Mar 05 21:39:49 pod xrdp[1119]: (1119)(139942974253888)[DEBUG] Closed socket > 11 (AF_INET6 :: port 0)
The above is strange. So even after the network-online target, there is still something that prevents XRDP for listening on its required port. After a few seconds it seems settled and you can start XRDP. If I search for this error online, there are many issues reported about this error message, so I'm not sure if this a different problem. Do you get the same error with the upstream systemd unit. About xrdp-sesman, it also fails because it cannot listen on a port, weird. Something is awry in the network implementation here that doesn't bother other daemons. Do you also use NetworkManager or a different network configuration stack? Kind regards, Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/XMPP: p...@luon.net | GnuPG key ID: 0x50064181
