failed: listen tcp 0.0.0.0:22000: listen: address already in use

We are using okteto on a kubernetes cluster. We have many users that are running jobs and we keep getting frozen pods. The initial sync seems fine, but alot of the time when the job completes on the kubernetes pod and is syncing data back it freezes. There are no errors on the containers or the server node that launched the job. I looked in the syncthing log and found below errors. I’m guess this means the address/port is in use because of another user. If this seems the case based on the logs, how do I change the default port and will I need to have each user use a different port? I don’t see a /config/syncthing anywhere and I’m thinking it’s because it come packaged with okteto. [ABKAV] 09:32:20 INFO: Listen (BEP/tcp): listen tcp 0.0.0.0:22000: listen: address already in use [ABKAV] 09:32:20 INFO: listenerSupervisor@tcp://0.0.0.0:22000: service tcp://0.0.0.0:22000 failed: listen tcp 0.0.0.0:22000: listen: address already in use [ABKAV] 09:32:20 INFO: Listen (BEP/tcp): listen tcp 0.0.0.0:22000: listen: address already in use [ABKAV] 09:32:20 INFO: listenerSupervisor@tcp://0.0.0.0:22000: service tcp://0.0.0.0:22000 failed: listen tcp 0.0.0.0:22000: listen: address already in use [ABKAV] 09:32:20 INFO: Listen (BEP/tcp): listen tcp 0.0.0.0:22000: listen: address already in use [ABKAV] 09:32:20 INFO: listenerSupervisor@tcp://0.0.0.0:22000: service tcp://0.0.0.0:22000 failed: listen tcp 0.0.0.0:22000: listen: address already in use [ABKAV] 09:32:33 INFO: Exiting

Thank you

Welcome here @bpopovich ! The command ‘netstat -nlp | grep 22000’ will tell you which process is using the port. Good luck!

Since Okteto ships with Syncthing in most likely a customised form, it may be a good idea to ask for help there. Their documentation provided about their ‘sync’ implementation and customisation properties is rather minimal.

Otherwise Syncthing Configuration — Syncthing v1.23.3 documentation is practically what you’re looking for. I don’t use any adjusted ports myself, but I can imagine that it may affect how one should configure remote devices.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.