Closed stefanwerfling closed 2 months ago
We have the problem that apparently only one server can bind to the Unix sock:
flyingfish_service | {"level":"error","message":"NginxServer::stderr: 2024/04/12 09:05:07 [emerg] 19#19: bind() to unix:/opt/flyingfish/nginx/socks/127_0_0_1_10443.sock failed (98: Address already in use)","timestamp":"2024-04-12T09:05:08.858Z"}
flyingfish_service | {"level":"error","message":"NginxServer::stderr: 2024/04/12 09:05:07 [emerg] 19#19: bind() to unix:/opt/flyingfish/nginx/socks/127_0_0_1_10080.sock failed (98: Address already in use)","timestamp":"2024-04-12T09:05:08.859Z"}
flyingfish_service | {"level":"error","message":"NginxServer::stderr: 2024/04/12 09:05:07 [notice] 19#19: try again to bind() after 500ms","timestamp":"2024-04-12T09:05:08.860Z"}
flyingfish_service | {"level":"error","message":"NginxServer::stderr: 2024/04/12 09:05:07 [emerg] 19#19: bind() to unix:/opt/flyingfish/nginx/socks/127_0_0_1_10443.sock failed (98: Address already in use)","timestamp":"2024-04-12T09:05:09.358Z"}
flyingfish_service | {"level":"error","message":"NginxServer::stderr: 2024/04/12 09:05:07 [emerg] 19#19: bind() to unix:/opt/flyingfish/nginx/socks/127_0_0_1_10080.sock failed (98: Address already in use)","timestamp":"2024-04-12T09:05:09.359Z"}
Unfortunately we cannot list multi http servers on unix, so the ticket is no longer valid.
Check whether an internal connection via Unix socket is possible. Double check beforehand whether this has a performance advantage.