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:
Yea. I thought the same thing once I figured it out. The error is
confusing but then it does make sense once
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 fo
On 05/19/2014 05:02 PM, 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).
Yeah, it's somewhat confusing. However, when you invoke a function
according to
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-C
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:
No #!ifdef, only one #!define one-liner.
0(3693) DEBUG: [sr_module.c:707]: find_mod_export_record():
find_export_record: not found
0(3693) DEBUG: [sr_module.c:70
No #!ifdef, only one #!define one-liner.
0(3693) DEBUG: [sr_module.c:707]: find_mod_export_record():
find_export_record: not found
0(3693) DEBUG: [sr_module.c:707]: find_mod_export_record():
find_export_record: not found
0(3693) ERROR: [cfg.y:3272]: yyparse(): cfg. parser: failed to find
c
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. It appears to be properly loading the module, aka no "failed to
load m
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 wrote:
> Hell
Hello,
do you get other errors in syslog before?
Cheers,
Daniel
On 19/05/14 19:19, Ryan Brindley wrote:
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 "
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_
10 matches
Mail list logo