Re: [OpenSIPS-Users] [Crash Report] openSIPS 2.4 clusterer module (opensipsctl fifo cluster_broadcast_mi 1 lb_reload)

[Ben Newlin]

If you’re running on an unsupported version, you’ll want to upgrade the version 
to a supported one first (2.4 or 3.0). If you’re already on one of those, or 
after upgrading, try running the latest revision (HEAD) of the respective 
branch from GitHub. Both of these steps are to make sure the crash has not 
already been fixed.

If the crash still occurs, you should check the open GitHub issues [1] to see 
if anyone has already reported a similar crash. If not, you should open a 
GitHub issue using the [CRASH] template. There are instructions on the OpenSIPS 
site [2] on how to gather the necessary information.

This is the process I have followed and seen recommended in the past. I do not 
make any claim that it is the official process. ☺

[1] https://github.com/OpenSIPS/opensips/issues
[2] https://www.opensips.org/Documentation/TroubleShooting-Crash

Ben Newlin

From: Users  on behalf of Sharad Kumar via 
Users 
Reply-To: Sharad Kumar , OpenSIPS users mailling 
list 
Date: Saturday, January 11, 2020 at 5:02 PM
To: "users@lists.opensips.org" 
Subject: [OpenSIPS-Users] [Crash Report] openSIPS 2.4 clusterer module 
(opensipsctl fifo cluster_broadcast_mi 1 lb_reload)

Hi folks,

I am encountering a segfault error, when I am trying to sync the load balancer 
module data among all nodes in the cluster. I have 2 nodes in cluster, and I am 
executing this command to reload lb module -

opensipsctl fifo cluster_broadcast_mi 1 lb_reload

After executing this command, the backup openSIPS node crash every time. Here 
are some useful logs -

Jan 11 21:45:57 ip-10-0-1-20 kernel: [600109.907423] opensips[13425]: segfault 
at 8 ip 7efe0fa33505 sp 7ffef08390a0 error 4 in 
db_mysql.so[7efe0fa24000+19000]
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
INFO:load_balancer:mi_lb_reload: "lb_reload" MI command received!
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
ERROR:core:db_use_table: invalid parameter value (nil), 0x7efe0bb1eb10
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
CRITICAL:core:sig_usr: segfault in process pid: 13425, id: 9
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: child process 13425 exited by a signal 11
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: core was not generated
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: terminating due to SIGCHLD

Please let me know if you guys need any other data to troubleshoot this issue.

Thanks and regards

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

Re: [OpenSIPS-Users] [Crash Report] openSIPS 2.4 clusterer module (opensipsctl fifo cluster_broadcast_mi 1 lb_reload)

[Johan De Clercq]

Version and backtrace will be needed.

Outlook voor iOS downloaden


Van: Users  namens Sharad Kumar via Users 

Verzonden: zaterdag, januari 11, 2020 11:02 PM
Aan: users@lists.opensips.org
Onderwerp: [OpenSIPS-Users] [Crash Report] openSIPS 2.4 clusterer module 
(opensipsctl fifo cluster_broadcast_mi 1 lb_reload)

Hi folks,

I am encountering a segfault error, when I am trying to sync the load balancer 
module data among all nodes in the cluster. I have 2 nodes in cluster, and I am 
executing this command to reload lb module -

opensipsctl fifo cluster_broadcast_mi 1 lb_reload

After executing this command, the backup openSIPS node crash every time. Here 
are some useful logs -

Jan 11 21:45:57 ip-10-0-1-20 kernel: [600109.907423] opensips[13425]: segfault 
at 8 ip 7efe0fa33505 sp 7ffef08390a0 error 4 in 
db_mysql.so[7efe0fa24000+19000]
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
INFO:load_balancer:mi_lb_reload: "lb_reload" MI command received!
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
ERROR:core:db_use_table: invalid parameter value (nil), 0x7efe0bb1eb10
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
CRITICAL:core:sig_usr: segfault in process pid: 13425, id: 9
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: child process 13425 exited by a signal 11
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: core was not generated
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: terminating due to SIGCHLD

Please let me know if you guys need any other data to troubleshoot this issue.

Thanks and regards

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

[OpenSIPS-Users] [Crash Report] openSIPS 2.4 clusterer module (opensipsctl fifo cluster_broadcast_mi 1 lb_reload)

[Sharad Kumar via Users]

Hi folks,

I am encountering a segfault error, when I am trying to sync the load balancer 
module data among all nodes in the cluster. I have 2 nodes in cluster, and I am 
executing this command to reload lb module -

opensipsctl fifo cluster_broadcast_mi 1 lb_reload

After executing this command, the backup openSIPS node crash every time. Here 
are some useful logs -

Jan 11 21:45:57 ip-10-0-1-20 kernel: [600109.907423] opensips[13425]: segfault 
at 8 ip 7efe0fa33505 sp 7ffef08390a0 error 4 in 
db_mysql.so[7efe0fa24000+19000]
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
INFO:load_balancer:mi_lb_reload: "lb_reload" MI command received!
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
ERROR:core:db_use_table: invalid parameter value (nil), 0x7efe0bb1eb10
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13425]: 
CRITICAL:core:sig_usr: segfault in process pid: 13425, id: 9
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: child process 13425 exited by a signal 11
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: core was not generated
Jan 11 21:45:57 ip-10-0-1-20 /usr/local/sbin/opensips[13412]: 
INFO:core:handle_sigs: terminating due to SIGCHLD

