[
https://issues.apache.org/jira/browse/TS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul updated TS-52:
--------------------------
Attachment: TS-52_traffic_cop_patch3.diff
This updated patch replaces TS-52_traffic_cop_patch2.diff and also reflects
changes in TS-6_traffic_manager_patch3.diff
patch -p0 -i TS-6_traffic_manager_patch3.diff
patch -p0 -i TS-52_traffic_cop_patch3.diff
The patch addresses the following issues:
1. PATH_NAME_MAX vs PATH_MAX
- This issue has been pulled out into Jira Ticket TS-84
2. ATS_ROOT vs TS_ROOT
- TS_ROOT is the default
3. /etc/traffic_server
- This issue has been pulled out into Jira Ticket TS-85
As a recap you need to set 'proxy.config.cluster.ethernet_interface' in
'proxy/config/records.config.in' to a valid interface like 'eth0'.
You should be able to bring up the traffic_cop->traffic_manager->traffic_server
sudo /usr/local/trafficserver/bin/traffic_cop &
To shutdown 'traffic_cop' you can do the following on linux:
sudo killall -s QUIT traffic_cop
This will currently only bring down 'traffic_cop'. To shutdown down
'traffic_manager' and 'traffic_server' you can do the following on linux:
sudo killall -s QUIT traffic_manager
Traffic Manger will come up with the Web interface disabled but you can execute
the 'sudo $PREFIX/bin/traffic_shell' command and see some cache, proxy and http
stats.
-George
> traffic_cop does not start
> --------------------------
>
> Key: TS-52
> URL: https://issues.apache.org/jira/browse/TS-52
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.0a
> Environment: All linux
> Reporter: George Paul
> Attachments: TS-52_traffic_cop_patch1.diff,
> TS-52_traffic_cop_patch2.diff, TS-52_traffic_cop_patch3.diff
>
>
> Currently Traffic Cop does not start and will not bring up Traffic Manager &
> Traffic Server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
