[jira] [Commented] (TS-1100) Coredump at startup when there's a duplicate remap rule
[ https://issues.apache.org/jira/browse/TS-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197789#comment-13197789 ] Nick Kew commented on TS-1100: -- To exit at startup on such an error - fine (though a clear error message would be helpful - starting up through the trafficserver script leaves only cryptic failure). But a coredump? What kind of by design is that? Coredump at startup when there's a duplicate remap rule --- Key: TS-1100 URL: https://issues.apache.org/jira/browse/TS-1100 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.1 Environment: Bog standard linux/x86; own build. Reporter: Nick Kew Priority: Minor A minor accident with cutpaste in vi leads to TS coredumping at startup. I had duplicated a line in remap.config: map http://myhost:8080/ http://target/ () map http://myhost:8080/ http://target/ The second instance is line 125 in remap.config, and the dump shows: FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 125 bin/traffic_server - STACK TRACE: /usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal_va+0xc7)[0xe21873] /usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal+0x2b)[0xe218c5] bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x1e48)[0x81e1120] bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x562)[0x810] bin/traffic_server(_Z18init_reverse_proxyv+0x41)[0x815500b] bin/traffic_server(_Z20init_HttpProxyServerv+0xe)[0x818fccc] bin/traffic_server(main+0xf7f)[0x813b65d] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x692bd6] bin/traffic_server[0x80f6001] Aborted -- 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] [Commented] (TS-1100) Coredump at startup when there's a duplicate remap rule
[ https://issues.apache.org/jira/browse/TS-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197935#comment-13197935 ] Conan Wang commented on TS-1100: I think TS-948 has fixed this? https://issues.apache.org/jira/browse/TS-948 Coredump at startup when there's a duplicate remap rule --- Key: TS-1100 URL: https://issues.apache.org/jira/browse/TS-1100 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.1 Environment: Bog standard linux/x86; own build. Reporter: Nick Kew Priority: Minor A minor accident with cutpaste in vi leads to TS coredumping at startup. I had duplicated a line in remap.config: map http://myhost:8080/ http://target/ () map http://myhost:8080/ http://target/ The second instance is line 125 in remap.config, and the dump shows: FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 125 bin/traffic_server - STACK TRACE: /usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal_va+0xc7)[0xe21873] /usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal+0x2b)[0xe218c5] bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x1e48)[0x81e1120] bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x562)[0x810] bin/traffic_server(_Z18init_reverse_proxyv+0x41)[0x815500b] bin/traffic_server(_Z20init_HttpProxyServerv+0xe)[0x818fccc] bin/traffic_server(main+0xf7f)[0x813b65d] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x692bd6] bin/traffic_server[0x80f6001] Aborted -- 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] [Commented] (TS-1100) Coredump at startup when there's a duplicate remap rule
[ https://issues.apache.org/jira/browse/TS-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13197416#comment-13197416 ] Leif Hedstrom commented on TS-1100: --- This is sort of by design, it refuses to start up with a bad remap.config. The reason you get a segfault is because our destructors are running on uninitialized objects :-/. Coredump at startup when there's a duplicate remap rule --- Key: TS-1100 URL: https://issues.apache.org/jira/browse/TS-1100 Project: Traffic Server Issue Type: Bug Components: Core Affects Versions: 3.1.1 Environment: Bog standard linux/x86; own build. Reporter: Nick Kew Priority: Minor A minor accident with cutpaste in vi leads to TS coredumping at startup. I had duplicated a line in remap.config: map http://myhost:8080/ http://target/ () map http://myhost:8080/ http://target/ The second instance is line 125 in remap.config, and the dump shows: FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 125 bin/traffic_server - STACK TRACE: /usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal_va+0xc7)[0xe21873] /usr/local/trafficserver/lib/libtsutil.so.3(ink_fatal+0x2b)[0xe218c5] bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x1e48)[0x81e1120] bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x562)[0x810] bin/traffic_server(_Z18init_reverse_proxyv+0x41)[0x815500b] bin/traffic_server(_Z20init_HttpProxyServerv+0xe)[0x818fccc] bin/traffic_server(main+0xf7f)[0x813b65d] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x692bd6] bin/traffic_server[0x80f6001] Aborted -- 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
