xrdp-sesman won't start #2816
Comments
|
Hi @tiapfy This sort of thing has been reported a couple of times now (#2750, #2752) and as yet we have not found a resolution I am happy with. What do you get for these commands? Being inexperienced with Ubuntu is fine - we've all been there! For reference these commands output the status of the two services, generate a system log for xrdp-sesman and see what is currently listening on port 3350. Thanks |
From From From Just to be clear, the last one says Invalid argument but I pasted exactly what you wrote. |
|
Interesting. According to the v0.9.12 sources, sesman will create a PID file in However, systemd is looking for a PID file in What do you get for these commands:- |
|
Here are the outputs: |
|
The problem seems to be that your I can't see any installation option that would cause these two locations to differ. Is there some local change you've made that may have caused this, or am I misunderstanding an Ubuntu installation option? Also, |
|
I didn't use any strange installation option consciously, because then it wouldn't have worked from the start, right? From what I gathered the last time someone used the remote desktop the python script we use everytime was started. All it does is start steamcmd and look for updates to the installed game. It never caused problems before this. A couple of weeks back I installed something through apt but ended up never using it and the problem appeared only later. I also installed some updates to Ubuntu at that time. |
|
I suspect at some point /var/run has been removed and re-created as a separate directory. The symlink is created when the A simple thing to try is this.
That will only affect xrdp. See if it fixes your problem. |
|
Ok, it failed again: xrdp-sesman.log: |
|
The edit hasn't worked. It's in the error message:- Check it's happened with |
|
The edit seems to be correct: I rebooted but it still doesn't work: |
|
Interesting. Can we just check those areas are currently not the same? What do you get for:- |
|
"No such file or directory" |
|
Right, so those directories aren't the same and it looks like systemd is assuming they are. We can make them the same, but it will be disruptive. If they've been separated for a good reason (I really can't think of one) this could cause issues that might require console access to fix. Can you get to the console of the VPS, or do you just has ssh access? My worry is that if the machine won't boot properly after this change you could be locked out of it. |
|
I can only access with SSH, sadly. I would have to wait for the weekend to test it without causing problems. What is the procedure? |
|
What do you get for the command Depending on the above, I'd think the following would do it, logged in over ssh:-
None of those steps should report an error. If they do, something else is going on. Does that make sense? |
|
Here's the output: |
|
Right - nothing is mounted on /var/run. So it looks like a simple case of the symlink being deleted. The steps I gave you above should be sufficient to restore a standard layout. |
|
So, this problem gets deeper. I'm having the same issue, and I thought you were onto something here. I read that other issue you closed where the guy said a syslink fixed it. But since the website was a dead link, we couldn't see what he did. I did as you asked above. following your instructions. I created a syslink from /run to /var/run. It worked fine, the link was created. I've verified. I was still getting the error that xrpd-sesman cannot find the pid in /var/run/xrdp/xrdp-seshman.pid. I even went as far as doing a sudo mkdir xrpd, as there wasn't one. I know most processes create their own path, but I just wanted to see what happened. What happens is that after xrdp-sesman fails, it deletes the directory. Expected. But it DOES show it's following the path! But it's still not working. I started getting this issue after updating my VM from Mint 20.* to Mint 21.2 (which uses ubuntu as its base). Net net, I'm getting bit by this new Ubuntu bug. EDIT: and well.... it worked. I don't know if adding the /var/run syslink helped or not. I'll be honest, since I was having this EXACT same problem, I didn't think to check if I already HAD a /var/run/. I did issue the mvdir command you had in your instructions above, and I now have a linked /var/oldrun. So I kinda suspect I did already have it. I DIDN'T try a reinstall, or a remove/install, before because I had seen other threads where that hadn't worked. But... it worked for me. And is the easiest thing to try. I have rebooted several times, and it's still working. Soo.... I'll call it fixed for now. No idea how a reinstall worked. But weirder things have happened. Linux isn't just an OS, it's an adventure! |
|
Triaging these things can be pretty difficult, as fixing something ASAP puts huge pressures on trying to work through problems slowly and methodically. If your /var/oldrun is a link now, it would have been before the procedure was followed. In any case, thanks for raising this. I don't think we've really got to the bottom of the issue (or the ones mentioned above), but I'm glad it's working at the moment. I'll leave this open for a bit just in case more information surfaces. |
|
Ok I tried the steps and rebooted and now it seems to work. Thank you for the help you provided even though it wasn't a problem directly related to xrdp. |
|
I can confirm the steps below fixed this issue on Linux Mint 21.2 and xrdp 0.9.17
|
|
I think I encountered this issue after upgrading from Ubuntu 23.04 to 23.10 |
xrdp version
0.9.12-1
Detailed xrdp version, build options
Operating system & version
Ubuntu 20.04
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
No response
What desktop environment do you use?
GNOME
Environment xrdp running on
VM
What's your client?
No response
Area(s) with issue?
Session manager (sesman)
Steps to reproduce
I've installed xrdp on a VPS a year ago and it worked well until 2 days ago (according to the logs), when it received a SIGHUP and shut down. Today I tried to connect and couldn't. I found the logs I just mentioned and started trying to fix the problem. Trying to start it manually with "sudo systemctl start xrdp" didn't work, saying "A dependency job for xrdp.service failed", which, according to other posts, means that xrdp-sesman is having a problem. At some point I uninstalled everything and in doing so I lost the original logs. Now I have reinstalled everything and it seems that sesman is still incapable of starting. I'm still pretty unexperienced with Ubuntu so I probably missed something obvious or didn't understand some of the posts I read.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
Anything else?
xrdp-sesman.log
xrdp.log is empty
xorg.conf is missing
The text was updated successfully, but these errors were encountered: