[
https://issues.apache.org/jira/browse/TS-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333838#comment-14333838
]
James Peach commented on TS-3393:
---------------------------------
This happens because specifies the {{RECC_STR}} checker but fails to provide a
checking regex. {{traffic_server}} crashes when it tries to check the
non-existent regex.
{code}
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f3b27fff700 (LWP 19519)]
0x00007f3b30aa2008 in pcre_compile2 () from /lib/x86_64-linux-gnu/libpcre.so.3
(gdb) where
#0 0x00007f3b30aa2008 in pcre_compile2 () from
/lib/x86_64-linux-gnu/libpcre.so.3
#1 0x00000000004712ef in recordRegexCheck (pattern=0x0, value=0x7f3b14004d60
"james")
at /opt/src/trafficserver.git/mgmt/WebMgmtUtils.cc:1176
#2 0x0000000000471243 in recordValidityCheck (varName=0x7f3b14004bf0
"proxy.config.hostdb.ip_resolve",
value=0x7f3b14004d60 "james") at
/opt/src/trafficserver.git/mgmt/WebMgmtUtils.cc:1142
#3 0x0000000000446ebf in MgmtRecordSet (rec_name=0x7f3b14004bf0
"proxy.config.hostdb.ip_resolve",
val=0x7f3b14004d60 "james", action_need=0x7f3b27ffed0c) at
/opt/src/trafficserver.git/mgmt/api/CoreAPI.cc:615
#4 0x000000000044a01a in handle_record_set (fd=16, req=0x7f3b14004d20,
reqlen=49)
at /opt/src/trafficserver.git/mgmt/api/TSControlMain.cc:448
#5 0x000000000044af3c in handle_control_message (fd=16, req=0x7f3b14004d20,
reqlen=49)
at /opt/src/trafficserver.git/mgmt/api/TSControlMain.cc:1038
#6 0x000000000044995b in ts_ctrl_main (arg=0x7f3b2d0a4d34)
at /opt/src/trafficserver.git/mgmt/api/TSControlMain.cc:212
#7 0x00007f3b30881182 in start_thread (arg=0x7f3b27fff700) at
pthread_create.c:312
#8 0x00007f3b2ff43fbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb) up
#1 0x00000000004712ef in recordRegexCheck (pattern=0x0, value=0x7f3b14004d60
"james")
at /opt/src/trafficserver.git/mgmt/WebMgmtUtils.cc:1176
1176 regex = pcre_compile(pattern, 0, &error, &erroffset, NULL);
(gdb) up
#2 0x0000000000471243 in recordValidityCheck (varName=0x7f3b14004bf0
"proxy.config.hostdb.ip_resolve",
value=0x7f3b14004d60 "james") at
/opt/src/trafficserver.git/mgmt/WebMgmtUtils.cc:1142
1142 if (recordRegexCheck(pattern, value)) {
(gdb) quit
{code}
{{traffic_line}} has a hack to emit the misleading message on any failure to
set a record.
> traffic_line gives cryptic error message when trying to set records which
> cannot be changed dynamically
> -------------------------------------------------------------------------------------------------------
>
> Key: TS-3393
> URL: https://issues.apache.org/jira/browse/TS-3393
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Reporter: Igor Galić
> Assignee: James Peach
> Fix For: 5.3.0
>
>
> for example, trying to set {{proxy.config.hostdb.ip_resolve}}, which for
> whatever reason cannot be changed dynamically, gives the following error:
> {code}
> traffic_line -s proxy.config.hostdb.ip_resolve -v 'ipv6;none'
> traffic_line: Please correct your variable name and|or value
> {code}
> perhaps we should consider this in the upcoming {{traffic_ctl}} effort
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
