Re: [OpenSIPS-Users] db_mysql core dump

[Duane Larson]

So the first bug I had appears to be fixed now, but installing the latest
SVN has brought the other issue that Ovidiu mentioned in the last email.

On Fri, Dec 10, 2010 at 4:34 PM, Duane Larson wrote:

> Thanks.  I won't do anything for now since it hasn't core dumped again.
> Will wait to see what the OpenSIPS team thinks.  Hopefully though the first
> issue is fixed though.  Should know over the weekend if OpenSIPS hasn't done
> a core dump with the same error.
>
> Appreciate the help.
>
>   On Fri, Dec 10, 2010 at 4:30 PM, Ovidiu Sas wrote:
>
>> You are using mi to send a publish.  The body of that publish is taken
>> from the mi command directly.
>> I think the body should be copied into the shared memory and not used
>> directly from the mi structure.
>> Or maybe if it's used from the mi structure, the free is not necessary
>> (as it may be done by the underlaying mi implementation).
>> I will let Anca and Bogdan to comment more on this one.
>>
>> An ugly workaraound here would be to remove the free (line 495,496 and
>> 505,506).
>> This may lead to some memory leak, but it may be manageable until a
>> fix will be uploaded (should be pretty straight forward to fix this
>> issue).
>> Or maybe this is the proper fix (if the free is already done by the
>> underlaying mi implementation).
>>
>>
>> Regards,
>> Ovidiu Sas
>>
>> On Fri, Dec 10, 2010 at 4:02 PM, Duane Larson 
>> wrote:
>> > Thanks for working with me on this Ovidiu.  I think this is what you are
>> > wanting (sorry not good with debugging)???
>> >
>> > (gdb) frame 4
>> > #4  0x7f1e935bc0b8 in send_publish_int (presentity=> > out>,
>> > publ=, ev=0x7f1e88d57518, hash_index=332) at
>> > send_publish.c:496
>> > 496 free(body->s);
>> >
>> > print body->s
>> > $1 = 0x83de41 "\n> > xmlns=\"urn:ietf:params:xml:ns:xcap-diff\"
>> > xcap-root=\"http://xcap.aethercommunications.com/xcap-root\
>> ">\n> > new-etag=\"697c57e1c3c03ffe4febcc2c8905f"...
>> >
>> >
>> > On Fri, Dec 10, 2010 at 2:56 PM, Ovidiu Sas 
>> wrote:
>> >>
>> >> This is a crash in the pua module (different than the previous one).
>> >> send_publish.c:496 => free(body->s);
>> >>
>> >> Can you print the value and content of the body?
>> >>
>> >>
>> >> Thanks,
>> >> Ovidiu
>> >>
>> >> On Fri, Dec 10, 2010 at 3:28 PM, Duane Larson 
>> >> wrote:
>> >> > I did a total removal of the older OpenSIPS install and dropped and
>> >> > readded
>> >> > the Presence tables into MySQL.  That really helped thanks.  I still
>> had
>> >> > some core dumps though not sure if it is going to happen more or not
>> >> > (will
>> >> > have to keep my eye on it), but this is what the core dump says
>> >> >
>> >> >
>> >> > (gdb) backtrace
>> >> > #0  0x7f1e97c6e165 in raise () from /lib/libc.so.6
>> >> > #1  0x7f1e97c70f70 in abort () from /lib/libc.so.6
>> >> > #2  0x7f1e97ca427b in ?? () from /lib/libc.so.6
>> >> > #3  0x7f1e97cadad6 in ?? () from /lib/libc.so.6
>> >> > #4  0x7f1e935bc0b8 in send_publish_int (presentity=> optimized
>> >> > out>, publ=, ev=0x7f1e88d57518, hash_index=332)
>> at
>> >> > send_publish.c:496
>> >> > #5  0x7f1e935bcf12 in send_publish (publ=0x7fff97d6adc0) at
>> >> > send_publish.c:572
>> >> > #6  0x7f1e92f968d3 in mi_pua_publish (cmd=0x84ddb0, param=> >> > optimized out>) at mi_func.c:237
>> >> > #7  0x7f1e9540e388 in run_mi_cmd (rx_sock=,
>> >> > tx_sock=) at ../../mi/mi.h:104
>> >> > #8  mi_datagram_server (rx_sock=, tx_sock=> >> > optimized out>) at datagram_fnc.c:529
>> >> > #9  0x7f1e95410463 in datagram_process (rank=0) at
>> mi_datagram.c:311
>> >> > #10 0x00493f0c in start_module_procs () at sr_module.c:574
>> >> > #11 0x0042cefa in main_loop (argc=,
>> >> > argv=> >> > optimized out>) at main.c:872
>> >> > #12 main (argc=, argv=) at
>> >> > main.c:1388
>> >> >
>> >> >
>> >> > libc.so.6 keeps popping up in the core dumps.
>> >> >
>> >> > On Fri, Dec 10, 2010 at 12:15 PM, Ovidiu Sas 
>> >> > wrote:
>> >> >>
>> >> >> Have you also updated the layout of the presentity table?
>> >> >> Check for the extra_hdrs field.
>> >> >>
>> >> >> Regards,
>> >> >> Ovidiu Sas
>> >> >>
>> >> >> On Fri, Dec 10, 2010 at 12:52 PM, Duane Larson <
>> duane.lar...@gmail.com>
>> >> >> wrote:
>> >> >> > I did update the presentity table to be 5 instead of 4.  Perhaps i
>> >> >> > didn't
>> >> >> > clean up the previous install.  Let me try that.
>> >> >> >
>> >> >> > On Dec 10, 2010 11:46 AM, "Ovidiu Sas" 
>> wrote:
>> >> >> >
>> >> >> > Do you see any errors in the logs?
>> >> >> > Make sure that you clean up your previous install (remove all the
>> >> >> > opensips modules and all the opensips binaries) before
>> re-installing
>> >> >> > opensips.
>> >> >> > Also, the presentity table has evolved (it has a new field:
>> >> >> > extra_hdrs).  The presentity version table should be 5.
>> >> >> >
>> >> >> >
>> >> >> > Regards,
>> >> >> > Ovidiu Sas
>> >> >> >
>> >> >> > 

