At least track now.
We repeatedly get this in the automatic system tests, and we don't really know why.
I got this on a test server now, and the reason is likely this odd connection stuck in a closing state: > [cendio@lab-210 ~]$ ss -nt | grep 904 > FIN-WAIT-1 0 168 127.0.0.1:904 127.0.0.1:904 It eventually timed out and vsmagent could start properly.
Perhaps we should be setting SO_REUSEADDR? It seems to be a bit of a norm for servers on well-known ports? https://stackoverflow.com/questions/6960219/why-not-using-so-reuseaddr-on-unix-tcp-ip-servers