[Serusers] Q registering ua using IP or fqdn? - sr-users

Andrey Kouprianov

27 Jun 27 Jun

4:02 p.m.

Do you also use IP for Domain/Realm? If so, then you'll have to change the www_authenticate and www_challenge realm too. On 6/27/06, Mindaugas Kuprys <mindaugask(a)erdves.lt> wrote:

...

Hi, Intresting thing, I'm able to register UA then I'm using SER FQDN but not then using IP address in UA config? This should be so? Mindaugas _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply

nick

28 Jun 28 Jun

8:54 a.m.

New subject: [Serusers] still battling ser

nick wrote:

...

A followup to my problem, I rebuilt the entire system, and have compiled 0.9.6 from scratch. The system works just fine, with a whole bunch of modules, but as soon as I add in the acc.so module *boom* I remember reading that the acc module has now been divided into different parts, do I need to compile the acc module seperately (I plan on using acc_db) ??? thanks for any ideas you can point me towards.. BTW, I may rebuild the binaries again, to see if I can get debugging to work, but I haven't been able to extract anything useful from gdb as of yet... _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Can anyone tell me how to get ser to stop forking??????? I have fork=no in my ser.cfg but when I load /usr/local/sbin/ser into gdb, then use the command run: [root@sipserver ~]# gdb /usr/local/sbin/ser GNU gdb Red Hat Linux (6.3.0.0-1.96rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/tls/libthread_db.so.1". (gdb) run Starting program: /usr/local/sbin/ser 192.168.1.93 [192.168.1.93]:5060 192.168.1.93 [192.168.1.93]:5060 Listening on udp: 192.168.1.93 [192.168.1.93]:5060 tcp: 192.168.1.93 [192.168.1.93]:5060 Aliases: tcp: pc-00093:5060 udp: pc-00093:5060 Detaching after fork from child process 3304. Program exited normally. ---------------------------- of course, the core dump is called core.3305 3305 being the PID of the process forked, even though I don't want it to fork. How can I run a stack trace on something that won't even obey it's own config file????

Reply

Weiter Leiter

9:14 a.m.

New subject: [Serusers] still battling ser

Hi, Nearly enough. In gdb promt, after the sigsegv received, run 'backtrace'. And post the whole output. Also, attach the output of 'ser -V'. WL. nick wrote:

...

nick wrote:

A followup to my problem, I rebuilt the entire system, and have compiled 0.9.6 from scratch. The system works just fine, with a whole bunch of modules, but as soon as I add in the acc.so module *boom* I remember reading that the acc module has now been divided into different parts, do I need to compile the acc module seperately (I plan on using acc_db) ??? thanks for any ideas you can point me towards.. BTW, I may rebuild the binaries again, to see if I can get debugging to work, but I haven't been able to extract anything useful from gdb as of yet... _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Can anyone tell me how to get ser to stop forking??????? I have fork=no in my ser.cfg but when I load /usr/local/sbin/ser into gdb, then use the command run: [root@sipserver ~]# gdb /usr/local/sbin/ser GNU gdb Red Hat Linux (6.3.0.0-1.96rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/tls/libthread_db.so.1". (gdb) run Starting program: /usr/local/sbin/ser 192.168.1.93 [192.168.1.93]:5060 192.168.1.93 [192.168.1.93]:5060 Listening on udp: 192.168.1.93 [192.168.1.93]:5060 tcp: 192.168.1.93 [192.168.1.93]:5060 Aliases: tcp: pc-00093:5060 udp: pc-00093:5060 Detaching after fork from child process 3304. Program exited normally. ---------------------------- of course, the core dump is called core.3305 3305 being the PID of the process forked, even though I don't want it to fork. How can I run a stack trace on something that won't even obey it's own config file???? _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

I ran it without forking via the command line option -D, it decided to listen to me finally: and gave me this: Starting program: /usr/local/sbin/ser -D -dddddddd 192.168.1.93 [192.168.1.93]:5060 192.168.1.93 [192.168.1.93]:5060 Listening on udp: 192.168.1.93 [192.168.1.93]:5060 tcp: 192.168.1.93 [192.168.1.93]:5060 Aliases: tcp: pc-00093:5060 udp: pc-00093:5060 WARNING: no fork mode acc - initializing Program received signal SIGSEGV, Segmentation fault. 0x0000002a9578516f in insert_tmcb (cb_list=0x0, types=1, f=0x2a955675c7 <acc_onreq>, param=0x0) at t_hooks.c:99 99 cbp->next = cb_list->first; Is this something that someone qualified can work with????? _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply

Greger V. Teigre

29 Jun 29 Jun

6:01 a.m.

New subject: [Serusers] still battling ser

Nick, You may want to post this to serdev(a)iptel.org so you know developers see your trace. g-) nick wrote:

...

Weiter Leiter wrote:

Hi, Nearly enough. In gdb promt, after the sigsegv received, run 'backtrace'. And post the whole output. Also, attach the output of 'ser -V'. WL. nick wrote:

nick wrote:

nick wrote: > A followup to my problem, I rebuilt the entire system, and have > compiled 0.9.6 from scratch. The system works just fine, with a > whole bunch of modules, but as soon as I add in the acc.so module > *boom* > > I remember reading that the acc module has now been divided into > different parts, do I need to compile the acc module seperately (I > plan on using acc_db) ??? > > thanks for any ideas you can point me towards.. > > BTW, I may rebuild the binaries again, to see if I can get debugging > to work, but I haven't been able to extract anything useful from gdb > as of yet... > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > Can anyone tell me how to get ser to stop forking??????? I have fork=no in my ser.cfg but when I load /usr/local/sbin/ser into gdb, then use the command run: [root@sipserver ~]# gdb /usr/local/sbin/ser GNU gdb Red Hat Linux (6.3.0.0-1.96rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...Using host libthread_db library "/lib64/tls/libthread_db.so.1". (gdb) run Starting program: /usr/local/sbin/ser 192.168.1.93 [192.168.1.93]:5060 192.168.1.93 [192.168.1.93]:5060 Listening on udp: 192.168.1.93 [192.168.1.93]:5060 tcp: 192.168.1.93 [192.168.1.93]:5060 Aliases: tcp: pc-00093:5060 udp: pc-00093:5060 Detaching after fork from child process 3304. Program exited normally. ---------------------------- of course, the core dump is called core.3305 3305 being the PID of the process forked, even though I don't want it to fork. How can I run a stack trace on something that won't even obey it's own config file???? _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

I ran it without forking via the command line option -D, it decided to listen to me finally: and gave me this: Starting program: /usr/local/sbin/ser -D -dddddddd 192.168.1.93 [192.168.1.93]:5060 192.168.1.93 [192.168.1.93]:5060 Listening on udp: 192.168.1.93 [192.168.1.93]:5060 tcp: 192.168.1.93 [192.168.1.93]:5060 Aliases: tcp: pc-00093:5060 udp: pc-00093:5060 WARNING: no fork mode acc - initializing Program received signal SIGSEGV, Segmentation fault. 0x0000002a9578516f in insert_tmcb (cb_list=0x0, types=1, f=0x2a955675c7 <acc_onreq>, param=0x0) at t_hooks.c:99 99 cbp->next = cb_list->first; Is this something that someone qualified can work with????? _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

(gdb) bt #0 0x0000002a9578516f in insert_tmcb (cb_list=0x0, types=1, f=0x2a955675c7 <acc_onreq>, param=0x0) at t_hooks.c:99 #1 0x0000002a95785494 in register_tmcb (p_msg=0x0, t=0x0, types=1, f=0x2a955675c7 <acc_onreq>, param=0x0) at t_hooks.c:166 #2 0x0000002a955674c7 in mod_init () at acc_mod.c:308 #3 0x0000000000430d79 in init_mod (m=0x5d5228) at sr_module.c:474 #4 0x0000000000430ce8 in init_mod (m=0x5d52e8) at sr_module.c:471 #5 0x0000000000430ce8 in init_mod (m=0x5d53a8) at sr_module.c:471 #6 0x0000000000430ce8 in init_mod (m=0x5d5468) at sr_module.c:471 #7 0x0000000000430ce8 in init_mod (m=0x5d5528) at sr_module.c:471 #8 0x0000000000430ce8 in init_mod (m=0x5d55e8) at sr_module.c:471 #9 0x0000000000430ce8 in init_mod (m=0x5d56a8) at sr_module.c:471 #10 0x0000000000430ce8 in init_mod (m=0x5d5768) at sr_module.c:471 #11 0x0000000000430e05 in init_modules () at sr_module.c:497 #12 0x0000000000416f3c in main (argc=3, argv=0x7fbffffa18) at main.c:1577 Starting program: /usr/local/sbin/ser -V version: ser 0.9.6 (x86_64/linux) flags: STATS: Off, EXTRA_DEBUG, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 @(#) $Id: main.c,v 1.197.2.1 2005/07/25 16:56:24 andrei Exp $ main.c compiled on 09:19:06 Jun 28 2006 with gcc 3.4.5 Program exited normally. I also did a bt full: (gdb) bt full #0 0x0000002a9578516f in insert_tmcb (cb_list=0x0, types=1, f=0x2a955675c7 <acc_onreq>, param=0x0) at t_hooks.c:99 cbp = (struct tm_callback *) 0x2a96010a78 #1 0x0000002a95785494 in register_tmcb (p_msg=0x0, t=0x0, types=1, f=0x2a955675c7 <acc_onreq>, param=0x0) at t_hooks.c:166 cb_list = (struct tmcb_head_list *) 0x0 #2 0x0000002a955674c7 in mod_init () at acc_mod.c:308 load_tm = 0x2a9578d4a0 <load_tm> #3 0x0000000000430d79 in init_mod (m=0x5d5228) at sr_module.c:474 No locals. #4 0x0000000000430ce8 in init_mod (m=0x5d52e8) at sr_module.c:471 No locals. #5 0x0000000000430ce8 in init_mod (m=0x5d53a8) at sr_module.c:471 No locals. #6 0x0000000000430ce8 in init_mod (m=0x5d5468) at sr_module.c:471 No locals. #7 0x0000000000430ce8 in init_mod (m=0x5d5528) at sr_module.c:471 No locals. #8 0x0000000000430ce8 in init_mod (m=0x5d55e8) at sr_module.c:471 No locals. #9 0x0000000000430ce8 in init_mod (m=0x5d56a8) at sr_module.c:471 No locals. #10 0x0000000000430ce8 in init_mod (m=0x5d5768) at sr_module.c:471 No locals. #11 0x0000000000430e05 in init_modules () at sr_module.c:497 No locals. #12 0x0000000000416f3c in main (argc=3, argv=0x7fbffffa18) at main.c:1577 cfg_stream = (FILE *) 0x6cd010 c = -1 r = 4224491 tmp = 0x39d1014c40 "" tmp_len = 0 port = 0 proto = 0 options = 0x46d4e8 "f:cm:b:l:n:N:rRvdDETVhw:t:u:g:P:G:i:x:" ret = -1 seed = 4256706975 rfd = 7 _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Reply