Re: [OpenSIPS-Users] Opensips Logrotate

[Wesley Volcov]

Hey Sergio,

I'm using log/messages to log opensips messages, then I have in my
/etc/logrotate.d/syslog the follow configuracion:

/var/log/messages {
rotate 250
size 50M
missingok
notifempty
postrotate
/bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null
|| true
/bin/kill -HUP `cat /var/run/rsyslogd.pid 2> /dev/null` 2> /dev/null
|| true
endscript
}

It works very well to me! In my server 50M gives me arround 1 hour of log.

I hope it help you.

Cheers!

On 12 December 2010 01:36, sergio  wrote:

> Hello list
>
> Does anyone have any suggestions to rotate the log OpenSIPS. My log file is
> over 7GB
>
> I am setting up logrotate
>
> I'm worried about the reload I've noticed is the OpenSIPS restart.
>
> /etc/logrotate.d/opensips
>
> /var/log/opensips.log {
>missingok
>notifempty
>sharedscripts
>postrotate
>/sbin/service opensips reload > /dev/null 2>/dev/null || true
>endscript
> }
>
> Thanks
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



-- 
Wesley Volcov
Email: wesleyvol...@gmail.com
Messenger: vol...@live.com
Mobile: +55 11 9989-5348
Website: http://volcov.blogspot.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Drouting module parameters not found

[Ronald Cepres]

Hi to all,

I have a problem about the drouting module. Here is a snippet of my script
configuration:

...
loadmodule "drouting.so"
modparam("drouting", "db_url", "mysql://user:p...@localhost/opensips")
modparam("drouting", "gw_id_avp", "$avp(s:gw_id)")
modparam("drouting", "rule_id_avp", "$avp(s:rule_id)")
...

Starting OpenSIPS gives me these errors:

ERROR:core:set_mod_param_regex: parameter  not found in module

CRITICAL:core:yyerror: parse error in config file, line 111, column 33-34:
Parameter  not found in module  - can't set
ERROR:core:set_mod_param_regex: parameter  not found in module

CRITICAL:core:yyerror: parse error in config file, line 112, column 35-36:
Parameter  not found in module  - can't set

Is there a way to fix this problem? I would appreciate any kind of help.
Thanks!

By the way, I am using the OpenSIPS 1.6.3 release version.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users