[jira] [Resolved] (TS-2348) rename tstop to traffic_top
[
https://issues.apache.org/jira/browse/TS-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach resolved TS-2348.
-
Resolution: Fixed
Fix Version/s: 4.2.0
> rename tstop to traffic_top
> ---
>
> Key: TS-2348
> URL: https://issues.apache.org/jira/browse/TS-2348
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Management, Quality
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 4.2.0
>
>
> We should rename the {{tstop}} tool to {{traffic_top}} for consistency with
> the rest of our command set.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2348) rename tstop to traffic_top
[
https://issues.apache.org/jira/browse/TS-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821962#comment-13821962
]
ASF subversion and git services commented on TS-2348:
-
Commit 88666ad43f65f5218602955b2bffcf2ba1883d30 in branch refs/heads/master
from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=88666ad ]
TS-2348: Rename tstop to traffic_top
> rename tstop to traffic_top
> ---
>
> Key: TS-2348
> URL: https://issues.apache.org/jira/browse/TS-2348
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Management, Quality
>Reporter: James Peach
>Assignee: James Peach
>
> We should rename the {{tstop}} tool to {{traffic_top}} for consistency with
> the rest of our command set.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2348) rename tstop to traffic_top
[
https://issues.apache.org/jira/browse/TS-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821959#comment-13821959
]
James Peach commented on TS-2348:
-
Consistency is more important than having a nice name :)
> rename tstop to traffic_top
> ---
>
> Key: TS-2348
> URL: https://issues.apache.org/jira/browse/TS-2348
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Management, Quality
>Reporter: James Peach
>Assignee: James Peach
>
> We should rename the {{tstop}} tool to {{traffic_top}} for consistency with
> the rest of our command set.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (TS-2348) rename tstop to traffic_top
[
https://issues.apache.org/jira/browse/TS-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach reassigned TS-2348:
---
Assignee: James Peach
> rename tstop to traffic_top
> ---
>
> Key: TS-2348
> URL: https://issues.apache.org/jira/browse/TS-2348
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Management, Quality
>Reporter: James Peach
>Assignee: James Peach
>
> We should rename the {{tstop}} tool to {{traffic_top}} for consistency with
> the rest of our command set.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (TS-2348) rename tstop to traffic_top
James Peach created TS-2348:
---
Summary: rename tstop to traffic_top
Key: TS-2348
URL: https://issues.apache.org/jira/browse/TS-2348
Project: Traffic Server
Issue Type: Bug
Components: Cleanup, Management, Quality
Reporter: James Peach
We should rename the {{tstop}} tool to {{traffic_top}} for consistency with the
rest of our command set.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2343) Remove the --schema option from Traffic Manager
[ https://issues.apache.org/jira/browse/TS-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821894#comment-13821894 ] ASF subversion and git services commented on TS-2343: - Commit 7d469d00efe3500ce826b427221007feca2144fb in branch refs/heads/5.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=7d469d0 ] Added TS-2343. > Remove the --schema option from Traffic Manager > --- > > Key: TS-2343 > URL: https://issues.apache.org/jira/browse/TS-2343 > Project: Traffic Server > Issue Type: Improvement > Components: Management >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 4.2.0 > > > There's a "-schema" option for traffic_manager, which is only partially > implemented (and we have no default scheme file to provide for it). From what > I can surmise, the intent was to allow for a schema based validation of > records.config. > Now, I suspect this -schema option was done prior to RecordsConfig.cc > refactoring. As such, I feel it's unnecessary, since RecordsConfig supports > validation "rules" for each configuration. > Finally, since this feature has no usable configurations or features, I > suggest eliminating it for v4.2.0, but I could be convinced to move it out > for v5.0.x. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2340) TSTextLogObject broken
[
https://issues.apache.org/jira/browse/TS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821896#comment-13821896
]
ASF subversion and git services commented on TS-2340:
-
Commit 2abdac235754fc7e60f78f3377f2d45e28ed4f34 in branch refs/heads/5.0.x from
[~bettydreamit]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=2abdac2 ]
TS-2340: fix TextLogObject log rolling
> TSTextLogObject broken
> --
>
> Key: TS-2340
> URL: https://issues.apache.org/jira/browse/TS-2340
> Project: Traffic Server
> Issue Type: Bug
>Reporter: bettydramit
>Assignee: James Peach
> Fix For: 4.2.0
>
>
> The cache url log error
> [Nov 11 21:12:19.246] Server {0x2b9709141700} NOTE: Rolling interval adjusted
> from 0 sec to 300 sec for /var/log/trafficserver/cacheurl.log
> when restart ate , It will rolling
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2343) Remove the --schema option from Traffic Manager
[ https://issues.apache.org/jira/browse/TS-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821895#comment-13821895 ] ASF subversion and git services commented on TS-2343: - Commit e754a1d0ce0c511586ac31654850a532c6a3d518 in branch refs/heads/5.0.x from [~zwoop] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e754a1d ] TS-2343 Remove --schema from docs, well the little that was there > Remove the --schema option from Traffic Manager > --- > > Key: TS-2343 > URL: https://issues.apache.org/jira/browse/TS-2343 > Project: Traffic Server > Issue Type: Improvement > Components: Management >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 4.2.0 > > > There's a "-schema" option for traffic_manager, which is only partially > implemented (and we have no default scheme file to provide for it). From what > I can surmise, the intent was to allow for a schema based validation of > records.config. > Now, I suspect this -schema option was done prior to RecordsConfig.cc > refactoring. As such, I feel it's unnecessary, since RecordsConfig supports > validation "rules" for each configuration. > Finally, since this feature has no usable configurations or features, I > suggest eliminating it for v4.2.0, but I could be convinced to move it out > for v5.0.x. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (TS-2347) buffer_upload uses unsafe function tempnam()
Igor Galić created TS-2347:
--
Summary: buffer_upload uses unsafe function tempnam()
Key: TS-2347
URL: https://issues.apache.org/jira/browse/TS-2347
Project: Traffic Server
Issue Type: Bug
Components: Plugins
Reporter: Igor Galić
{code}
make[3]: Entering directory
`/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/buffer_upload'
CXX buffer_upload.lo
CXXLDbuffer_upload.la
.libs/buffer_upload.o: In function `attach_pvc_plugin(tsapi_cont*, TSEvent,
void*)':
/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/buffer_upload/../../../../plugins/experimental/buffer_upload/buffer_upload.cc:915:
warning: the use of `tempnam' is dangerous, better use `mkstemp'
make[3]: Leaving directory
`/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/buffer_upload'
Making all in esi
make[3]: Entering directory
`/home/igalic/src/asf/trafficserver/bldir/plugins/experimental/esi'
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Closed] (TS-2346) tstop link error: undefined reference to `ink_atoi64(char const*)'
[
https://issues.apache.org/jira/browse/TS-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Galić closed TS-2346.
--
Resolution: Invalid
Assignee: Igor Galić
Well, that was silly. The build is picking up the previous installation under
$prefix, that's why it's trying to link against an ink_atoi64 with a different
contract.
> tstop link error: undefined reference to `ink_atoi64(char const*)'
> ---
>
> Key: TS-2346
> URL: https://issues.apache.org/jira/browse/TS-2346
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
>Reporter: Igor Galić
>Assignee: Igor Galić
>
> I consistently get this failure on Linux with 4.1.x as soon as I change
> {{--prefix}}. No other {{configure}} option makes a difference.
> {code}
> make[1]: Leaving directory `/home/igalic/src/asf/trafficserver/plugins'
> Making all in tools
> make[1]: Entering directory `/home/igalic/src/asf/trafficserver/tools'
> CXXLDtstop/tstop
> ../mgmt/api/remote/.libs/libtsmgmt.so: undefined reference to
> `ink_atoi64(char const*)'
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> make[1]: *** [tstop/tstop] Error 1
> make[1]: Leaving directory `/home/igalic/src/asf/trafficserver/tools'
> make: *** [all-recursive] Error 1
> 2 igalic@levix ~/src/asf/trafficserver (git)-[4.1.2] % cd -
> ~/src/asf/trafficserver/tools
> igalic@levix ~/src/asf/trafficserver/tools (git)-[4.1.2] % readelf -a
> ../mgmt/api/remote/.libs/libtsmgmt.so | c++filt | grep ink_atoi64
> 0022cb00 00490007 R_X86_64_JUMP_SLO ink_atoi64(char
> const*) + 0
> 73: 0 FUNCGLOBAL DEFAULT UND ink_atoi64(char
> const*)
>601: 0 FUNCGLOBAL DEFAULT UND ink_atoi64(char
> const*)
> igalic@levix ~/src/asf/trafficserver/tools (git)-[4.1.2] %
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (TS-2346) tstop link error: undefined reference to `ink_atoi64(char const*)'
Igor Galić created TS-2346:
--
Summary: tstop link error: undefined reference to
`ink_atoi64(char const*)'
Key: TS-2346
URL: https://issues.apache.org/jira/browse/TS-2346
Project: Traffic Server
Issue Type: Bug
Components: Build
Reporter: Igor Galić
I consistently get this failure on Linux with 4.1.x as soon as I change
{{--prefix}}. No other {{configure}} option makes a difference.
{code}
make[1]: Leaving directory `/home/igalic/src/asf/trafficserver/plugins'
Making all in tools
make[1]: Entering directory `/home/igalic/src/asf/trafficserver/tools'
CXXLDtstop/tstop
../mgmt/api/remote/.libs/libtsmgmt.so: undefined reference to `ink_atoi64(char
const*)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [tstop/tstop] Error 1
make[1]: Leaving directory `/home/igalic/src/asf/trafficserver/tools'
make: *** [all-recursive] Error 1
2 igalic@levix ~/src/asf/trafficserver (git)-[4.1.2] % cd -
~/src/asf/trafficserver/tools
igalic@levix ~/src/asf/trafficserver/tools (git)-[4.1.2] % readelf -a
../mgmt/api/remote/.libs/libtsmgmt.so | c++filt | grep ink_atoi64
0022cb00 00490007 R_X86_64_JUMP_SLO ink_atoi64(char
const*) + 0
73: 0 FUNCGLOBAL DEFAULT UND ink_atoi64(char
const*)
601: 0 FUNCGLOBAL DEFAULT UND ink_atoi64(char
const*)
igalic@levix ~/src/asf/trafficserver/tools (git)-[4.1.2] %
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2340) TSTextLogObject broken
[
https://issues.apache.org/jira/browse/TS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821543#comment-13821543
]
ASF subversion and git services commented on TS-2340:
-
Commit cdf37be6d2a95173115c563d3e61e693bf6fab25 in branch refs/heads/4.1.x from
[~bettydreamit]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=cdf37be ]
TS-2340: fix TextLogObject log rolling
Conflicts:
CHANGES
> TSTextLogObject broken
> --
>
> Key: TS-2340
> URL: https://issues.apache.org/jira/browse/TS-2340
> Project: Traffic Server
> Issue Type: Bug
>Reporter: bettydramit
>Assignee: James Peach
> Fix For: 4.2.0
>
>
> The cache url log error
> [Nov 11 21:12:19.246] Server {0x2b9709141700} NOTE: Rolling interval adjusted
> from 0 sec to 300 sec for /var/log/trafficserver/cacheurl.log
> when restart ate , It will rolling
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (TS-2345) failed assert in Regression test SDK_API_HttpTxnTransform
Thomas Berger created TS-2345:
-
Summary: failed assert in Regression test SDK_API_HttpTxnTransform
Key: TS-2345
URL: https://issues.apache.org/jira/browse/TS-2345
Project: Traffic Server
Issue Type: Bug
Components: TS API
Reporter: Thomas Berger
The regression test for SDK_API_HttpTxnTransform failes with an assertion
failure:
{noformat}
FATAL:
/var/tmp/paludis/net-proxy-trafficserver-4.1.1/work/trafficserver-4.1.1/proxy/InkAPITest.cc:7151:
failed assert `request_id != -1`
traffic_server - STACK TRACE:
/usr/lib64/libtsutil.so.4(+0x14aff)[0x7f4d7237caff]
/usr/lib64/libtsutil.so.4(+0x13e4f)[0x7f4d7237be4f]
traffic_server[0x4a7936]
traffic_server[0x4f299d]
traffic_server(_ZN6HttpSM17state_api_calloutEiPv+0x532)[0x508542]
traffic_server(_ZN6HttpSM14set_next_stateEv+0xf0a)[0x5179ea]
traffic_server(_ZN6HttpSM32state_read_client_request_headerEiPv+0x71c)[0x505e3c]
traffic_server(_ZN6HttpSM12main_handlerEiPv+0x99)[0x504979]
traffic_server(_ZN18UnixNetVConnection11net_read_ioEP10NetHandlerP7EThread+0x438)[0x6152e8]
traffic_server(_ZN10NetHandler12mainNetEventEiP5Event+0x4ea)[0x60fb6a]
traffic_server(_ZN7EThread13process_eventEP5Eventi+0xc7)[0x62c257]
traffic_server(_ZN7EThread7executeEv+0x5a4)[0x62c9b4]
traffic_server[0x62b32e]
/lib64/libpthread.so.0(+0x8fe6)[0x7f4d70a18fe6]
/lib64/libc.so.6(clone+0x6d)[0x7f4d7001a8ad]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (TS-2344) 404 error was logged while url redirect request was processed corrctly
[ https://issues.apache.org/jira/browse/TS-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821374#comment-13821374 ] Eddie commented on TS-2344: --- One more thing, the 'http:///' in the log message is really misleading. I spent a lot of time trying to figure out who is sending this empty host request. > 404 error was logged while url redirect request was processed corrctly > -- > > Key: TS-2344 > URL: https://issues.apache.org/jira/browse/TS-2344 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Eddie > > I am seeing a lot of entries in the error log for my url redirect request. > The request was processed correctly and I could see the expected response in > log as below: > 2013-11-08 18:23:37 301 FIN http://yahoo.com > http://www.yahoo.com/ > But log messages like following were printed in the error log too, which > generates a lot of error logs (log rotation configured) and filling up disk > space pretty fast. > 20131108.18h23m37s RESPONSE: sent status 404 (Not Found on > Accelerator) for 'http:///' > 20131108.18h23m37s RESPONSE: sent status 301 (Redirect) > for 'http:///' > I watched my tcpdump log and did not see that the 404 error was sent out at > all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in > the error log for my url redirect request. The request was processed correctly > I could see the expected response in log as well: > 2013-11-08 18:23:37 301 FIN http://yahoo.com > http://www.yahoo.com/ > But log messages like following were printed too: > 20131108.18h23m37s RESPONSE: sent status 404 (Not Found on > Accelerator) for 'http:///' > 20131108.18h23m37s RESPONSE: sent status 301 (Redirect) > for 'http:///' > I watched my tcpdump log and did not see that the 404 error was sent out at > all. I am using ATS/3.2.4 and following > is the log configuration. > CONFIG proxy.config.log.logging_enabled INT 3 > CONFIG proxy.config.log.max_secs_per_buffer INT 1 > CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 > CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 > CONFIG proxy.config.log.max_space_mb_headroom INT 1000 > CONFIG proxy.config.log.hostname STRING localhost > CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver > CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- > CONFIG proxy.config.log.custom_logs_enabled INT 1 > CONFIG proxy.config.log.squid_log_enabled INT 0 > CONFIG proxy.config.log.squid_log_is_ascii INT 0 > CONFIG proxy.config.log.squid_log_name STRING squid > CONFIG proxy.config.log.squid_log_header STRING NULL > CONFIG proxy.config.log.common_log_enabled INT 0 > CONFIG proxy.config.log.common_log_is_ascii INT 1 > CONFIG proxy.config.log.common_log_name STRING common > CONFIG proxy.config.log.common_log_header STRING NULL > CONFIG proxy.config.log.extended_log_enabled INT 0 > CONFIG proxy.config.log.extended_log_is_ascii INT 0 > CONFIG proxy.config.log.extended_log_name STRING extended > CONFIG proxy.config.log.extended_log_header STRING NULL > CONFIG proxy.config.log.extended2_log_enabled INT 0 > CONFIG proxy.config.log.extended2_log_is_ascii INT 1 > CONFIG proxy.config.log.extended2_log_name STRING extended2 > CONFIG proxy.config.log.extended2_log_header STRING NULL > CONFIG proxy.config.log.separate_icp_logs INT 0 > CONFIG proxy.config.log.separate_host_logs INT 0 > Is this a bug or is this a misconfiguration? Does anyone have any idea?) and > following is the log configuration. > CONFIG proxy.config.log.logging_enabled INT 3 > CONFIG proxy.config.log.max_secs_per_buffer INT 1 > CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 > CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 > CONFIG proxy.config.log.max_space_mb_headroom INT 1000 > CONFIG proxy.config.log.hostname STRING localhost > CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver > CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- > CONFIG proxy.config.log.custom_logs_enabled INT 1 > CONFIG proxy.config.log.squid_log_enabled INT 0 > CONFIG proxy.config.log.squid_log_is_ascii INT 0 > CONFIG proxy.config.log.squid_log_name STRING squid > CONFIG proxy.config.log.squid_log_header STRING NULL > CONFIG proxy.config.log.common_log_enabled INT 0 > CONFIG proxy.config.log.common_log_is_ascii INT 1 > CONFIG proxy.config.log.common_log_name STRING common > CONFIG proxy.config.log.common_log_header STRING NULL > CONFIG proxy.config.log.extended_log_enabled INT 0 > CONFIG proxy.config.log.extended_log_is_ascii INT 0 > CONFIG proxy.config.log.extended_log_name STRING extended > CONFIG proxy.config.log.extended_log_header STRING NULL > CONFIG proxy.config.log.extended2_log_enabled INT 0 > CONFIG pr
[jira] [Created] (TS-2344) 404 error was logged while url redirect request was processed corrctly
Eddie created TS-2344: - Summary: 404 error was logged while url redirect request was processed corrctly Key: TS-2344 URL: https://issues.apache.org/jira/browse/TS-2344 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Eddie I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly and I could see the expected response in log as below: 2013-11-08 18:23:37 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed in the error log too, which generates a lot of error logs (log rotation configured) and filling up disk space pretty fast. 20131108.18h23m37s RESPONSE: sent status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 (also checked with I am seeing a lot of entries in the error log for my url redirect request. The request was processed correctly I could see the expected response in log as well: 2013-11-08 18:23:37 301 FIN http://yahoo.com http://www.yahoo.com/ But log messages like following were printed too: 20131108.18h23m37s RESPONSE: sent status 404 (Not Found on Accelerator) for 'http:///' 20131108.18h23m37s RESPONSE: sent status 301 (Redirect) for 'http:///' I watched my tcpdump log and did not see that the 404 error was sent out at all. I am using ATS/3.2.4 and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG proxy.config.log.extended_log_name STRING extended CONFIG proxy.config.log.extended_log_header STRING NULL CONFIG proxy.config.log.extended2_log_enabled INT 0 CONFIG proxy.config.log.extended2_log_is_ascii INT 1 CONFIG proxy.config.log.extended2_log_name STRING extended2 CONFIG proxy.config.log.extended2_log_header STRING NULL CONFIG proxy.config.log.separate_icp_logs INT 0 CONFIG proxy.config.log.separate_host_logs INT 0 Is this a bug or is this a misconfiguration? Does anyone have any idea?) and following is the log configuration. CONFIG proxy.config.log.logging_enabled INT 3 CONFIG proxy.config.log.max_secs_per_buffer INT 1 CONFIG proxy.config.log.max_space_mb_for_logs INT 25000 CONFIG proxy.config.log.max_space_mb_for_orphan_logs INT 25 CONFIG proxy.config.log.max_space_mb_headroom INT 1000 CONFIG proxy.config.log.hostname STRING localhost CONFIG proxy.config.log.logfile_dir STRING var/log/trafficserver CONFIG proxy.config.log.logfile_perm STRING rw-r--r-- CONFIG proxy.config.log.custom_logs_enabled INT 1 CONFIG proxy.config.log.squid_log_enabled INT 0 CONFIG proxy.config.log.squid_log_is_ascii INT 0 CONFIG proxy.config.log.squid_log_name STRING squid CONFIG proxy.config.log.squid_log_header STRING NULL CONFIG proxy.config.log.common_log_enabled INT 0 CONFIG proxy.config.log.common_log_is_ascii INT 1 CONFIG proxy.config.log.common_log_name STRING common CONFIG proxy.config.log.common_log_header STRING NULL CONFIG proxy.config.log.extended_log_enabled INT 0 CONFIG proxy.config.log.extended_log_is_ascii INT 0 CONFIG proxy.config.log.extended_log_name STRING extended CONFIG proxy.config.log.extended_log_header STRING NULL CONFIG proxy.config.log.extended2_log_enabled INT 0 CONFIG proxy.config.log.extended2_log_is_ascii INT 1 CONFIG proxy.config.log.extended2_log_name STRING extended2 CONFIG proxy.config.log.extended2_log_header STRING NULL CONFIG proxy.config.log.separate_icp_logs INT 0 CONFIG proxy.config.log.separate_host_logs INT 0 Is this a bug or is this a misconfiguration? Does anyone have any idea? Also, I noticed that with ATS/4.0.1, if there is no URL redirect rule defined in remap.config, I will not see the following response back as ATS 3.2.4: HTTP/1.1 404 Not Found on Accelerator Date: Wed, 13 Nov
[jira] [Commented] (TS-2335) Putting Alibaba Lua plugin into /experimental
[ https://issues.apache.org/jira/browse/TS-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821175#comment-13821175 ] portl4t commented on TS-2335: - 1. I tested the performance of ts-lua with 'header rewrite' case, and ts-lua performs well, but I suggest you test it yourself with your own case and make a comparison. 2. A lua context can be used by multiple client requests with lock protected, and HttpSM won't be blocked by ts-lua, I suggest TS_LUA_MAX_STATE_COUNT to be 2048 or more. > Putting Alibaba Lua plugin into /experimental > - > > Key: TS-2335 > URL: https://issues.apache.org/jira/browse/TS-2335 > Project: Traffic Server > Issue Type: New Feature > Components: Plugins >Reporter: Kit Chan > > There is an awesome plugin created by Alibaba engineer - portl4t > https://github.com/portl4t/ts-lua/ > There is a mail thread on dev mailing list and the author agrees to put it to > ATS source as well. > So I would like to start things off with filing a jira first. > I think it would be nice to put it into /experimental/ to start things first. -- This message was sent by Atlassian JIRA (v6.1#6144)
