Hey Community,
I'm trying to play around with ndb_redis, but seem to be missing something probably obvious as I'm getting a "failed to find command redis_cmd" error on load.
loadmodule "ndb_redis.so" modparam("ndb_redis", "server", "name=test;addr=127.0.0.1;port=7000")
request_route { redis_cmd("test", "SET foo bar", "r"); }
I've verified that mpath = /usr/local/lib64/kamailio/modules/ and that ndb_redis.so is in that directory.
Any help is greatly appreciated.
Ryan Brindley
Hello,
do you get other errors in syslog before?
Cheers, Daniel On 19/05/14 19:19, Ryan Brindley wrote:
No. It appears to be properly loading the module, aka no "failed to load module" errors and even properly setting the server modparam.
Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108
On Mon, May 19, 2014 at 3:40 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
Are you having some #!ifdef statements? If yes, check if they are paired properly with #!endif. If not, can you give the log messages with debug=3 in kamailio.cfg?
Cheers, Daniel
On 19/05/14 22:50, Ryan Brindley wrote:
No #!ifdef, only one #!define one-liner.
0(3693) DEBUG: <core> [sr_module.c:707]: find_mod_export_record(): find_export_record: <redis_cmd> not found 0(3693) DEBUG: <core> [sr_module.c:707]: find_mod_export_record(): find_export_record: <redis_cmd> not found 0(3693) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find command redis_cmd 0(3693) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 66, column 40: unknown command, missing loadmodule?
Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108
On Mon, May 19, 2014 at 3:52 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
It doesn't look like all log messages from start. have you pasted all of them?
Daniel
On 19/05/14 22:58, Ryan Brindley wrote:
Wow...I found the issue :-/
The example I gave in this thread was not a copy paste and I had redis_cmd("name", "SET foo bar" "r"); (not the lack of the second comma).
Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108
On Mon, May 19, 2014 at 4:00 PM, Daniel-Constantin Mierla <miconda@gmail.com
wrote:
On 05/19/2014 05:02 PM, Ryan Brindley wrote:
Yeah, it's somewhat confusing. However, when you invoke a function according to a prototype that doesn't exist, the fixup functions will return an error in such a way as to produce a "function doesn't exist" message in the logs. It does exist, just not in the two-argument variety. :-)
Yea. I thought the same thing once I figured it out. The error is confusing but then it does make sense once you understand its looking for the 2 argument prototype.
Maybe an additional "wrong parameters?" at the end of the error message could help prevent misdirection debugging.
Thanks Daniel for helping!
Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108
On Mon, May 19, 2014 at 4:51 PM, Alex Balashov abalashov@evaristesys.comwrote:
I enhanced the log message to print the number of parameters for the functions that is searched -- hope that helps in the future.
Cheers, Daniel
On 20/05/14 04:08, Ryan Brindley wrote: