[OpenSIPS-Users] Invalid parameter errors

[Liviu Chircu]

Hi Ben,

We are actually dealing with two bugs here, which may or may not be 
related to one another.

Bug #1: bad? variable during a route() call
-------------------------------------------------------

For this one, can you enumerate all "route()" calls in your script which 
pass at least one variable, along with their full parameter call 
syntax?  Example call:

route(sequential_requests, $rm, $avp(myinfo));

Bug #2: bad "key variable" during a $json expansion
----------------------------------------------------------------------

For this one, can you enumerate all $json() variable appearances which 
include at least one parameterized key access?  I realize there may be 
lots of these, but you may group them into "categories" and print out a 
few ones that might be relevant (i.e. their index may contain an 
INT-only variable, which is >wrong<).  Example appearances:

$json(http_body/$var(tag))
$json(http_body/users[0]/$avp(username))

Best regards,

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 24.01.2019 01:37, Ben Newlin wrote:
>
> Liviu,
>
> Thank you for the quick response. I do see 2 such errors shortly after 
> startup:
>
> ERROR:core:pv_get_param: cannot get spec value
>
> ERROR:core:pv_get_param: cannot get spec value
>
> However, after that it just continues on with more of the same errors 
> that keep scrolling. There is a variation of the scrolling errors that 
> was I didn’t included before, in case it helps:
>
> ERROR:core:comp_scriptvar: cannot get left var value
>
> WARNING:core:do_action: errorin expression at opensips.cfg:583
>
> ERROR:json:expand_tag_list: Non string value in key
>
> ERROR:json:pv_set_json: Cannot expand variables in path
>
> ERROR:core:do_assign: setting PV failed
>
> ERROR:core:do_assign: errorat opensips.cfg:346
>
> ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
>
> There aren’t any other non-repeating errors. I have picked up your 
> commit and will try to gather more information from it, but this issue 
> is primarily happening in our production environment so it may take a bit.
>
> Also, I haven’t completely verified this yet, but it seems that 
> enabling TLS has made the errors stop somehow. Continuing to 
> investigate that.
>
> Ben Newlin
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of Liviu 
> Chircu <liviu at opensips.org>
> *Reply-To: *OpenSIPS users mailling list <users at lists.opensips.org>
> *Date: *Tuesday, January 22, 2019 at 6:08 PM
> *To: *"users at lists.opensips.org" <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] Invalid parameter errors
>
> Hi, Ben!
>
> The strange "...type 1836017711" errors seem to be caused by a poorly 
> handed error condition (a secondary bug), which is now fixed [1]. If 
> this theory holds, you must have a "cannot get spec value" error (or 
> slew of errors) in the earlier section of your OpenSIPS log (possibly 
> right after restart or shortly after starting to process traffic).
>
> Could you please confirm/infirm the above?  If true, are there any 
> other relevant errors thrown around that initial "cannot get spec 
> value" error message?  Those error logs could be key to making 
> progress in understanding the main bug.
>
> Best regards,
>
> [1]: https://github.com/OpenSIPS/opensips/commit/52ff74af8702a
>
> Liviu Chircu
> OpenSIPS Developer
> http://www.opensips-solutions.com
>
> On 22.01.2019 20:58, Ben Newlin wrote:
>
>     Hi,
>
>     Since upgrading to 2.4.4 we are seeing the following logs
>     scrolling nearly continuously on our servers:
>
>
>
>     ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
>
>     ERROR:core:comp_scriptvar: cannot get left var value
>
>     WARNING:core:do_action: errorin expression at opensips.cfg:583
>     ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
>
>     ERROR:core:comp_scriptvar: cannot get left var value
>
>     WARNING:core:do_action: errorin expression at opensips.cfg:583
>     ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
>
>     ERROR:core:comp_scriptvar: cannot get left var value
>
>     ALERT:core:pv_get_param: BUG: invalid parameter type 1836017711
>
>     ERROR:core:comp_scriptvar: cannot get left var value
>
>     WARNING:core:do_action: errorin expression at opensips.cfg:439
>
>     It seems to be related to our use of the json module. We often
>     pass json variable types as parameters to other routes and I
>     believe the errors are caused by that. But it’s hard to say as
>     there are a few different script lines referenced in the errors,
>     but some of them point to return statements and other code
>     sections that don’t really make sense. For example, line 583
>     referenced in the error above is:
>
>       return(-1);
>
>     Any ideas?
>
>     Ben Newlin
>
>
>
>     _______________________________________________
>
>     Users mailing list
>
>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190124/f991f0d7/attachment-0001.html>