XRDP Service Keep on getting stopped #2937
Unanswered
AbinayaSandhiyaM
asked this question in
Q&A
Replies: 1 comment
-
Hi @AbinayaSandhiyaM - welcome back. Your xrdp process is receiving a SIGTERM (or possibly SIGINT) signal from another process:-
Check your system logs for system activity just before this time with:-
If that doesn't give you any clues, you may need to track down the sender of the signal. This can be hard. Have a look at RHEL knowledgebase #165993. This is for SIGKILL but can be readily adapted for SIGTERM. It also contains links which I can't follow, as I don't have a RH account. As you mention RHEL, I'm assuming you do. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
On our RHEL8 Server XRDP service getting stopped/dead automatically.
And based on the log could see below messages
xrdp/xrdp.log
[20240125-07:22:35] [ERROR] [ITU-T X.224] Connection Sequence: CR-TPDU (Connection Request) failed
[20240125-07:22:35] [ERROR] xrdp_sec_incoming: xrdp_iso_incoming failed
[20240125-07:22:35] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20240125-07:22:35] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20240125-07:22:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:10.151.75.13 port 3389)
[20240125-08:52:52] [INFO ] Received termination signal, stopping the server accept new connections thread
[20240125-08:52:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
Could any one let us know what could be the reason for this failure.
Since we been using XRDP on different machine like RHEL7, 9 etc.
But recently on one our newly configured RHEL8 machine facing this sudden xrdp stop/dead issue
Beta Was this translation helpful? Give feedback.
All reactions