Please let me know if you guys need any other data to troubleshoot this issue.

Thanks and regards___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] yum repo is down

[Антон Ершов]

hi,
yum repo is down. again
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] B2B user agent logic

[Donat Zenichev]

First of all thanks for your replies Răzvan and Ben.

Ben, the case with local_route might be the thing I need. I read a bit on
the matter, but haven’t digged into it deeply yet.
I will try to play with this, one of these days, and will share my
experience to OpenSIPS community.

>From what I got, local_route first of all gives a possibility to catch and
then edit messages coming to B2Bua. Am I wrong?

Răzvan, yes topology hiding module fits this demand and I guess this is
even more simple implementation in comparison with B2B.

The idea I’m trying to follow, is that OpenSIPS plays a role of a routing
server for a border controller. And the border controller in its turn can
consider an INVITE (with already changed destination) having the same
call-id as a loop.
Thus routing solution can be implemented using two ways:
- 3XX redirection server
- B2BUA that divides a call into two legs

I guess, topology hiding module fits the second case (when I need to divide
a call) just fine.

I will try both ways with topology hiding module and local_route of b2b
module(s) and see which one fits better.
Of course I will share my experience in the end!

Have a nice day!




On Fri, 10 Jan 2020 at 5:43 PM, Răzvan Crainea  wrote:

> Hi, Donat!
>
> Indeed, the B2B module(s) are not compatible with the dialog module.
> However, if your purpose is just to have different callids between the
> two legs, why not using the topology hiding module[1], which does change
> the callids (using the "C" flag for the topology_hiding() function[2])
> and is built on top of the dialog module.
> The B2B does indeed offer a similar behavior, but it is usually used for
>   much more complex calling scenarios - if you don't need those complex
> scenarios, simply use the topology_hiding mode.
>
> [1] https://opensips.org/html/docs/modules/3.0.x/topology_hiding.html
> [2]
>
> https://opensips.org/html/docs/modules/3.0.x/topology_hiding.html#func_topology_hiding
>
> Best regards,
> Răzvan
>
> On 1/10/20 5:21 PM, Donat Zenichev wrote:
> > Hello OpenSIPS community!
> >
> > I have a brief question regarding how to better implement B2B user agent
> > logic, within OpenSIPS installation.
> >
> > The goal is quite simple:
> > - I have OpenSIPS as a routing system (making decisions on calls)
> > - OpenSIPS at the same time separates dialog into two legs (so two
> > Call-IDs as result)
> >
> > Firstly I've started looking into b2b_logic + b2b_entities modules
> > I read manuals provided by OpenSIPS dev team and everything is quite
> > clear for me.
> >
> > But, from what I understand provided b2b module is not compatible with a
> > dialog module
> > (paragraph 6 at Back-to-Back User Agent manual).
> > But dialog module is quite significant for me, at least since of
> > "dialog_replication_cluster" parameter.
> >
> > Another feature of the b2b_logic module is, that it only implements
> > scenarios within a separate xml configuration file. And from the script
> > routing you're only able to access coming requests and responses in a
> > read-only mode.
> >
> > To sum up, the general goal is to separate call into two legs, to let
> > both legs have different call-ids. And it's also quite important to be
> > able to rule changes on requests (e.g. resetting of R-URI) from the
> > routing script.
> >
> > Everything from mentioned above led me to a thought, that there could be
> > some much elaborate solution for implementation of B2B within OpenSIPS
> > installation.
> > For sure b2b_logic and b2b_entities modules are great! But still I'm
> > looking for a bit different installation.
> >
> > I know, OpenSIPS is a SIP proxy and it's not supposed to be run with a
> > role of B2BUA.
> > But still, might be someone can share his/her own experience and hint
> > some better way out for this?
> >
> > Many thanks in advance and have a nice day!
> >
> >
> >
> > --
> >
> > Best regards,
> > Donat Zenichev
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> --
> Răzvan Crainea
> OpenSIPS Core Developer
>http://www.opensips-solutions.com
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 

Best regards,
Donat Zenichev
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] update from repo fails

[Антон Ершов]

it looks like the repository is completely dead))
http://yum.opensips.org/3.0/nightly/el/7/x86_64/repodata/repomd.xml: [Errno
14] curl#7 - "Failed connect to yum.opensips.org:80


пт, 10 янв. 2020 г. в 19:10, Антон Ершов :

> Thanks!
>
> пт, 10 янв. 2020 г., 19:07 Nick Altmann :
>
>> Must be fixed for now.
>>
>> чт, 9 янв. 2020 г. в 12:13, Nick Altmann :
>>
>>> Hi,
>>>
>>> Thanks for reporting. I'll take a look at this today later.
>>>
>>> чт, 9 янв. 2020 г. в 11:35, Антон Ершов :
>>>
 Hi,
 when I try to upgrade from a repository with nightly builds I get this
 error
 rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
 opensips-yum-nightly-3.0-5.el7.noarch

 found on the network that you need to rebuild a package that supports
 this dependency.
 How can you solve this problem yourself?
 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users

>>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users