You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2014/11/05 18:19:34 UTC
[jira] [Updated] (TS-1871) No Error on Startup if auto_conf Port is
Unavailable
[ https://issues.apache.org/jira/browse/TS-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan Hinrichs updated TS-1871:
-------------------------------
Fix Version/s: (was: 5.2.0)
5.3.0
> 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: Manager
> Reporter: Clinton Wolfe
> Labels: newbie
> Fix For: 5.3.0
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)