[jira] [Updated] (TS-714) traffic_shell broken
[
https://issues.apache.org/jira/browse/TS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billy Vierra updated TS-714:
Description:
traffic_shell appears to be broken in 2.5.0 all the way through trunk (works
fine in 2.4.0)
--
\# traffic_shell
Successfully Initialized MgmtAPI in /var/trafficserver
% show:security
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
Web Interface Port - -1
Traffic Server Access
---
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
command returned bad code: 9
--
traffic.out shows:
[Mar 20 21:51:04.702] Manager {1143769408} ERROR: [preprocess_msg] ERROR: 22 is
invalid op type
[Mar 20 21:51:04.703] Manager {1143769408} ERROR: (last system error 32:
Broken pipe)
I do not believe that it is the mgmtapi however as the Apache::TS::AdminClient
perl module works fine.
was:
traffic_shell appears to be broken in 2.5.0 all the way through trunk (works
fine in 2.4.0)
--
# traffic_shell
Successfully Initialized MgmtAPI in /var/trafficserver
% show:security
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
Web Interface Port - -1
Traffic Server Access
---
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
command returned bad code: 9
--
traffic.out shows:
[Mar 20 21:51:04.702] Manager {1143769408} ERROR: [preprocess_msg] ERROR: 22 is
invalid op type
[Mar 20 21:51:04.703] Manager {1143769408} ERROR: (last system error 32:
Broken pipe)
I do not believe that it is the mgmtapi however as the Apache::TS::AdminClient
perl module works fine.
traffic_shell broken
Key: TS-714
URL: https://issues.apache.org/jira/browse/TS-714
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 2.1.7, 2.1.6, 2.1.5
Reporter: Billy Vierra
Labels: traffic_shell
traffic_shell appears to be broken in 2.5.0 all the way through trunk (works
fine in 2.4.0)
--
\# traffic_shell
Successfully Initialized MgmtAPI in /var/trafficserver
% show:security
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
Web Interface Port - -1
Traffic Server Access
---
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
command returned bad code: 9
--
traffic.out shows:
[Mar 20 21:51:04.702] Manager {1143769408} ERROR: [preprocess_msg] ERROR: 22
is invalid op type
[Mar 20 21:51:04.703] Manager {1143769408} ERROR: (last system error 32:
Broken pipe)
I do not believe that it is the mgmtapi however as the
Apache::TS::AdminClient perl module works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-714) traffic_shell broken
traffic_shell broken
Key: TS-714
URL: https://issues.apache.org/jira/browse/TS-714
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 2.1.5, 2.1.6, 2.1.7
Reporter: Billy Vierra
traffic_shell appears to be broken in 2.5.0 all the way through trunk (works
fine in 2.4.0)
--
# traffic_shell
Successfully Initialized MgmtAPI in /var/trafficserver
% show:security
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
Web Interface Port - -1
Traffic Server Access
---
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
command returned bad code: 9
--
traffic.out shows:
[Mar 20 21:51:04.702] Manager {1143769408} ERROR: [preprocess_msg] ERROR: 22 is
invalid op type
[Mar 20 21:51:04.703] Manager {1143769408} ERROR: (last system error 32:
Broken pipe)
I do not believe that it is the mgmtapi however as the Apache::TS::AdminClient
perl module works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TS-715) Apache::TS::AdminClient broken in trunk
Apache::TS::AdminClient broken in trunk --- Key: TS-715 URL: https://issues.apache.org/jira/browse/TS-715 Project: Traffic Server Issue Type: Bug Components: Management Affects Versions: 2.1.7 Reporter: Billy Vierra funtion get_stat uses a function called float if $resp[2] == TS_REC_STRING. float is not a standard perl function and is not defined anywhere in the module. I have created a patch that fixes this along with: * Cleans up code * perltidy's code * Add a function: _find_socket that will check multiple locations to see if the socket exists if one is not passed. * Changed required perl version in Makefile.PL from perl 5.10.1 to perl 5.8.8 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-715) Apache::TS::AdminClient broken in trunk
[ https://issues.apache.org/jira/browse/TS-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Vierra updated TS-715: Attachment: apache-ts-adminclient.patch Apache::TS::AdminClient broken in trunk --- Key: TS-715 URL: https://issues.apache.org/jira/browse/TS-715 Project: Traffic Server Issue Type: Bug Components: Management Affects Versions: 2.1.7 Reporter: Billy Vierra Attachments: apache-ts-adminclient.patch funtion get_stat uses a function called float if $resp[2] == TS_REC_STRING. float is not a standard perl function and is not defined anywhere in the module. I have created a patch that fixes this along with: * Cleans up code * perltidy's code * Add a function: _find_socket that will check multiple locations to see if the socket exists if one is not passed. * Changed required perl version in Makefile.PL from perl 5.10.1 to perl 5.8.8 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-715) Apache::TS::AdminClient broken in trunk
[ https://issues.apache.org/jira/browse/TS-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-715: Assignee: Leif Hedstrom Apache::TS::AdminClient broken in trunk --- Key: TS-715 URL: https://issues.apache.org/jira/browse/TS-715 Project: Traffic Server Issue Type: Bug Components: Management Affects Versions: 2.1.7 Reporter: Billy Vierra Assignee: Leif Hedstrom Attachments: apache-ts-adminclient.patch funtion get_stat uses a function called float if $resp[2] == TS_REC_STRING. float is not a standard perl function and is not defined anywhere in the module. I have created a patch that fixes this along with: * Cleans up code * perltidy's code * Add a function: _find_socket that will check multiple locations to see if the socket exists if one is not passed. * Changed required perl version in Makefile.PL from perl 5.10.1 to perl 5.8.8 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-714) traffic_shell broken
[
https://issues.apache.org/jira/browse/TS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-714:
Assignee: Leif Hedstrom
traffic_shell broken
Key: TS-714
URL: https://issues.apache.org/jira/browse/TS-714
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 2.1.7, 2.1.6, 2.1.5
Reporter: Billy Vierra
Assignee: Leif Hedstrom
Labels: traffic_shell
traffic_shell appears to be broken in 2.5.0 all the way through trunk (works
fine in 2.4.0)
--
\# traffic_shell
Successfully Initialized MgmtAPI in /var/trafficserver
% show:security
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
Web Interface Port - -1
Traffic Server Access
---
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
command returned bad code: 9
--
traffic.out shows:
[Mar 20 21:51:04.702] Manager {1143769408} ERROR: [preprocess_msg] ERROR: 22
is invalid op type
[Mar 20 21:51:04.703] Manager {1143769408} ERROR: (last system error 32:
Broken pipe)
I do not believe that it is the mgmtapi however as the
Apache::TS::AdminClient perl module works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-714) traffic_shell broken
[
https://issues.apache.org/jira/browse/TS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-714:
-
Fix Version/s: 2.1.8
traffic_shell broken
Key: TS-714
URL: https://issues.apache.org/jira/browse/TS-714
Project: Traffic Server
Issue Type: Bug
Components: Management
Affects Versions: 2.1.7, 2.1.6, 2.1.5
Reporter: Billy Vierra
Assignee: Leif Hedstrom
Labels: traffic_shell
Fix For: 2.1.8
traffic_shell appears to be broken in 2.5.0 all the way through trunk (works
fine in 2.4.0)
--
\# traffic_shell
Successfully Initialized MgmtAPI in /var/trafficserver
% show:security
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
Web Interface Port - -1
Traffic Server Access
---
ERROR: Timed-out while communicating with traffic_manager.
Ability to make configuration changes depends on traffic_manager.
command returned bad code: 9
--
traffic.out shows:
[Mar 20 21:51:04.702] Manager {1143769408} ERROR: [preprocess_msg] ERROR: 22
is invalid op type
[Mar 20 21:51:04.703] Manager {1143769408} ERROR: (last system error 32:
Broken pipe)
I do not believe that it is the mgmtapi however as the
Apache::TS::AdminClient perl module works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-715) Apache::TS::AdminClient broken in trunk
[ https://issues.apache.org/jira/browse/TS-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-715: - Fix Version/s: 2.1.8 Apache::TS::AdminClient broken in trunk --- Key: TS-715 URL: https://issues.apache.org/jira/browse/TS-715 Project: Traffic Server Issue Type: Bug Components: Management Affects Versions: 2.1.7 Reporter: Billy Vierra Assignee: Leif Hedstrom Fix For: 2.1.8 Attachments: apache-ts-adminclient.patch funtion get_stat uses a function called float if $resp[2] == TS_REC_STRING. float is not a standard perl function and is not defined anywhere in the module. I have created a patch that fixes this along with: * Cleans up code * perltidy's code * Add a function: _find_socket that will check multiple locations to see if the socket exists if one is not passed. * Changed required perl version in Makefile.PL from perl 5.10.1 to perl 5.8.8 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-633) SSL Termination reverse_mapping
[ https://issues.apache.org/jira/browse/TS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Aguado Sánchez updated TS-633: - Attachment: UrlRewrite.cc.patch This patch fixes the issue with reverse_map and different URL schemes. SSL Termination reverse_mapping --- Key: TS-633 URL: https://issues.apache.org/jira/browse/TS-633 Project: Traffic Server Issue Type: Bug Components: Remap API, SSL Affects Versions: 2.1.0 Reporter: Andreas Hartke Fix For: 2.1.8 Attachments: UrlRewrite.cc.patch We configure reverse_proxy with SSL Termination and have problems with respones from the origin server containing http-adresses. If the origin server sends reponses with addresses the reverse_mapped adresses from trafficserver contain http instead of https. Here our configuration: map https://asp2.geomagic.de/path/ http://origin_server:8080/path/ reverse_map http://origin_server:8080/path/ https://asp2.geomagic.de/path/ redirect_temporary https://asp2.geomagic.de/path https://asp2.geomagic.de/path/ The redirection from https to https works fine but a redirect_temporary from a http-adress to a https-address maps to a http-address instead of a https-address. redirect_temporary http://asp2.geomagic.de/gasline https://asp2.geomagic.de/gasline/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TS-633) SSL Termination reverse_mapping
[ https://issues.apache.org/jira/browse/TS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009353#comment-13009353 ] Carlos Aguado Sánchez edited comment on TS-633 at 3/21/11 8:26 PM: --- Problem found: attached is the patch that fixes the issue with reverse_map and different URL schemes. was (Author: caguado): This patch fixes the issue with reverse_map and different URL schemes. SSL Termination reverse_mapping --- Key: TS-633 URL: https://issues.apache.org/jira/browse/TS-633 Project: Traffic Server Issue Type: Bug Components: Remap API, SSL Affects Versions: 2.1.0 Reporter: Andreas Hartke Fix For: 2.1.8 Attachments: UrlRewrite.cc.patch We configure reverse_proxy with SSL Termination and have problems with respones from the origin server containing http-adresses. If the origin server sends reponses with addresses the reverse_mapped adresses from trafficserver contain http instead of https. Here our configuration: map https://asp2.geomagic.de/path/ http://origin_server:8080/path/ reverse_map http://origin_server:8080/path/ https://asp2.geomagic.de/path/ redirect_temporary https://asp2.geomagic.de/path https://asp2.geomagic.de/path/ The redirection from https to https works fine but a redirect_temporary from a http-adress to a https-address maps to a http-address instead of a https-address. redirect_temporary http://asp2.geomagic.de/gasline https://asp2.geomagic.de/gasline/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-550) Eliminate some uncessary usages of STL on the crititcal path
[ https://issues.apache.org/jira/browse/TS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-550. -- Resolution: Fixed Eliminate some uncessary usages of STL on the crititcal path Key: TS-550 URL: https://issues.apache.org/jira/browse/TS-550 Project: Traffic Server Issue Type: Bug Components: Cleanup Reporter: Leif Hedstrom Assignee: Leif Hedstrom Fix For: 2.1.8 Moving out some non-critical bugs to v2.1.7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-633) SSL Termination reverse_mapping
[ https://issues.apache.org/jira/browse/TS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-633: Assignee: Leif Hedstrom SSL Termination reverse_mapping --- Key: TS-633 URL: https://issues.apache.org/jira/browse/TS-633 Project: Traffic Server Issue Type: Bug Components: Remap API, SSL Affects Versions: 2.1.0 Reporter: Andreas Hartke Assignee: Leif Hedstrom Fix For: 2.1.8 Attachments: UrlRewrite.cc.patch We configure reverse_proxy with SSL Termination and have problems with respones from the origin server containing http-adresses. If the origin server sends reponses with addresses the reverse_mapped adresses from trafficserver contain http instead of https. Here our configuration: map https://asp2.geomagic.de/path/ http://origin_server:8080/path/ reverse_map http://origin_server:8080/path/ https://asp2.geomagic.de/path/ redirect_temporary https://asp2.geomagic.de/path https://asp2.geomagic.de/path/ The redirection from https to https works fine but a redirect_temporary from a http-adress to a https-address maps to a http-address instead of a https-address. redirect_temporary http://asp2.geomagic.de/gasline https://asp2.geomagic.de/gasline/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-654) request for support of Layer7 http health checking for Origin Servers
[ https://issues.apache.org/jira/browse/TS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mohan_zl updated TS-654: Attachment: TS-654-v2.patch Keep up with latest trunk request for support of Layer7 http health checking for Origin Servers - Key: TS-654 URL: https://issues.apache.org/jira/browse/TS-654 Project: Traffic Server Issue Type: New Feature Components: HTTP Affects Versions: 2.1.5 Reporter: Zhao Yongming Fix For: 2.1.8 Attachments: Passive-L7-Health-Check.patch, TS-654-v2.patch this ticket is for the L7 health checking project: https://cwiki.apache.org/confluence/display/TS/HttpHealthCheck -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
