15 May
2007
15 May
'07
2 p.m.
Thanks Martin,
it looks like the crash occurs in a function registered as callback to
TM for the TMCB_RESPONSE_IN event.
there are couple of modules doing this - acc, osp, siptrace, uac, but I
cannot figure out which one. Can you get more info from the debugger ?
gdb provides more info - like the corresponding files for the called
functions...
also which modules (from above) are you using?
regards,
bogdan
Martin Klisch wrote:
Hi Bogdan-Andrei,
here is the backtrace:
root@sip-b:/var/core # pstack core_sip-b_openser_40002_40002_1178955651_10547
core 'core_sip-b_openser_40002_40002_1178955651_10547' of 10547:
/opt/SER/SER0/bin/openser -P /var/run/SER0.pid -f /opt/SER/SER0/etc/SE
ff2c0888 memcpy (fc9fab20, 2, 0, feb868c0, 2, 4a8) + 3c8
ff02bb5c run_trans_callbacks (2, fc9eb7e8, 12c9cc, dfcd8, fc9a4ea8, 1) + bc
ff02ee24 t_reply_matching (140ac8, 3, e788c, 3, 0, 1) + 12e4
ff02f548 t_check (140ac8, ffbffa7c, 22c2e0, 3, 0, 2) + 268
ff0388b4 reply_received (140ac8, 3, ff05df54, 0, ff0388a0, ec400) + 14
00024dcc forward_reply (140ac8, 3, e0400, 0, fc804ae8, a1f7) + 10c
00043b70 receive_msg (12d800, a1f6, 1, 0, 0, 13c4) + 6d0
0006f12c udp_rcv_loop (fc890, fc800, e7800, fc800, 10c890, dfc00) + a4c
00033854 main_loop (fc8040e8, 2500000, 0, e7800, 38, dfc00) + 5f4
00035bdc main (3, e7800, ffbffde4, 3, ffffffff, e7800) + 1cbc
000174fc _start (0, 0, 0, 0, 0, 0) + 5c
Hi Martin,
once you spot the error against, please follow the wiki indications and
get the dump for pkg memory.
changing from db_mode 3 to 1 should not affect the consumption of
private memory (the location cache is kept in shared memory).
If you still have the core file, please post the backtrace.
Thanks and regards,
Bogdan
Martin Klisch wrote:
Hi,
i can not reproduce the errors. it only appears per random. in the last
5
days it appeared two times. five days ago i moves the daemon to another
sun fire with less ram and switched from db_mode 3 to 1 - could this be
the reason? i moved it back to the other machine now.
on saturday it coredumped after the memory errors. would the coredump
file
help?
bye, martin
Martin,
the errors refer to a potential problem related to private memory (not
shared one), so you need to send the signal (as explained on the wiki)
to the process printing such errors ( like 20106). Get and post the mem
dump for pkg memory.
regards,
bogdan
Klaus Darilion wrote:
> http://openser.org/dokuwiki/doku.php/troubleshooting:memory
>
> Martin Klisch wrote:
>
>
>> Hi,
>>
>> i have some memory errors after running OpenSER one day:
>> May 15 02:46:56 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 381148
>> local0.error] ERROR: build_req_buf_from_sip_req: out of memory
>> May 15 02:46:56 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 933771
>> local0.error] ERROR:tm:print_uac_request: no pkg_mem
>> May 15 02:46:56 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 826633
>> local0.error] ERROR:tm:t_forward_nonack: failure to add branches
>> May 15 02:47:00 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 381148
>> local0.error] ERROR: build_req_buf_from_sip_req: out of memory
>> May 15 02:47:00 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 933771
>> local0.error] ERROR:tm:print_uac_request: no pkg_mem
>> May 15 02:47:00 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 826633
>> local0.error] ERROR:tm:t_forward_nonack: failure to add branches
>> May 15 02:47:03 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 381148
>> local0.error] ERROR: build_req_buf_from_sip_req: out of memory
>> May 15 02:47:03 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 933771
>> local0.error] ERROR:tm:print_uac_request: no pkg_mem
>>
>> Version: OpenSER 1.2.0
>> OS: Solaris 10
>> Arch: Sparc
>>
>> Is there a memory leak an any module? or is my memory too low?
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>>
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>>
> _______________________________________________
> Users mailing list
> Users(a)openser.org
> http://openser.org/cgi-bin/mailman/listinfo/users
>
>
>