Improve an error message regarding Unix domain sockets.
When starting unit, if its Unix domain control socket was already active you would get an error message like 2023/03/15 18:07:55 [alert] 53875#8669650 connect(5, unix:/tmp/control.sock) succeed, address already in use which is confusing in a couple of regards, firstly we have the classic success/failure message and secondly 'address already in use' is an actual errno value, EADDRINUSE and we didn't get an error from this connect(2). Re-word this error message for greater clarity. Reported-by: Liam Crilly <liam.crilly@nginx.com> Cc: Liam Crilly <liam.crilly@nginx.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
This commit is contained in:
@@ -161,7 +161,7 @@ nxt_listen_socket_create(nxt_task_t *task, nxt_mp_t *mp,
|
||||
nxt_socket_close(task, ts);
|
||||
|
||||
if (ret == 0) {
|
||||
nxt_alert(task, "connect(%d, %*s) succeed, address already in use",
|
||||
nxt_alert(task, "connect(%d, %*s) socket already in use",
|
||||
ts, (size_t) orig_sa->length,
|
||||
nxt_sockaddr_start(orig_sa));
|
||||
|
||||
|
||||
Reference in New Issue
Block a user