[
https://issues.apache.org/jira/browse/TS-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582116#comment-14582116
]
Sudheer Vinukonda commented on TS-3685:
---------------------------------------
Umm, it looks like traffic_manager already sets SO_REUSEADDR option - given
this, perhaps, setting SO_REUSEPORT will not make any difference.
> traffic_manager can't bind to port 80 sometimes.
> ------------------------------------------------
>
> Key: TS-3685
> URL: https://issues.apache.org/jira/browse/TS-3685
> Project: Traffic Server
> Issue Type: Bug
> Components: Manager
> Reporter: Sudheer Vinukonda
>
> During new install/updates sometimes, when ATS is restarted too quickly
> multiple times, we occasionally end up with the below error, causing ATS not
> to come up:
> {code}
> [Jun 11 14:46:24.852] Manager {0x7fa0e2b217e0} NOTE:
> [LocalManager::listenForProxy] Listening on port: 80
> [Jun 11 14:46:24.852] Manager {0x7fa0e2b217e0} NOTE:
> [LocalManager::listenForProxy] Listening on port: 443
> [Jun 11 14:46:24.852] Manager {0x7fa0e2b217e0} ERROR: [bindProxyPort] Unable
> to bind socket: 80 : Address already in use
> {code}
> This is quite annoying and inconvenient since it blocks ATS from coming up
> (sometimes for very long) until a reboot or some other deep clean up is
> performed.
> Would like to add the socket option *SO_REUSEPORT* to the socket doing the
> proxy port binding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
