Asterisk Console Warnings After Upgrade to Distro 10.13.66

#1

We recently upgraded our FreePBX Distro to 10.13.66 from 6.12.65. Just before upgrading the system we switched to asterisk 13. Since then, I have lots of these messages popping up in the console, even when verbosity is off.

[2016-03-24 13:35:47] WARNING[31447][C-0000251e]: func_strings.c:1417 function_eval: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:35:47] WARNING[31447][C-0000251e]: func_strings.c:1430 function_eval2: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:35:47] WARNING[31447][C-0000251e]: func_strings.c:1417 function_eval: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:35:47] WARNING[31447][C-0000251e]: func_strings.c:1430 function_eval2: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:11] WARNING[31497][C-00002521]: func_strings.c:1417 function_eval: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:11] WARNING[31497][C-00002521]: func_strings.c:1430 function_eval2: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:11] WARNING[31497][C-00002521]: func_strings.c:1417 function_eval: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:11] WARNING[31497][C-00002521]: func_strings.c:1430 function_eval2: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:17] WARNING[31504][C-0000251e]: func_strings.c:1417 function_eval: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:17] WARNING[31504][C-0000251e]: func_strings.c:1430 function_eval2: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:17] WARNING[31504][C-0000251e]: func_strings.c:1417 function_eval: EVAL requires an argument: EVAL(<string>)
[2016-03-24 13:36:17] WARNING[31504][C-0000251e]: func_strings.c:1430 function_eval2: EVAL requires an argument: EVAL(<string>)`

We also have a smaller number of these similar messages:

[2016-03-24 13:35:34] WARNING[2492]: func_cdr.c:352 cdr_write_callback: CDR requires a value (CDR(variable)=value)

Can anyone take a shot at what they pertain to? Here are a few of these lines in context:

[2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Goto (sub-record-check,exten,11) [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:11] Gosub("Local/[email protected];2", "recordcheck,1(dontcare,external,402)") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:1] NoOp("Local/[email protected];2", "Starting recording check against dontcare") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:2] Goto("Local/[email protected];2", "dontcare") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Goto (sub-record-check,recordcheck,3) [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:3] Return("Local/[email protected];2", "") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:12] Return("Local/[email protected];2", "") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:6] Macro("Local/[email protected];2", "dial-one,,tr,402") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:1] Set("Local/[email protected];2", "DEXTEN=402") in new stack [2016-03-24 13:46:59] WARNING[735][C-0000255c] func_strings.c: EVAL requires an argument: EVAL(<string>) [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:2] ExecIf("Local/[email protected];2", "0?Set(__ZULU_URL_=)") in new stack [2016-03-24 13:46:59] WARNING[735][C-0000255c] func_strings.c: EVAL requires an argument: EVAL(<string>) [2016-03-24 13:46:59] WARNING[735][C-0000255c] func_strings.c: EVAL requires an argument: EVAL(<string>) [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:3] ExecIf("Local/[email protected];2", "0?Set(__ZULU_TYPE_=)") in new stack [2016-03-24 13:46:59] WARNING[735][C-0000255c] func_strings.c: EVAL requires an argument: EVAL(<string>) [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:4] Set("Local/[email protected];2", "DIALSTATUS_CW=") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:5] GosubIf("Local/[email protected];2", "0?screen,1()") in new stack [2016-03-24 13:46:59] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:6] GosubIf("Local/[email protected];2", "0?cf,1()") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:7] GotoIf("Local/[email protected];2", "1?skip1") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Goto (macro-dial-one,s,10) [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:10] GotoIf("Local/[email protected];2", "0?nodial") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:11] GotoIf("Local/[email protected];2", "0?continue") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:12] Set("Local/[email protected];2", "EXTHASCW=") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:13] GotoIf("Local/[email protected];2", "1?next1:cwinusebusy") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Goto (macro-dial-one,s,14) [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:14] GotoIf("Local/[email protected];2", "0?docfu:skip3") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Goto (macro-dial-one,s,18) [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:18] GotoIf("Local/[email protected];2", "1?next2:continue") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Goto (macro-dial-one,s,19) [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Executing [[email protected]:19] GotoIf("Local/[email protected];2", "1?continue") in new stack [2016-03-24 13:47:00] VERBOSE[735][C-0000255c] pbx.c: Goto (macro-dial-one,s,27)

Many thanks,

Tom

#2

Eval requires an argument is normal. It comes from ZULU but doesn’t hurt the dialplan and is an annoyance from how Asterisk works.

#3

Wow, that is an annoyance! Thanks for the reply.

#4

I plan on fixing it soon. It’s basically doing this

Is this string from the DB empty? If so then EVAL it.

Well the string IS empty and the statement is returning false but even with a false it parses the EVAL. So it needs a proper goto but I have to re-evaluate the dialplan.

#5

We are seeing a LOT of these even with verbose 0.

#6

Yes and this is 100% normal if you are using Zulu.

#7

Thanks Andrew,
It will be nice to get the clutter out of the logs. It really obscures the important stuff.