{"version":"2.1.251","anchor":"clearer-errors-when-the-messaging-socket-cannot-be-bound","canonical_anchor":"clearer-errors-when-the-messaging-socket-cannot-be-bound","heading":"Clearer errors when the messaging socket cannot be bound","tier":"notice","area":"Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/clearer-errors-when-the-messaging-socket-cannot-be-bound","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Clearer errors when the messaging socket cannot be bound\n\nFailing to bind the messaging socket now names the cause: path too long, in use, or permissions.\n\n**What**\n\nFailing to bind the peer-messaging socket at startup now produces a message specific to the cause: a path too long for a Unix socket (roughly 104 bytes), an address already in use, or a permissions problem. A separate error covers the case where the bind works but the setup after it fails.\n\n**Details**\n\n- The too-long case tells you to choose a shorter path.\n- Applies to the error path only; successful startup is unchanged.\n\n**Evidence**\n\n`the path is too long for a Unix socket (max ~104 bytes); choose a shorter one`\n\n- Area: Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}