[OpenSIPS-Users] Help with sip trace errors please

ha do haloha201 at yahoo.com
Tue Dec 15 05:31:02 CET 2009


Hi Bogdan

i use the Checked out revision 6439.
it is still issue when the sip_trace has content

do you have a plan to make enhancement of sip_trace that logs all message without stop/start opensips 
how to admin opensips without log :((

Thank you
Ha`

--- On Mon, 12/14/09, Bogdan-Andrei Iancu <bogdan at voice-system.ro> wrote:

From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
To: "OpenSIPS users mailling list" <users at lists.opensips.org>
Date: Monday, December 14, 2009, 5:38 AM

Hi Ha,

found the bug - there was an issue when loading the sip_trace file with 
content (some columns being NULL).

I fixed the problem on SVN, so if you do an update and re-compile, you 
should not need to delete the file during restarts.

Thanks and regards,
Bogdan

ha do wrote:
> HI Bogdan
>
> it is clear now :)
>
> f the file has content (aside the first line), the siptrace module 
> does not start ?
> no, the sip_trace module starts fine, i only need to replace new 
> sip_trace file then the error is gone :)
>
> is there a module with the same function as sip_trace but no need to 
> shutdown opensips
>
>
> Thank you
> Ha`
>
> --- On *Fri, 12/11/09, Bogdan-Andrei Iancu /<bogdan at voice-system.ro>/* 
> wrote:
>
>
>     From: Bogdan-Andrei Iancu <bogdan at voice-system.ro>
>     Subject: Re: [OpenSIPS-Users] Help with sip trace errors please
>     To: "OpenSIPS users mailling list" <users at lists.opensips.org>
>     Date: Friday, December 11, 2009, 11:18 AM
>
>     Hi Ha,
>
>     Note that the DB content is updated only at shutdown.
>
>     So, to synthesize - if the file has content (aside the first
>     line), the
>     siptrace module does not start ?
>
>     Regards,
>     Bogdan
>
>     ha do wrote:
>     > HI Brian
>     >
>     > [root at localhost opensipsdb]# ls -ld /tmp/opensipsdb/
>     > drwxr-xr-x 2 root root 4096 Dec 11 14:56 /tmp/opensipsdb/
>     > [root at localhost opensipsdb]# ls -ld /tmp/opensipsdb/sip_trace
>     > -rw-r--r-- 1 root root 168 Dec 11 14:56 /tmp/opensipsdb/sip_trace
>     > [root at localhost opensipsdb]# ps axu | grep opensips
>     > root      2014  0.0  1.1  38072  2928 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2016  0.0  0.3  38072   824 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2017  0.0  0.3  38072   796 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2018  0.0  0.3  38072   796 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2019  0.0  0.3  38072   796 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2020  0.0  0.6  38072  1712 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2021  0.0  0.6  38072  1696 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2022  0.0  0.6  38072  1724 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2023  0.0  0.6  38072  1588 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2024  0.0  0.2  38072   632 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2025  0.0  0.3  38072   948 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2026  0.0  0.3  38076   824 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2027  0.0  0.3  38072   892 ?        R    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2028  0.0  0.3  38072   892 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2029  0.0  0.3  38072   892 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2030  0.0  0.3  38072   892 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2031  0.0  0.3  38072   880 ?        S    14:56   0:00
>     > /usr/local/sbin/opensips
>     > root      2044  0.0  0.2   3904   672 pts/0    R+   15:00   0:00
>     grep
>     > opensips
>     >
>     > let me describe my steps:
>     > step1 : create file sip_trace then insert with 1 line :
>     > id(int,auto) time_stamp(int) callid(string) traced_user(string)
>     > msg(string) method(string) status(string) fromip(string)
>     toip(string)
>     > fromtag(string) direction(string)
>     >
>     > step 2 : start opensips with sip_trace enable :
>     /etc/init.d/opensips
>     > start
>     >
>     > step 3 : use xlite softphone(2000)  + eyebeam(8000) register and
>     > register successfull
>     >
>     > step 4 : make call from 2000 to 8000 then connected fine then hangup
>     >
>     > step5 : check the /tmp/opensipsdb/sip_trace : cat
>     > /tmp/opensipsdb/sip_trace and result
>     > [root at localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace
>     > id(int,auto) time_stamp(int) callid(string) traced_user(string)
>     > msg(string) method(string) status(string) fromip(string)
>     toip(string)
>     > fromtag(string) direction(string)
>     >
>     > step 6: wait about 3 mins
>     >
>     > step 7: check the sip_trace file :
>     > [root at localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace
>     > id(int,auto) time_stamp(int) callid(string) traced_user(string)
>     > msg(string) method(string) status(string) fromip(string)
>     toip(string)
>     > fromtag(string) direction(string)
>     >
>     >
>     > step 8 : stop opensips : /etc/init.d/opensips stop
>     >
>     > step 9: check the sip_trace file : at this time all logs are now in
>     > the /tmp/opensipsdb/sip_trace
>     > [root at localhost opensipsdb]# cat /tmp/opensipsdb/sip_trace
>     > id(int,auto) time_stamp(int) callid(string) traced_user(string)
>     > msg(string) method(string) status(string) fromip(string)
>     toip(string)
>     > fromtag(string) direction(string)
>     > 39:1260518390:MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.::SIP/2.0
>     > 200 OK\r\nVia\: SIP/2.0/UDP
>     >
>     192.168.237.1\:5592;received=192.168.237.1;branch=z9hG4bK-d8754z-5d41606f451fca7c-1---d8754z-;rport=5592\r\nContact\:
>
>     > <sip\:8000 at 192.168.237.1\:19032>\r\nTo\:
>     > <sip\:8000 at 192.168.237.131>;tag=5378ee52\r\nFrom\:
>     > "2000"<sip\:2000 at 192.168.237.131>;tag=aa323d0e\r\nCall-ID\:
>     > MGRjYzNhYzQ0YTc2YTU0MWQyYzI4MTEyY2Q5NjcwYjI.\r\nCSeq\: 2
>     > BYE\r\nUser-Agent\: eyeBeam release 1004p stamp
>     > 31962\r\nContent-Length\:
>     >
>     0\r\n\r\n:BYE:200:udp\:192.168.237.131\:5060:udp\:192.168.237.1\:5592:aa323d0e:out
>     >
>     > step 10 : start opensips again : /etc/initd/opensips start - start
>     > successfull without problem
>     >
>     > step 11 : register 2000 + 8000 again
>     >
>     > step 12: get error from debug :
>     > Dec 11 15:03:49 localhost /usr/local/sbin/opensips[2120]:
>     > ERROR:db_text:dbt_insert: table does not exist!
>     > Dec 11 15:03:49 localhost /usr/local/sbin/opensips[2120]:
>     > ERROR:siptrace:sip_trace: error storing trace
>     >
>     >
>     > what happen in your lab, Brian
>     > does the log of sip_trace write down to
>     /tmp/opensipsdb/sip_trace file
>     > right away or you need to wait some times
>     >
>     >
>     > Thank you
>     > Ha
>     >
>     >     Are you saying that when no /tmp/opensipsdb/sip_trace
>     exists, and
>     >     you start opensips fresh, then no error appears in the log
>     and the
>     >     sip_trace file is created normally?
>     >
>     >     And are you saying that when a /tmp/opensipsdb/sip_trace exists,
>     >     and you start opensips fresh, then a error appears in the
>     log and
>     >     the sip_trace file is not written to with new transactions?
>     Please
>     >     show the errors in the log file if this is the case.
>     >
>     >     Also, please tell us the results of:
>     >
>     >       [root at localhost ~]# ls -ld /tmp/opensipsdb
>     >       [root at localhost ~]# ls -ld /tmp/opensipsdb/sip_trace
>     >       [root at localhost ~]# ps aux | grep opensips
>     >
>     >     ...in order to determine if you have a permissions problem
>     easily
>     >     solved in the opensips.cfg.
>     >
>     >     Regards,
>     >     Brian
>     >
>     >     _______________________________________________
>     >     Users mailing list
>     >     Users at lists.opensips.org
>     </mc/compose?to=Users at lists.opensips.org>
>     </mc/compose?to=Users at lists.opensips.org
>     </mc/compose?to=Users at lists.opensips.org>>
>     >     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Users mailing list
>     > Users at lists.opensips.org </mc/compose?to=Users at lists.opensips.org>
>     > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     >   
>
>
>     -- 
>     Bogdan-Andrei Iancu
>     www.voice-system.ro
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org </mc/compose?to=Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   


-- 
Bogdan-Andrei Iancu
www.voice-system.ro


_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20091214/02208307/attachment-0001.htm 


More information about the Users mailing list