Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kill then start server causes "Warning: NET_IP4Socket: bind: Address already in use" #427

Open
bbashy opened this issue Apr 5, 2024 · 3 comments

Comments

@bbashy
Copy link
Contributor

bbashy commented Apr 5, 2024

Getting an issue where it thinks the port is still in-use when restarting servers.

I use kill -15 <pid> and then start it back up 30 seconds later. When it starts it crashes and has the following;

Opening IP socket: 45.282.361.513:28960 UDP
[1;33mWarning: NET_IP4Socket: bind: Address already in use
---- Network shutdown ----
--------------------------

Sys_Error: Could not bind to a IPv4 network socket

Is there a solution to gracefully kill it? I don't get the same issue with CoD4 1.7 servers.

@D4edalus
Copy link
Contributor

D4edalus commented Apr 6, 2024

try fuser -k 28960/udp

https://stackoverflow.com/a/11596144

@bbashy
Copy link
Contributor Author

bbashy commented Apr 6, 2024

Comment says port will still be unavailable for 60 seconds. Might just wait 60 seconds instead just for CoD4x servers.

@K-Faktor
Copy link
Contributor

K-Faktor commented Apr 6, 2024

pkill -f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants