You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "George Paul (JIRA)" <ji...@apache.org> on 2009/12/01 01:52:21 UTC
[jira] Created: (TS-52) traffic_cop does not start
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
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.
[jira] Updated: (TS-52) traffic_cop does not start
Posted by "George Paul (JIRA)" <ji...@apache.org>.
[ 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_patch1.diff
This patch uses PREFIX, PKGLOCALSTATEDIR and PKGSYSCONFDIR to set default locations for config files, logs, etc. This patch was used in conjuction with patches TS-21_stats_patch1.diff and TS-6_traffic_manager_patch1.diff. This patch also replaces TS-36_patch1.diff
patch -p0 -i TS-21_stats_patch1.diff
patch -p0 -i TS-6_traffic_manager_patch1.diff
patch -p0 -i TS-52_traffic_cop_patch1.diff
If your 'traffic_manager' does not start and you see message like the following in /var/log/syslog:
Nov 19 17:36:12 wopr traffic_manager[25918]: {2243651312} NOTE: [LocalManager::initCCom] Unable to find network interface (null). Exiting...
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
Please note that the WebUI is disabled and will need to be fixed but the 'traffic_shell' should work to view some proxy, http and cache statistics.
Please review and let me know if there are any issues.
-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
>
>
> 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.
[jira] Resolved: (TS-52) traffic_cop does not start
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom resolved TS-52.
-----------------------------
Resolution: Fixed
Committed. Thanks 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.
[jira] Updated: (TS-52) traffic_cop does not start
Posted by "George Paul (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (TS-52) traffic_cop does not start
Posted by "George Paul (JIRA)" <ji...@apache.org>.
[ 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_patch2.diff
This updated patch replaces TS-52_traffic_cop_patch1.diff and reflects changes incorporated by patch TS-21_stats_patch3.diff and TS-6_traffic_manager_patch2.diff.
patch -p0 -i TS-6_traffic_manager_patch2.diff
patch -p0 -i TS-52_traffic_cop_patch2.diff
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.
Please review and let me know if there are any issues.
-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
>
>
> 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.
[jira] Commented: (TS-52) traffic_cop does not start
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790386#action_12790386 ]
Leif Hedstrom commented on TS-52:
---------------------------------
A few comments (these similar to the comments in TS-6):
In this patch, you do
+static char local_state_dir[PATH_MAX];
which I think is good, but inconsistent with your TS-6 patch.
This comment should be changed, to reflect that the "root" dir is whatever --prefix was specified, or /usr/local:
+ if (stat(log_dir, &stat_buf) < 0) {
+ // Try 'root_dir/var/log/trafficserver' directory
+ snprintf(log_dir, sizeof(log_dir), "%s%s%s%s%s%s%s",
+ root_dir, DIR_SEP,"var",DIR_SEP,"log",DIR_SEP,"trafficserver");
For this:
- if ((env_path = getenv("ROOT")) || (env_path = getenv("INST_ROOT"))) {
+ if ((env_path = getenv("ATS_ROOT")) || (env_path = getenv("ATS_INST_ROOT"))) {
Just as in TS-6, lets standardize on one environment variable only, $TS_ROOT.
This error message should be fixed accordingly:
+ cop_log(COP_FATAL," please set correct path in either env variable ATS_ROOT or in /etc/traffic_server \n");
Lets make sure we use TS_ROOT consistently through the code, and $prefix/{etc,var}/trafficserver as the defaults.
> 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
>
>
> 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.