[Serusers] problem for using the latest pa module

Kevin Chu kevin.chu at viditec.com
Wed Jan 21 18:34:21 CET 2004


Hi Jamey,

I am interested for testing the new extensions of the pa module from the
latest
unstable release. However, I got problem for configuring pa module.

This is the stacktrace I got from the coredump when I was trying to load
the pa module:

>> (gdb) bt
>> #0  0x4207a453 in strlen () from /lib/tls/libc.so.6
>> #1  0x4009725d in pa_mod_init () at pa_mod.c:148
>> #2  0x08070387 in init_mod (m=0x80d4328) at sr_module.c:453
>> #3  0x08070411 in init_modules () at sr_module.c:476
>> #4  0x0805a629 in main (argc=1, argv=0xbfffd9e4) at main.c:1425
>> #5  0x42015574 in __libc_start_main () from /lib/tls/libc.so.6
>> (gdb)

I think it was coming from this line of code in pa_mod.c:
>> db_url.len = strlen(db_url.s);

Since I didn't set the parameter 'db_url' for pa module in ser.cfg, I got
the segmentation fault as shown above. If I set the parameter to some
value, then the fault is gone.

However, I don't know how to create the db for pa, I still can not get it
running
correctly.

It will be appreciated if you can provide me some instructions or examples
for
creating the db as well as setting the new parameters (presentity_table,
watcherinfo_table) and using the new commands.

Best Regards,
Kevin





More information about the sr-users mailing list