code-server restarted endlessly by systemd with error listen EADDRINUSE #5001
-
Hello! I'm using code-server with ssh on ubuntu server installed in Raspberry Pi 4. I'm using a ssh client with termius android application, code-server was connected with local port forwarding through ssh host. (localhost:8080 (client) -> 127.0.0.1:34543 (host)) There has been no major problem running code-server and actually it works, but I just found this problem while looking through the system logs.
This endlessly repeated schedules devoured my resources of raspi4. I did stop code-server service and killed process which looked up by I would be very grateful if you could help me solve this problem. Thank you. edited 22.03.20 17:16: edited 22.03.01 00:34:
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 8 replies
-
I am not super familiar with |
Beta Was this translation helpful? Give feedback.
-
Why is it resetting the process continuously? Systemctl ensures background processes like ssh and code-server is a lightweight binary... But there should be a code bug since my theory is that due to a crucial code change, it seems to reset itself on background processing. @snublueberry I think you said it works normally on normal startup. Can you try using tmux? |
Beta Was this translation helpful? Give feedback.
-
I've tried some ways to solve with your thankful suggests, but I still don't know why. I think there was a problem with the multiple connection of ssh with the same id. (But I'm not sure at all) |
Beta Was this translation helpful? Give feedback.
-
I meet the same problem today 😂 I have tried several methods but cannot solve this problem. I cannot use systemctl to control code-server.
Although these problems do not affect the use, I finally reinstalled the code-server, and gave up using systemctl to control it. |
Beta Was this translation helpful? Give feedback.
-
Oh, I'm so stupid 🤡 I incorrectly wrote Now everything is fine. |
Beta Was this translation helpful? Give feedback.
I've tried some ways to solve with your thankful suggests, but I still don't know why. I think there was a problem with the multiple connection of ssh with the same id. (But I'm not sure at all)
Now, I'm using it with https connection and it works well.