[
https://issues.apache.org/jira/browse/TS-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach reassigned TS-1871:
-------------------------------
Assignee: James Peach
This bit me recently, since it's possible to get ATS itself to bind to this
port (eg. the proxy_pac port). Way too easy to shoot a toe off here.
> No Error on Startup if auto_conf Port is Unavailable
> ----------------------------------------------------
>
> Key: TS-1871
> URL: https://issues.apache.org/jira/browse/TS-1871
> Project: Traffic Server
> Issue Type: Bug
> Components: Management
> Reporter: Clinton Wolfe
> Assignee: James Peach
> Fix For: 3.3.6
>
>
> If another process is already listening on the auto_conf port (8083 by
> default), traffic_manager silently fails to bind to it.
> This can break heartbeats, because heartbeats are sent to the process on 8083
> (which will probably not give the expected response as
> http://127.0.0.1:8083/synthetic.txt). With heartbeats broken, traffic_cop
> constantly re-starts traffic_server - which was the obvious symptom, in my
> case.
> Observed on ts 3.2.4, stock config, centos 5.9
> discussed in #traffic-server on freenode IRC, ortho_stice (clintoncwolfe) and
> amc, 2013-05-01 and 2013-05-02
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
