[jira] [Updated] (TS-902) Crash report: invalid ip range in remap.config crash server
[
https://issues.apache.org/jira/browse/TS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-902:
-
Fix Version/s: (was: 3.3.3)
3.3.2
Assignee: Leif Hedstrom
Crash report: invalid ip range in remap.config crash server
---
Key: TS-902
URL: https://issues.apache.org/jira/browse/TS-902
Project: Traffic Server
Issue Type: Bug
Components: Configuration, HTTP
Affects Versions: 3.1.0, 3.0.1
Environment: TS 3.0.1
Reporter: Zhao Yongming
Assignee: Leif Hedstrom
Labels: crash
Fix For: 3.3.2
when I put a strage ip range, ie: src_ip=128.0.0.0-121.14.89.0 in remap ip
filtering, it will cause the server crash:
{code}
[TrafficServer] using root directory '/usr'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '13'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE: [Alarms::signalAlarm]
Server Process born
[Aug 4 11:04:54.222] {46990117603664} STATUS: opened
/var/log/trafficserver/diags.log
[Aug 4 11:04:54.224] {46990117603664} NOTE: updated diags config
[Aug 4 11:04:54.225] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.239] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.343] Server {46990117603664} NOTE: logging initialized[7],
logging_mode = 1
[Aug 4 11:04:54.345] Server {46990117603664} NOTE: PrefetchProcessor:
Started the prefetch processor
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: Could not add rule at
line #1; Aborting!
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: [ReverseProxy] Unable
to parse IP value in src_ip=128.0.0.0-121.14.89.0 at line 1
FATAL: [ReverseProxy] Unable to parse IP value in
src_ip=128.0.0.0-121.14.89.0 at line 1
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x3ab46127dd]
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ab4612938]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x585)[0x580335]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x2fa)[0x58219a]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0xec)[0x4de75c]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x51ee7b]
/usr/bin/traffic_server(main+0xc07)[0x4bf177]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x389961d994]
/usr/bin/traffic_server(__gxx_personality_v0+0x491)[0x4793a9]
[Aug 4 11:04:54.506] Manager {140564987967264} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
{code}
and here is the rules defined in my remap.config:
{code}
.defflt tools @action=deny @src_ip=0.0.0.0-127.0.0.0
@src_ip=128.0.0.0-121.14.89.0 @src_ip=121.14.90.254-255.255.255.255
@method=PURGE
.useflt tools
{code}
well, it is invalid, but we should not crash, right?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-902) Crash report: invalid ip range in remap.config crash server
[
https://issues.apache.org/jira/browse/TS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-902:
-
Fix Version/s: (was: 3.1.4)
3.3.0
Moving all unassigned bugs out to 3.3.0. Move back and assign as necessary.
Crash report: invalid ip range in remap.config crash server
---
Key: TS-902
URL: https://issues.apache.org/jira/browse/TS-902
Project: Traffic Server
Issue Type: Bug
Components: Configuration, HTTP
Affects Versions: 3.1.0, 3.0.1
Environment: TS 3.0.1
Reporter: Zhao Yongming
Labels: crash
Fix For: 3.3.0
when I put a strage ip range, ie: src_ip=128.0.0.0-121.14.89.0 in remap ip
filtering, it will cause the server crash:
{code}
[TrafficServer] using root directory '/usr'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '13'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE: [Alarms::signalAlarm]
Server Process born
[Aug 4 11:04:54.222] {46990117603664} STATUS: opened
/var/log/trafficserver/diags.log
[Aug 4 11:04:54.224] {46990117603664} NOTE: updated diags config
[Aug 4 11:04:54.225] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.239] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.343] Server {46990117603664} NOTE: logging initialized[7],
logging_mode = 1
[Aug 4 11:04:54.345] Server {46990117603664} NOTE: PrefetchProcessor:
Started the prefetch processor
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: Could not add rule at
line #1; Aborting!
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: [ReverseProxy] Unable
to parse IP value in src_ip=128.0.0.0-121.14.89.0 at line 1
FATAL: [ReverseProxy] Unable to parse IP value in
src_ip=128.0.0.0-121.14.89.0 at line 1
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x3ab46127dd]
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ab4612938]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x585)[0x580335]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x2fa)[0x58219a]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0xec)[0x4de75c]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x51ee7b]
/usr/bin/traffic_server(main+0xc07)[0x4bf177]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x389961d994]
/usr/bin/traffic_server(__gxx_personality_v0+0x491)[0x4793a9]
[Aug 4 11:04:54.506] Manager {140564987967264} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
{code}
and here is the rules defined in my remap.config:
{code}
.defflt tools @action=deny @src_ip=0.0.0.0-127.0.0.0
@src_ip=128.0.0.0-121.14.89.0 @src_ip=121.14.90.254-255.255.255.255
@method=PURGE
.useflt tools
{code}
well, it is invalid, but we should not crash, right?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-902) Crash report: invalid ip range in remap.config crash server
[
https://issues.apache.org/jira/browse/TS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-902:
-
Fix Version/s: (was: 3.1.2)
3.1.3
Crash report: invalid ip range in remap.config crash server
---
Key: TS-902
URL: https://issues.apache.org/jira/browse/TS-902
Project: Traffic Server
Issue Type: Bug
Components: Configuration, HTTP
Affects Versions: 3.1.0, 3.0.1
Environment: TS 3.0.1
Reporter: Zhao Yongming
Labels: crash
Fix For: 3.1.3
when I put a strage ip range, ie: src_ip=128.0.0.0-121.14.89.0 in remap ip
filtering, it will cause the server crash:
{code}
[TrafficServer] using root directory '/usr'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '13'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE: [Alarms::signalAlarm]
Server Process born
[Aug 4 11:04:54.222] {46990117603664} STATUS: opened
/var/log/trafficserver/diags.log
[Aug 4 11:04:54.224] {46990117603664} NOTE: updated diags config
[Aug 4 11:04:54.225] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.239] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.343] Server {46990117603664} NOTE: logging initialized[7],
logging_mode = 1
[Aug 4 11:04:54.345] Server {46990117603664} NOTE: PrefetchProcessor:
Started the prefetch processor
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: Could not add rule at
line #1; Aborting!
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: [ReverseProxy] Unable
to parse IP value in src_ip=128.0.0.0-121.14.89.0 at line 1
FATAL: [ReverseProxy] Unable to parse IP value in
src_ip=128.0.0.0-121.14.89.0 at line 1
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x3ab46127dd]
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ab4612938]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x585)[0x580335]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x2fa)[0x58219a]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0xec)[0x4de75c]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x51ee7b]
/usr/bin/traffic_server(main+0xc07)[0x4bf177]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x389961d994]
/usr/bin/traffic_server(__gxx_personality_v0+0x491)[0x4793a9]
[Aug 4 11:04:54.506] Manager {140564987967264} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
{code}
and here is the rules defined in my remap.config:
{code}
.defflt tools @action=deny @src_ip=0.0.0.0-127.0.0.0
@src_ip=128.0.0.0-121.14.89.0 @src_ip=121.14.90.254-255.255.255.255
@method=PURGE
.useflt tools
{code}
well, it is invalid, but we should not crash, right?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-902) Crash report: invalid ip range in remap.config crash server
[
https://issues.apache.org/jira/browse/TS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-902:
-
Fix Version/s: (was: 3.1.1)
3.1.2
Moving all unassigned bugs out to 3.1.2
Crash report: invalid ip range in remap.config crash server
---
Key: TS-902
URL: https://issues.apache.org/jira/browse/TS-902
Project: Traffic Server
Issue Type: Bug
Components: Configuration, HTTP
Affects Versions: 3.1.0, 3.0.1
Environment: TS 3.0.1
Reporter: Zhao Yongming
Labels: crash
Fix For: 3.1.2
when I put a strage ip range, ie: src_ip=128.0.0.0-121.14.89.0 in remap ip
filtering, it will cause the server crash:
{code}
[TrafficServer] using root directory '/usr'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '13'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE: [Alarms::signalAlarm]
Server Process born
[Aug 4 11:04:54.222] {46990117603664} STATUS: opened
/var/log/trafficserver/diags.log
[Aug 4 11:04:54.224] {46990117603664} NOTE: updated diags config
[Aug 4 11:04:54.225] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.239] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.343] Server {46990117603664} NOTE: logging initialized[7],
logging_mode = 1
[Aug 4 11:04:54.345] Server {46990117603664} NOTE: PrefetchProcessor:
Started the prefetch processor
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: Could not add rule at
line #1; Aborting!
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: [ReverseProxy] Unable
to parse IP value in src_ip=128.0.0.0-121.14.89.0 at line 1
FATAL: [ReverseProxy] Unable to parse IP value in
src_ip=128.0.0.0-121.14.89.0 at line 1
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x3ab46127dd]
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ab4612938]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x585)[0x580335]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x2fa)[0x58219a]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0xec)[0x4de75c]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x51ee7b]
/usr/bin/traffic_server(main+0xc07)[0x4bf177]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x389961d994]
/usr/bin/traffic_server(__gxx_personality_v0+0x491)[0x4793a9]
[Aug 4 11:04:54.506] Manager {140564987967264} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
{code}
and here is the rules defined in my remap.config:
{code}
.defflt tools @action=deny @src_ip=0.0.0.0-127.0.0.0
@src_ip=128.0.0.0-121.14.89.0 @src_ip=121.14.90.254-255.255.255.255
@method=PURGE
.useflt tools
{code}
well, it is invalid, but we should not crash, right?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-902) Crash report: invalid ip range in remap.config crash server
[
https://issues.apache.org/jira/browse/TS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-902:
-
Fix Version/s: 3.1.1
Crash report: invalid ip range in remap.config crash server
---
Key: TS-902
URL: https://issues.apache.org/jira/browse/TS-902
Project: Traffic Server
Issue Type: Bug
Components: Configuration, HTTP
Affects Versions: 3.1.0, 3.0.1
Environment: TS 3.0.1
Reporter: Zhao Yongming
Labels: crash
Fix For: 3.1.1
when I put a strage ip range, ie: src_ip=128.0.0.0-121.14.89.0 in remap ip
filtering, it will cause the server crash:
{code}
[TrafficServer] using root directory '/usr'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE:
[LocalManager::pollMgmtProcessServer] New process connecting fd '13'
[Aug 4 11:04:53.209] Manager {140564987967264} NOTE: [Alarms::signalAlarm]
Server Process born
[Aug 4 11:04:54.222] {46990117603664} STATUS: opened
/var/log/trafficserver/diags.log
[Aug 4 11:04:54.224] {46990117603664} NOTE: updated diags config
[Aug 4 11:04:54.225] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.239] Server {46990117603664} NOTE: cache clustering disabled
[Aug 4 11:04:54.343] Server {46990117603664} NOTE: logging initialized[7],
logging_mode = 1
[Aug 4 11:04:54.345] Server {46990117603664} NOTE: PrefetchProcessor:
Started the prefetch processor
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: Could not add rule at
line #1; Aborting!
[Aug 4 11:04:54.346] Server {46990117603664} WARNING: [ReverseProxy] Unable
to parse IP value in src_ip=128.0.0.0-121.14.89.0 at line 1
FATAL: [ReverseProxy] Unable to parse IP value in
src_ip=128.0.0.0-121.14.89.0 at line 1
/usr/bin/traffic_server - STACK TRACE:
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0x9d)[0x3ab46127dd]
/usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0x88)[0x3ab4612938]
/usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x585)[0x580335]
/usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x2fa)[0x58219a]
/usr/bin/traffic_server(_Z18init_reverse_proxyv+0xec)[0x4de75c]
/usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x51ee7b]
/usr/bin/traffic_server(main+0xc07)[0x4bf177]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x389961d994]
/usr/bin/traffic_server(__gxx_personality_v0+0x491)[0x4793a9]
[Aug 4 11:04:54.506] Manager {140564987967264} ERROR:
[LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
Aborted
{code}
and here is the rules defined in my remap.config:
{code}
.defflt tools @action=deny @src_ip=0.0.0.0-127.0.0.0
@src_ip=128.0.0.0-121.14.89.0 @src_ip=121.14.90.254-255.255.255.255
@method=PURGE
.useflt tools
{code}
well, it is invalid, but we should not crash, right?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
