from:"Ginhoux, Patrick"

Re: [SR-Users] Mails received twice in my Inbox

2022-10-07 Thread Ginhoux, Patrick

Thanks for the list. I have now removed the one with fr unisys dot com and
will wait for new emails on the other address.

But it is still strange this problem happened recently.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : Henning Westerholt  
Envoyé : jeudi 6 octobre 2022 13:32
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : RE: Mails received twice in my Inbox

 

EXTERNAL EMAIL - Be cautious of all links and attachments.

Hello,

 

you are subscribed with two addresses, only list the domains below:

 

at fr unisys dot com

at unisys dot com

 

You can change your subscription with the URL: https://lists.kamailio.org 

 

Cheers,

 

Henning

 

From: Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> > 
Sent: Thursday, October 6, 2022 1:25 PM
To: Henning Westerholt mailto:h...@gilawa.com> >
Cc: Kamailio (SER) - Users Mailing List mailto:sr-users@lists.kamailio.org> >
Subject: RE: Mails received twice in my Inbox

 

Hi,

 

Im sure Im not registered with different account, but who can check that
in the mailing list to be sure ?

 

Actually, I registered in 2017 and this issue occurs recently but I cant
tell exactly since when.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com
<mailto:patrick.ginh...@unisys.com> 

 

De : Henning Westerholt mailto:h...@gilawa.com> > 
Envoyé : jeudi 6 octobre 2022 11:06
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.kamailio.org> >
Cc : Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >
Objet : RE: Mails received twice in my Inbox

 

EXTERNAL EMAIL - Be cautious of all links and attachments.

Hello,

 

Strange issue. Stupid question, but you are not registered two times to the
mailing list, maybe with different accounts?

 

Cheers,

 

Henning

 

-- 

Henning Westerholt   <https://skalatan.de/blog/> https://skalatan.de/blog/

Kamailio services   <https://gilawa.com/> https://gilawa.com

 

From: sr-users mailto:sr-users-boun...@lists.kamailio.org> > On Behalf Of Ginhoux, Patrick
Sent: Wednesday, October 5, 2022 10:04 AM
To: sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> 
Subject: [SR-Users] Mails received twice in my Inbox

 

Hi,

 

Since several weeks, I received the same mails twice in my Inbox.

Examples :

 



 

Is there anybody else that has the same thing ?

 

Thanks in advance for your help.

 

Cordialement.

Patrick GINHOUX 



smime.p7s
Description: S/MIME cryptographic signature
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Mails received twice in my Inbox

2022-10-06 Thread Ginhoux, Patrick

Hi,

 

Im sure Im not registered with different account, but who can check that
in the mailing list to be sure ?

 

Actually, I registered in 2017 and this issue occurs recently but I cant
tell exactly since when.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : Henning Westerholt  
Envoyé : jeudi 6 octobre 2022 11:06
À : Kamailio (SER) - Users Mailing List 
Cc : Ginhoux, Patrick 
Objet : RE: Mails received twice in my Inbox

 

EXTERNAL EMAIL - Be cautious of all links and attachments.

Hello,

 

Strange issue. Stupid question, but you are not registered two times to the
mailing list, maybe with different accounts?

 

Cheers,

 

Henning

 

-- 

Henning Westerholt   <https://skalatan.de/blog/> https://skalatan.de/blog/

Kamailio services   <https://gilawa.com/> https://gilawa.com

 

From: sr-users mailto:sr-users-boun...@lists.kamailio.org> > On Behalf Of Ginhoux, Patrick
Sent: Wednesday, October 5, 2022 10:04 AM
To: sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> 
Subject: [SR-Users] Mails received twice in my Inbox

 

Hi,

 

Since several weeks, I received the same mails twice in my Inbox.

Examples :

 



 

Is there anybody else that has the same thing ?

 

Thanks in advance for your help.

 

Cordialement.

Patrick GINHOUX 



smime.p7s
Description: S/MIME cryptographic signature
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Mails received twice in my Inbox

2022-10-05 Thread Ginhoux, Patrick

Hi,

 

Since several weeks, I received the same mails twice in my Inbox.

Examples :

 



 

Is there anybody else that has the same thing ?

 

Thanks in advance for your help.

 

Cordialement.

Patrick GINHOUX 



smime.p7s
Description: S/MIME cryptographic signature
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] How to not write logs to journald with kamailio

2021-11-25 Thread Ginhoux, Patrick

Hi,

Thanks all for your information.

Now this morning on live SIP Proxies, I have configured the
/etc/systemd/journald.conf with :

RateLimitIntervalSec=0
RateLimitBurst=0

I have restarted the journald/rsyslog services. But few seconds later, the
logging still stop again.

I have applied the other values suggested in the old article:

RateLimitBurst=100 in /etc/systemd/journald.conf

$imjournalRatelimitInterval 1 and $imjournalRatelimitBurst 50 in
/etc/rsyslog.conf

With the above values, I have new no more logs issues like reported in the
article.

The above issue is a pure OS problem and I will probably open a ticket to
RedHat.

Now back on my initial question related to journald.

On my SIP Proxies, journald is using about 10% of the CPU configured, which is
very high when Kamailio used about 1%.

So I’m looking to replace the current mechanism to write log thru the standard
openlog() and syslog() functions. I assume this is done using the ‘xlog’ module.

Do you think possible to change this by a mechanism to send log messages thru
UDP to write the logs directly to rsyslog,

meaning to replace all the xlog calls in the kamailio.cfg script ?

Cordialement.

Patrick GINHOUX

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

De : Sergey Safarov
Envoyé : mercredi 24 novembre 2021 21:49
À : Daniel-Constantin Mierla ; Kamailio (SER) - Users
Mailing List
Cc : Ginhoux, Patrick
Objet : Re: [SR-Users] How to not write logs to journald with kamailio

EXTERNAL EMAIL - Be cautious of all links and attachments.

you need configure journald config file

/etc/systemd/journald.conf

[root@bcf-b ~]# grep RateLimit /etc/systemd/journald.conf
RateLimitIntervalSec=0
RateLimitBurst=0

On Wed, Nov 24, 2021 at 7:50 PM Daniel-Constantin Mierla mailto:mico...@gmail.com> > wrote:

Hello,

kamailio uses internally openlog() and syslog() functions from standard libc.
It has not control of what the syslog daemon does, it is a matter of OS
configuration, so what you mention might be the required configuration, not a
workaround. Anyhow, maybe others can comment more.

There are many other cases when the OS has to be tuned to get desired
behaviour, eg., increase file descriptor limits to handle lots of connections.

Cheers,
Daniel

On 23.11.21 12:16, Ginhoux, Patrick wrote:

Hi,

I resend this mail because of the initial destination address was not correct.

The topic was a logging problem :

With the upgrade of my SIP Router proxies to RHEL 7 (and Kamailio 5.0.7) , we
encounter problems where the logs are blocked to be written in the syslog.

This problem is similar as the one reported in this article : [SR-Users]
Kamailio logs in RHEL 7 environment
<https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html> .

The resolution was to increase some journald/rsyslog settings
(RateLimitBurst=100 / $imjournalRatelimitInterval 1
$imjournalRatelimitBurst 50).

But it is somehow a workaround.

I’m looking to know if it should be possible for kamailio to write directly the
logs to the syslog only.

Thanks in advance to those can help me.

Regards

Patrick Ginhoux

De : Ginhoux, Patrick
Envoyé : lundi 22 novembre 2021 16:49
À : 'sr-users' <mailto:sr-users-boun...@lists.kamailio.org>

Objet : How to not write logs to journald with kamailio

Hi,

With the upgrade of my SIP Router proxies to RHEL 7 (and Kamailio 5.0.7) , we
encounter problems where the logs are blocked to be written in the syslog.

This problem is similar as the one reported in this article : [SR-Users]
Kamailio logs in RHEL 7 environment
<https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html> .

The resolution was to increase some journald/rsyslog settings
(RateLimitBurst=100 / $imjournalRatelimitInterval 1
$imjournalRatelimitBurst 50).

But it is somehow a workaround.

I’m looking to know if it should be possible for kamailio to write directly the
logs to the syslog only.

Thanks in advance to those can help me.

Regards

Patrick Ginhoux

__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--
Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio Advanced Training - Online
Feb 21-24, 2022 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/

__
Kamailio - Users Mailin

Re: [SR-Users] How to not write logs to journald with kamailio

2021-11-23 Thread Ginhoux, Patrick

Hi,

 

I resend this mail because of the initial destination address was not
correct.

 

The topic was a logging problem :

 

With the upgrade of my SIP Router proxies to RHEL 7  (and Kamailio 5.0.7) ,
we encounter problems where the logs are blocked to be written in the
syslog.

 

This problem is similar as the one reported in this article : [SR-Users]
Kamailio logs in RHEL 7 environment
<https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html> .

The resolution was to increase some journald/rsyslog settings
(RateLimitBurst=100 / $imjournalRatelimitInterval 1
$imjournalRatelimitBurst 50).
 
But it is somehow a workaround. 
 
Im looking to know if it should be possible for kamailio to write directly
the logs to the syslog only.
 
Thanks in advance to those can help me.
 

Regards

Patrick Ginhoux

 

De : Ginhoux, Patrick 
Envoyé : lundi 22 novembre 2021 16:49
À : 'sr-users' 
Objet : How to not write logs to journald with kamailio

 

Hi,

 

With the upgrade of my SIP Router proxies to RHEL 7  (and Kamailio 5.0.7) ,
we encounter problems where the logs are blocked to be written in the
syslog.

 

This problem is similar as the one reported in this article : [SR-Users]
Kamailio logs in RHEL 7 environment
<https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html> .

The resolution was to increase some journald/rsyslog settings
(RateLimitBurst=100 / $imjournalRatelimitInterval 1
$imjournalRatelimitBurst 50).
 
But it is somehow a workaround. 
 
Im looking to know if it should be possible for kamailio to write directly
the logs to the syslog only.
 
Thanks in advance to those can help me.
 

Regards

Patrick Ginhoux



smime.p7s
Description: S/MIME cryptographic signature
__
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

2018-09-04 Thread Ginhoux, Patrick

Hi,

 

Looking at your message, I checked again the installation and mainly the 
symlink I had created for Kamailio to get the socket file.

 

For some reason, this link were corrupted. Hereafter what was the issue:

 

The initial symlink for the socket file was : ln -s 
/myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock

But actually a locate command : returns strange

locate *.sock

/myqdata/mysiprdb/data/mysiprdb.sock

/var/lib/gssproxy/default.sock

/var/lib/mysql/mysql.sock

/var/lib/mysql/mysql.sock/mysiprdb.sock

The “/var/lib/mysql/mysql.sock/mysiprdb.sock” doesn’t make sense here.

And the “/var/lib/mysql/mysql.sock” was actually a directoty

[root@in52inmvt2router1 ~]# ll /var/lib/mysql/

total 4

drwx-- 2 root root 4096 Sep  4 10:21 mysql.sock

Removing all of these files/directories, then recreate the symlink have fixed 
the issue.

 

Thanks everybody for your ideas of things to check..

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : David Villasmil  
Envoyé : mardi 4 septembre 2018 09:41
À : Kamailio (SER) - Users Mailing List 
Cc : Ginhoux, Patrick 
Objet : Re: [SR-Users] Can't connect to local MySQL server (13 "Permission 
denied")

 

You should paste your failing cfg line.

 

On Tue, Sep 4, 2018, 08:39 David Villasmil mailto:david.villasmil.w...@gmail.com> > wrote:

Make sure the password is correct and try with "localhost" and if that doesn't 
work, try with 127.0.0.1

 

On Tue, Sep 4, 2018, 07:35 Henning Westerholt mailto:h...@kamailio.org> > wrote:

Am Freitag, 31. August 2018, 21:01:13 CEST schrieb Ginhoux, Patrick:
> Usually I connect on a command line like this ;
> 
> su- mysql
> 
> mysql
> 
> use siprouter;
> 
> If now I use
> 
> mysql -u siprouter -p
> 
> Enter password:
> 
> mysql:siprouter:(none)> use siprouter;
> 
> Database changed
> 
> So I can connect the local server.

Hello Patrick,

just some ideas to help you troubleshoot the problem:

- maybe there is an issue with the socket file, that kamailio uses the wrong 
socket file?
- maybe kamailio don't have file system access rights to the socket file?
- maybe there is a mistake in the kamailio cfg or an old cfg file is used?
- enable mysql server logging and try to spot something in the log during the 
kamailio start

Best regards,

Henning

-- 
Henning Westerholt
https://skalatan.de/blog/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> 
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

2018-08-31 Thread Ginhoux, Patrick

Hi Henning,

 

Usually I connect on a command line like this ;

su- mysql

mysql

use siprouter;



 

If now I use 

mysql -u siprouter -p

Enter password:

mysql:siprouter:(none)> use siprouter;

Database changed

 

So I can connect the local server.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

-Message d'origine-
De : Henning Westerholt  
Envoyé : vendredi 31 août 2018 19:07
À : sr-users@lists.kamailio.org
Cc : Ginhoux, Patrick 
Objet : Re: [SR-Users] Can't connect to local MySQL server (13 "Permission
denied")

 

Am Freitag, 31. August 2018, 09:07:51 CEST schrieb Ginhoux, Patrick:

> In a previous post ([SR-Users] Questions about changes between 5.0.1 and

> 5.0.7

> < <https://lists.kamailio.org/pipermail/sr-users/2018-August/102442.html>
https://lists.kamailio.org/pipermail/sr-users/2018-August/102442.html> ), I

> reported problem to upgrade my kamailio from 5.0.1 to 5.0.7-7 level.

> 

> With help from some people, it was finally fixed on my test server in my

> lab.

 

Hello Patrick,

 

the mysql module will usually just give you the error message back from the 

server/mysql client library.

 

Can you try to connect with the "mysql" client command on the command line
to 

connect to the local server, with the same username/password as in your 

Kamailio configuration?

> Now I was expecting to do the same upgrade on a real server using these

> packages:

> 

> kamailio-5.0.7-7.el7.x86_64.rpm 

> kamailio-ims-5.0.7-7.el7.x86_64.rpm 

> kamailio-mysql-5.0.7-7.el7.x86_64.rpm 

> kamailio-perl-5.0.7-7.el7.x86_64.rpm 

> kamailio-snmpstats-5.0.7-7.el7.x86_64.rpm

> 

> But kamailio failed to connect the local MySQL server :

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> DEBUG:  [db.c:314]: db_do_init2(): connection 0x7fef779958f8 not
found

> in pool

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening

> connection: mysql://:@localhost/siprouter

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver
error:

> Can't connect to local MySQL server through socket

> '/var/lib/mysql/mysql.sock' (13 "Permission denied")

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> ERROR:  [db.c:318]: db_do_init2(): could not add connection to the

> pool

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the

> database

> 

> Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:

> ERROR:  [core/sr_module.c:974]: init_mod(): Error while initializing

> module htable (/usr/lib64/kamailio/modules/htable.so)

> 

> 

> 

> My "kamailio.cfg" contains the following command:

> 

> 

> 

> modparam("htable", "db_url",

> "mysql://siprouter:password@localhost/siprouter")

> 

> 

> 

> The service unit : "/usr/lib/systemd/system/kamailio.service" content is :

> 

> 

> 

> [Unit]

> 

> Description=Kamailio (OpenSER) - the Open Source SIP Server

> 

> After=network.target mysql.service

> 

> 

> 

> [Service]

> 

> Type=simple

> 

> User=kamailio

> 

> Group=kamailio

> 

> Environment='CFGFILE=/etc/kamailio/kamailio.cfg'

> 

> Environment='SHM_MEMORY=1024'

> 

> Environment='PKG_MEMORY=8'

> 

> EnvironmentFile=-/etc/sysconfig/kamailio

> 

> ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f

> $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY

> 

> Restart=on-failure

> 

> 

> 

> [Install]

> 

> WantedBy=multi-user.target

> 

> 

> 

> The "/etc/sysconfig/kamailio" content is :

> 

> 

> 

> #

> 

> # Kamailio startup options

> 

> #

> 

> 

> 

> #

> 

> # Kamailio startup options

> 

> #

> 

> 

> 

> # Set to yes to enable kamailio, once configured properly.

> 

> RUN_KAMAILIO=yes

> 

> 

> 

> # User to run as

> 

> USER=kamailio

> 

> 

> 

> # Group to run as

> 

> GROUP=kamailio

> 

> 

> 

> # Amount of shared memory to allocate for the running Kamailio server (in

> Mb)

> 

> SHM_MEMORY=1024

> 

> 

> 

> # Amount of per-proces

[SR-Users] Can't connect to local MySQL server (13 "Permission denied")

2018-08-31 Thread Ginhoux, Patrick

Hi,

 

In a previous post ([SR-Users] Questions about changes between 5.0.1 and
5.0.7
 ), I
reported problem to upgrade my kamailio from 5.0.1 to 5.0.7-7 level.

With help from some people, it was finally fixed on my test server in my
lab.

 

Now I was expecting to do the same upgrade on a real server using these
packages:

kamailio-5.0.7-7.el7.x86_64.rpm

kamailio-ims-5.0.7-7.el7.x86_64.rpm

kamailio-mysql-5.0.7-7.el7.x86_64.rpm

kamailio-perl-5.0.7-7.el7.x86_64.rpm

kamailio-snmpstats-5.0.7-7.el7.x86_64.rpm

 

But kamailio failed to connect the local MySQL server :

 

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
DEBUG:  [db.c:314]: db_do_init2(): connection 0x7fef779958f8 not found
in pool

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening
connection: mysql://:@localhost/siprouter

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error:
Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (13 "Permission denied")

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
ERROR:  [db.c:318]: db_do_init2(): could not add connection to the
pool

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the
database

Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]:
ERROR:  [core/sr_module.c:974]: init_mod(): Error while initializing
module htable (/usr/lib64/kamailio/modules/htable.so)

 

My "kamailio.cfg" contains the following command:

 

modparam("htable", "db_url",
"mysql://siprouter:password@localhost/siprouter") 

 

The service unit : "/usr/lib/systemd/system/kamailio.service" content is :

 

[Unit]

Description=Kamailio (OpenSER) - the Open Source SIP Server

After=network.target mysql.service

 

[Service]

Type=simple

User=kamailio

Group=kamailio

Environment='CFGFILE=/etc/kamailio/kamailio.cfg'

Environment='SHM_MEMORY=1024'

Environment='PKG_MEMORY=8'

EnvironmentFile=-/etc/sysconfig/kamailio

ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f
$CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY

Restart=on-failure

 

[Install]

WantedBy=multi-user.target

 

The "/etc/sysconfig/kamailio" content is :

 

#

# Kamailio startup options

#

 

#

# Kamailio startup options

#

 

# Set to yes to enable kamailio, once configured properly.

RUN_KAMAILIO=yes

 

# User to run as

USER=kamailio

 

# Group to run as

GROUP=kamailio

 

# Amount of shared memory to allocate for the running Kamailio server (in
Mb)

SHM_MEMORY=1024

 

# Amount of per-process (package) memory to allocate for Kamailio (in Mb)

PKG_MEMORY=8

 

Below the existing user in mysql :

 

mysql:root:(none)> use mysql;

Database changed

mysql:root:mysql> select user,host from user;

+---+---+

| user  | host  |

+---+---+

| myadmin   | % |

| siprouter | % |

| kamailio  | localhost |

| root  | localhost |

+---+---+

I have a symlink to locate the my.cnf : ln -s /myqdata/mysiprdb/data/my.cnf
/etc/my.cnf

And also this link to fix a htable reload problem : ln -s
/myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock

 

I don't find what the problem is this time.

 

So if there is people that could help on the issue, thanks in advance.

 

Cordialement.

Patrick GINHOUX 

 



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Fail to reload htable

2018-08-23 Thread Ginhoux, Patrick

Hi,

 

Well, my mistake, I thought it was the ‘auth’ attribute that you mentioned .

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : Daniel-Constantin Mierla  
Envoyé : jeudi 23 août 2018 16:20
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List ; 
Soltanici Ilie ; Henning Westerholt 
Objet : Re: [SR-Users] Fail to reload htable

 

Hello,

in your email you have htable defined with dbtable attribute, like one pasted 
next, which I grabbed from the link you provided:

modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")


So it is not the same case.

The dbtable attribute should be listed in the section documenting htable 
parameter. Or, were you asking something else?

Cheers,
Daniel

On 23.08.18 16:07, Ginhoux, Patrick wrote:

Hi Daniel,

 

May I ask you some questions about the htable reload problem ?

 

I reported a similar case that Henning and I have discussed 
(https://lists.kamailio.org/pipermail/sr-users/2018-August/102393.html). I 
solved it by adding a symlink as follows:

mkdir /var/lib/mysql

ln -s /myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock

 

Here, you pointed about the htable auth defined with dbtable attribute in the 
config file.

 

I was looking at the documentation for the 5.0.7 level but I don’t find the 
reference of this settings. Can you show me where it is documented?

 

And do you think it could also fix my case ?

 

Thanks in advance for the help.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com 
<mailto:patrick.ginh...@unisys.com> 

 

De : sr-users  <mailto:sr-users-boun...@lists.kamailio.org> 
 De la part de Soltanici Ilie
Envoyé : mercredi 22 août 2018 13:52
À : mico...@gmail.com <mailto:mico...@gmail.com> 
Cc : Kamailio (SER) - Users Mailing List  <mailto:sr-users@lists.kamailio.org> 

Objet : Re: [SR-Users] Fail to reload htable

 

Daniel,

I need to reload a hash table to clear all records without waiting before they 
will expire. I can delete them all one by one with htable.delete - or make a 
loop with htable.dump and then delete them - but I was thinking that the same 
can be achieved by htable.reload command.

I didn't pay attention to this line from the documentation: "Reload hash table 
from database."
Thank You




Среда, 22 августа 2018, 11:47 +01:00 от Daniel-Constantin Mierla 
mailto:mico...@gmail.com> >:

Hello,

then there is no database table from where to reload -- why you issue a reload 
in this case? It should be done only when writing records to database table and 
then you want them to be loaded in memory.

Cheers,
Daniel

 

On 21.08.18 19:06, Soltanici Ilie wrote:

Hi Daniel,

No, it is not.

modparam("htable", "htable", "auth=>size=8;autoexpire=300;")





Вторник, 21 августа 2018, 8:07 +01:00 от Daniel-Constantin Mierla  
 
:

Hello,

is the htable auth defined with dbtable attribute?

Cheers,
Daniel


On 20.08.18 21:04, Henning Westerholt wrote:
> Am Montag, 20. August 2018, 20:58:43 CEST schrieb Soltanici Ilie:
>> In the logs, I see these errors:
>>
>> ERROR:  [db.c:463]: db_use_table(): invalid parameter value
>> Aug 20 19:56:41 kamailio[12716]: ERROR:  [db.c:463]: db_use_table():
>> invalid parameter value Aug 20 19:56:41 kamailio[12716]: ERROR: htable
>> [ht_db.c:211]: ht_db_load_table(): failed to use_table
> Hi,
>
> please keep the list in CC.
>
> This error is related to a database issue. Please double check if there are 
> any issues during startup in the log. Do you see any other error there?
>
> A similar (not 100% identical) issue was discussed recently here:
>
> https://lists.kamailio.org/pipermail/sr-users/2018-August/102393.html
>
> Maybe this helps you as well.
>
> Best regards,
>
> Henning
>

-- 
Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> 
www.twitter.com/miconda <http://www.twitter.com/miconda>  -- 
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> 
Kamailio World Conference -- www.kamailioworld.com 
<http://www.kamailioworld.com> 



С уважением,
Ilie Soltanici
ili...@mail.ru  






-- 
Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> 
www.twitter.com/miconda <http://www.twitter.com/miconda>  -- 
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> 
Kamailio World Conference -- www.kamailioworld.com 
<http://www.kamailioworld.com> 



С уважением,
Ilie Soltanici
ili...@mail.ru <mailto:ili...@mail.ru> 





-- 
Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> 
www.twitter.com/miconda <http://www.twitter.com/miconda>  -- 
www.linkedin.com/in/miconda <http://www.linkedin.com/in/mi

Re: [SR-Users] Fail to reload htable

2018-08-23 Thread Ginhoux, Patrick

Hi Daniel,

May I ask you some questions about the htable reload problem ?

I reported a similar case that Henning and I have discussed 
(https://lists.kamailio.org/pipermail/sr-users/2018-August/102393.html). I 
solved it by adding a symlink as follows:

mkdir /var/lib/mysql

ln -s /myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock

Here, you pointed about the htable auth defined with dbtable attribute in the 
config file.

I was looking at the documentation for the 5.0.7 level but I don’t find the 
reference of this settings. Can you show me where it is documented?

And do you think it could also fix my case ?

Thanks in advance for the help.

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

De : sr-users  De la part de Soltanici Ilie
Envoyé : mercredi 22 août 2018 13:52
À : mico...@gmail.com
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Fail to reload htable

Daniel,

I need to reload a hash table to clear all records without waiting before they 
will expire. I can delete them all one by one with htable.delete - or make a 
loop with htable.dump and then delete them - but I was thinking that the same 
can be achieved by htable.reload command.

I didn't pay attention to this line from the documentation: "Reload hash table 
from database."
Thank You

Среда, 22 августа 2018, 11:47 +01:00 от Daniel-Constantin Mierla 
mailto:mico...@gmail.com> >:

Hello,

then there is no database table from where to reload -- why you issue a reload 
in this case? It should be done only when writing records to database table and 
then you want them to be loaded in memory.

Cheers,
Daniel

On 21.08.18 19:06, Soltanici Ilie wrote:

Hi Daniel,

No, it is not.

modparam("htable", "htable", "auth=>size=8;autoexpire=300;")

Вторник, 21 августа 2018, 8:07 +01:00 от Daniel-Constantin Mierla  

:

Hello,

is the htable auth defined with dbtable attribute?

Cheers,
Daniel

On 20.08.18 21:04, Henning Westerholt wrote:
> Am Montag, 20. August 2018, 20:58:43 CEST schrieb Soltanici Ilie:
>> In the logs, I see these errors:
>>
>> ERROR:  [db.c:463]: db_use_table(): invalid parameter value
>> Aug 20 19:56:41 kamailio[12716]: ERROR:  [db.c:463]: db_use_table():
>> invalid parameter value Aug 20 19:56:41 kamailio[12716]: ERROR: htable
>> [ht_db.c:211]: ht_db_load_table(): failed to use_table
> Hi,
>
> please keep the list in CC.
>
> This error is related to a database issue. Please double check if there are 
> any issues during startup in the log. Do you see any other error there?
>
> A similar (not 100% identical) issue was discussed recently here:
>
> https://lists.kamailio.org/pipermail/sr-users/2018-August/102393.html
>
> Maybe this helps you as well.
>
> Best regards,
>
> Henning
>

-- 
Daniel-Constantin Mierla -- www.asipto.com  
www.twitter.com/miconda   -- 
www.linkedin.com/in/miconda  
Kamailio World Conference -- www.kamailioworld.com 

С уважением,
Ilie Soltanici
ili...@mail.ru  

-- 
Daniel-Constantin Mierla -- www.asipto.com  
www.twitter.com/miconda   -- 
www.linkedin.com/in/miconda  
Kamailio World Conference -- www.kamailioworld.com 

С уважением,
Ilie Soltanici
ili...@mail.ru  

smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

2018-08-10 Thread Ginhoux, Patrick

Hi Henning,

 

I review the my.cnf file on my serve. I dont find the readme, 

but by looking the doc
(https://www.kamailio.org/docs/modules/stable/modules/db_mysql.html#idp38664
564), it seems correct.

 

It is located at <<<< /myqdata/mysiprdb/data/my.cnf >>>.

It contains the following sections :

 

[client]

port=3306

socket=/myqdata/mysiprdb/data/mysiprdb.sock 

 

[kamailio]

socket = /myqdata/mysiprdb/data/mysiprdb.sock

user = siprouter

password = Isgcomms1!

default-character-set = utf8

 

In my kamailio.cfg, I have :

modparam("htable", "db_url",
"mysql://siprouter:Isgcomms1!@localhost/siprouter")

 

So, I expected that there is no need to have symlinkg to locate the db.

 

Is there a config issue ?

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

-Message d'origine-
De : Henning Westerholt  
Envoyé : jeudi 9 août 2018 21:31
À : Ginhoux, Patrick 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Am Donnerstag, 9. August 2018, 09:51:31 CEST schrieb Ginhoux, Patrick:

> Some update since recent discussions about the changes between 5.0.1 and

> 5.0.7 with Sergey Safarov :

 

Hello Patrick,

 

thank you for the update, and great that you figured out the issues. 

 

> 

> -  The mod_perl module had been introduced by mistake in the 5.0.7

> stream so that new packages are now available (5.0.7-7) without this
module,

> packages I use to upgrade my server.

 

Yes, I saw the commit. Good that its now fixed. Some more comments below.

 

> -  Once the upgrade done to 5.0.7-7 level, I reported 2 problems :

> 

> o   An error reported by the jsonrpcs module : ERROR: jsonrpcs

> [jsonrpcs_fifo.c:82]: jsonrpc_init_fifo_server(): Failed to change the

> owner/group for /var/run/kamailio/kamailio_rpc_fifo  to 248.248; Operation

> not permitted[1]

> 

> ð  It is fixed now by configuring the USER/GROUP parameters with the
correct

> values in the systemd unit file

> 

> o   An error to open the MySQL: ERROR: db_mysql [km_my_con.c:129]:

> db_mysql_new_connection(): driver error: Can't connect to local MySQL
server

> through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

> 

> ð  Initially on my Kamailio with 5.0.1, I had created these 2 symbolic
links

> to get the connection to the local MySQL server:

> 

> #Symbolic links for the MySQL to MariaDB change to allow kamailio to
locate

> the mysql libs and then open the siprouter database

> 

> ln -s /opt/mysql/na/10.2.14/lib64/libmysqlclient.so.18.0.0

> /usr/lib64/libmysqlclient.so.18

> 

> ln -s /myqdata/mysiprdb/data/my.cnf /etc/my.cnf

> 

> This was good for kamailio to open the local MySQL server, but it failed
to

> reload a Hash table; the kamcmd htable.reload propertiesHash returns a

> problem :

> 

> kamcmd htable.reload propertiesHash

> 

> error: 500 - Failed to open htable db connection

> 

> The kamailio.log reported that it can't connect the db :

> 

> DEBUG:  [core/sr_module.c:694]: find_mod_export_record():

> find_export_record: found  in module db_mysql

> [/usr/lib64/kamailio/modules/db_mysql.so]

> 

> DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

> 

> DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f68cc354c10 not
found

> in pool

> 

> DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening

> connection: mysql://:@/siprouter

> 

> ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver
error:

> Can't connect to local MySQL server through socket

> '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

> 

> ð  Now with my Kamailio upgraded with 5.0.7-7, it fails immediately at the

> startup to connect the local MySQL server.

 

Interesting behavior, but as you said - good that its fails now immediately.


 

> DEBUG:  [core/sr_module.c:698]: find_mod_export_record():

> find_export_record: found  in module db_mysql

> [/usr/lib64/kamailio/modules/db_mysql.so]

> 

> DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

> 

> DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f65e4974868 not
found

> in pool

> 

> DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening

> connection: mysql://:@localhost/siprouter

> 

> ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver
error:

> Can't connect to local MySQL server through socket

> '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

> 

> That is a strange behavior versus the one with kamailio 5.0.1, but it is

> maybe better as it immediately fails.

>

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

2018-08-09 Thread Ginhoux, Patrick

Hi Henning,

 

Some update since recent discussions about the changes between 5.0.1 and
5.0.7 with Sergey Safarov :

 

-  The mod_perl module had been introduced by mistake in the 5.0.7
stream so that new packages are now available (5.0.7-7) without this module,
packages I use to upgrade my server.

 

-  Once the upgrade done to 5.0.7-7 level, I reported 2 problems :

 

o   An error reported by the jsonrpcs module : ERROR: jsonrpcs
[jsonrpcs_fifo.c:82]: jsonrpc_init_fifo_server(): Failed to change the
owner/group for /var/run/kamailio/kamailio_rpc_fifo  to 248.248; Operation
not permitted[1]

 

ð  It is fixed now by configuring the USER/GROUP parameters with the correct
values in the systemd unit file 

 

o   An error to open the MySQL: ERROR: db_mysql [km_my_con.c:129]:
db_mysql_new_connection(): driver error: Can't connect to local MySQL server
through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

 

ð  Initially on my Kamailio with 5.0.1, I had created these 2 symbolic links
to get the connection to the local MySQL server:

 

#Symbolic links for the MySQL to MariaDB change to allow kamailio to locate
the mysql libs and then open the siprouter database

ln -s /opt/mysql/na/10.2.14/lib64/libmysqlclient.so.18.0.0
/usr/lib64/libmysqlclient.so.18

ln -s /myqdata/mysiprdb/data/my.cnf /etc/my.cnf

 

This was good for kamailio to open the local MySQL server, but it failed to
reload a Hash table; the kamcmd htable.reload propertiesHash returns a
problem :

 

kamcmd htable.reload propertiesHash

error: 500 - Failed to open htable db connection

 

The kamailio.log reported that it can't connect the db :

 

DEBUG:  [core/sr_module.c:694]: find_mod_export_record():
find_export_record: found  in module db_mysql
[/usr/lib64/kamailio/modules/db_mysql.so]

DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f68cc354c10 not found
in pool

DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening
connection: mysql://:@/siprouter

ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error:
Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2 "No such file or directory")

 

ð  Now with my Kamailio upgraded with 5.0.7-7, it fails immediately at the
startup to connect the local MySQL server.

 

DEBUG:  [core/sr_module.c:698]: find_mod_export_record():
find_export_record: found  in module db_mysql
[/usr/lib64/kamailio/modules/db_mysql.so]

DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f65e4974868 not found
in pool

DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening
connection: mysql://:@localhost/siprouter

ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error:
Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2 "No such file or directory")

 

That is a strange behavior versus the one with kamailio 5.0.1, but it is
maybe better as it immediately fails.

 

In all the case, I had have to do the following the fix the issue :

 

mkdir /var/lib/mysql

ln -s /myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock

 

This new symbolic link would then replace the first I had created : ln -s
/myqdata/mysiprdb/data/my.cnf /etc/my.cnf.

 

If I can consider these problems as fixed, it lets me confused on the manner
the db_mysql module works.

I would expect that it would find by configuration the location on the local
MySQL server. But is seems not.

 

If you have comments on that, please advise.

 

Thanks in advance.

 

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : sr-users  De la part de Ginhoux,
Patrick
Envoyé : mardi 7 août 2018 16:50
À : Henning Westerholt 
Cc : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Hi Henning,

 

Some update on my upgrade to kamailio 5.0.7.

 

First of all, I posted other question related to the mod_perl requirement,
etc... and I got some interesting answers.

 

I succeeded to get rid of the dependencies and now my server is upgraded to
5.0.7. Unfortunately, Kamailio doesn't start and is in a kind of loop.

 

The kamailio.log contains entries I've never seen before with 5.0.1. Extract
of the log :

 

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG:  [core/cfg.y:1623]:
yyparse(): loading module app_perl.so

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: 
[core/sr_module.c:575]: load_module(): trying to load


Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: 
[core/sr_module.c:624]: load_module(): attempt to lookup exports structure
failed - dlerror: /usr/lib64/kamailio/modules/app_perl.so: undefined symbol:
exports

Aug  7 10:02:09 vm-siprouter74 kamailio: DEBUG: 
[core/sr_module.c:636]: load_module()

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

2018-08-08 Thread Ginhoux, Patrick

Well, previously we changed the memory allocated in the <<<< 
/etc/default/kamailio >>>> config file : 

#

# Kamailio startup options

#

 

# Set to yes to enable kamailio, once configured properly.

RUN_KAMAILIO=yes

 

# User to run as

USER=kamailio

 

# Group to run as

GROUP=kamailio

 

# Amount of shared memory to allocate for the running Kamailio server (in Mb)

SHM_MEMORY=1024

 

# Amount of private memory to allocate for the running Kamailio server (in Mb)

PKG_MEMORY=8

 

# Enable the server to leave a core file when it crashes.

# Set this to 'yes' to enable kamailio to leave a core file when it crashes

# or 'no' to disable this feature. This option is case sensitive and only

# accepts 'yes' and 'no' and only in lowercase letters.

# On some systems (e.g. Ubuntu 6.10, Debian 4.0) it is necessary to specify

# a directory for the core files to get a dump. Look into the kamailio

# init file for an example configuration.

DUMP_CORE=no

 

# Add extra command line parameters in the EXTRA_OPTIONS variable

# EXTRA_OPTIONS="-a no"

 

Now such changes need to be applied in the new service unit file <<<< 
/usr/lib/systemd/system/kamailio.service >>>> :

 

Description=Kamailio (OpenSER) - the Open Source SIP Server

After=network.target mysql.service

 

[Service]

Type=simple

User=kamailio

Group=daemon

Environment='CFGFILE=/etc/kamailio/kamailio.cfg'

Environment='SHM_MEMORY=1024'

Environment='PKG_MEMORY=8'

EnvironmentFile=-/etc/sysconfig/kamailio

ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE 
-m $SHM_MEMORY -M $PKG_MEMORY

Restart=on-failure

 

[Install]

WantedBy=multi-user.target

 

That’s all changes I’ve seen.

 

But now my kamailio doesn’t start due to jsonpcs issue I describe in my initial 
thread : [SR-Users] kamcmd htable.reload propertiesHash problem.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : sr-users  De la part de Sergey Safarov
Envoyé : mercredi 8 août 2018 10:29
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

 

Kamailio is upgraded.

Check old config at kamailio.rpmsave

ср, 8 авг. 2018 г., 10:02 Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >:

Sergey,

 

I have successfully downloaded the new stream for 5.0.7 that is now 5.0.7-7 
(previously 5.0.7-1).

 

Then after restoring my Kamailio server before the initial upgrade with 
5.0.7-1, I have upgraded it with the 5.0.7-7 packages.

Now there is no more dependencies with the mod_perl package (good job) but only 
with the kamailio-ims package I’ve already seen:

 

[root@vm-siprouter74 kamailio-5.0.7-7]# ll

total 5484

-rw--- 1 root root 5368448 Aug  7 21:05 kamailio-5.0.7-7.el7.x86_64.rpm

-rw--- 1 root root   75208 Aug  7 21:05 
kamailio-mysql-5.0.7-7.el7.x86_64.rpm

-rw--- 1 root root   81516 Aug  7 21:05 kamailio-perl-5.0.7-7.el7.x86_64.rpm

-rw--- 1 root root   84096 Aug  7 21:05 
kamailio-snmpstats-5.0.7-7.el7.x86_64.rpm

 

[root@vm-siprouter74 kamailio-5.0.7-7]# rpm -Uvh *

warning: kamailio-5.0.7-7.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 
941fdbdd: NOKEY

error: Failed dependencies:

libkamailio_ims.so.0()(64bit) is needed by kamailio-5.0.7-7.el7.x86_64

 

Adding the kamailio-ims-5.0.7-7.el7 package get rid of this :

 

[root@vm-siprouter74 kamailio-5.0.7-7]# rpm -Uvh *

warning: kamailio-5.0.7-7.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 
941fdbdd: NOKEY

Preparing...  # [100%]

Updating / installing...

   1:kamailio-ims-5.0.7-7.el7 # [ 11%]

   2:kamailio-5.0.7-7.el7 warning: /etc/kamailio/kamailio.cfg 
created as /etc/kamailio/kamailio.cfg.rpmnew

warning: /etc/kamailio/kamctlrc created as /etc/kamailio/kamctlrc.rpmnew

# [ 22%]

   3:kamailio-mysql-5.0.7-7.el7   # [ 33%]

   4:kamailio-perl-5.0.7-7.el7# [ 44%]

   5:kamailio-snmpstats-5.0.7-7.el7   # [ 56%]

Cleaning up / removing...

   6:kamailio-snmpstats-5.0.1-1.1 # [ 67%]

   7:kamailio-perl-5.0.1-1.1  # [ 78%]

   8:kamailio-mysql-5.0.1-1.1 # [ 89%]

   9:kamailio-5.0.1-1.1   warning: /etc/rc.d/init.d/kamailio saved 
as /etc/rc.d/init.d/kamailio.rpmsave

# [100%]

warning: /etc/default/kamailio saved as /etc/default/kamailio.rpmsave

 

Any comments on this upgrade and the kamailio-ims dependencies?

 

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com 
<mailto:patrick.ginh...@unisys

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

2018-08-08 Thread Ginhoux, Patrick

Sergey,

 

I have successfully downloaded the new stream for 5.0.7 that is now 5.0.7-7 
(previously 5.0.7-1).

 

Then after restoring my Kamailio server before the initial upgrade with 
5.0.7-1, I have upgraded it with the 5.0.7-7 packages.

Now there is no more dependencies with the mod_perl package (good job) but only 
with the kamailio-ims package I’ve already seen:

 

[root@vm-siprouter74 kamailio-5.0.7-7]# ll

total 5484

-rw--- 1 root root 5368448 Aug  7 21:05 kamailio-5.0.7-7.el7.x86_64.rpm

-rw--- 1 root root   75208 Aug  7 21:05 
kamailio-mysql-5.0.7-7.el7.x86_64.rpm

-rw--- 1 root root   81516 Aug  7 21:05 kamailio-perl-5.0.7-7.el7.x86_64.rpm

-rw--- 1 root root   84096 Aug  7 21:05 
kamailio-snmpstats-5.0.7-7.el7.x86_64.rpm

 

[root@vm-siprouter74 kamailio-5.0.7-7]# rpm -Uvh *

warning: kamailio-5.0.7-7.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 
941fdbdd: NOKEY

error: Failed dependencies:

libkamailio_ims.so.0()(64bit) is needed by kamailio-5.0.7-7.el7.x86_64

 

Adding the kamailio-ims-5.0.7-7.el7 package get rid of this :

 

[root@vm-siprouter74 kamailio-5.0.7-7]# rpm -Uvh *

warning: kamailio-5.0.7-7.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 
941fdbdd: NOKEY

Preparing...  # [100%]

Updating / installing...

   1:kamailio-ims-5.0.7-7.el7 # [ 11%]

   2:kamailio-5.0.7-7.el7 warning: /etc/kamailio/kamailio.cfg 
created as /etc/kamailio/kamailio.cfg.rpmnew

warning: /etc/kamailio/kamctlrc created as /etc/kamailio/kamctlrc.rpmnew

# [ 22%]

   3:kamailio-mysql-5.0.7-7.el7   # [ 33%]

   4:kamailio-perl-5.0.7-7.el7# [ 44%]

   5:kamailio-snmpstats-5.0.7-7.el7   # [ 56%]

Cleaning up / removing...

   6:kamailio-snmpstats-5.0.1-1.1 # [ 67%]

   7:kamailio-perl-5.0.1-1.1  # [ 78%]

   8:kamailio-mysql-5.0.1-1.1 # [ 89%]

   9:kamailio-5.0.1-1.1   warning: /etc/rc.d/init.d/kamailio saved 
as /etc/rc.d/init.d/kamailio.rpmsave

# [100%]

warning: /etc/default/kamailio saved as /etc/default/kamailio.rpmsave

 

Any comments on this upgrade and the kamailio-ims dependencies?

 

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : sr-users  De la part de Sergey Safarov
Envoyé : mardi 7 août 2018 18:38
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

 

We still have not resolved issue with RPM build service.

But you can try download from 
https://download.opensuse.org/repositories/home:/kamailio:/v5.0.x-rpms/RHEL_7/
after 40 min

 

вт, 7 авг. 2018 г. в 17:30, Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >:

Sergey,

 

Good to know that mistake and that there is a fixed. Do you know if there is a 
new Kamailio-perl rpm available ?

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12   | +33 6 60 32 24 
74   | patrick.ginh...@unisys.com 
<mailto:patrick.ginh...@unisys.com> 

 

De : sr-users mailto:sr-users-boun...@lists.kamailio.org> > De la part de Sergey Safarov
Envoyé : mardi 7 août 2018 13:51


À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.kamailio.org> >
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

 

Typo

 

Correct 

mod_perl and mod_perl-devel dependency is added by mistake. PR is fixed this

About package moving between repos please ask RHEL support team. RHEL is drives 
this process.

 

Sergey.

 

вт, 7 авг. 2018 г. в 14:49, Sergey Safarov mailto:s.safa...@gmail.com> >:

I mod_perl and mod_perl-devel dependency is added by mistake. PR is fixed this

About package moving between repos please as RHEL support team. RHEL is drives 
this process.

 

Sergey.

вт, 7 авг. 2018 г. в 14:43, Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >:

Hi Sergey,

 

Thanks for the link that shows the mod_perl use.

 

But I’m interested to understand why such change between the 5.0.1 and 5.0.7 
level. And also why the use of mod_perl which is removed from official distro.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12   | +33 6 60 32 24 
74   | patrick.ginh...@unisys.com 
<mailto:patrick.ginh...@unisys.com> 

 

De : sr-users mailto:sr-users-boun...@lists.kamailio.org> > De la part de Sergey Safarov
Envoyé : mardi 7 août 2018 11:37
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.kamailio.org> >
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

 

Hello Patrick

Please review packaging PR https://github.com/kamailio/kamailio/pull/1615

вт, 7 авг

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

2018-08-07 Thread Ginhoux, Patrick

Sergey,

Good to know that mistake and that there is a fixed. Do you know if there is a
new Kamailio-perl rpm available ?

Cordialement.

Patrick GINHOUX

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

De : sr-users De la part de Sergey Safarov
Envoyé : mardi 7 août 2018 13:51
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

Typo

Correct

mod_perl and mod_perl-devel dependency is added by mistake. PR is fixed this

About package moving between repos please ask RHEL support team. RHEL is drives
this process.

Sergey.

вт, 7 авг. 2018 г. в 14:49, Sergey Safarov mailto:s.safa...@gmail.com> >:

I mod_perl and mod_perl-devel dependency is added by mistake. PR is fixed this

About package moving between repos please as RHEL support team. RHEL is drives
this process.

Sergey.

вт, 7 авг. 2018 г. в 14:43, Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >:

Hi Sergey,

Thanks for the link that shows the mod_perl use.

But I’m interested to understand why such change between the 5.0.1 and 5.0.7
level. And also why the use of mod_perl which is removed from official distro.

Cordialement.

Patrick GINHOUX

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24
74 | patrick.ginh...@unisys.com
<mailto:patrick.ginh...@unisys.com>

De : sr-users mailto:sr-users-boun...@lists.kamailio.org> > De la part de Sergey Safarov
Envoyé : mardi 7 août 2018 11:37
À : Kamailio (SER) - Users Mailing List mailto:sr-users@lists.kamailio.org> >
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

Hello Patrick

Please review packaging PR https://github.com/kamailio/kamailio/pull/1615

вт, 7 авг. 2018 г. в 9:52, Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >:

Hi,

Following a problem with the kamcmd htable.reload with Kamailio 5.0.1 (see
related thread for this), I have upgraded to the 5.0.7 level (with some
difficulties due to my specific environment).

My server runs the RHEL 7.4 distribution.

Now the upgrade is complete, I notice that that are changes not really
documented:

- The kamailio-perl-5.0.7-1.el7.x86_64.rpm requires to install the
mod_perl module that doesn’t exist anymore in RHEL 7. It needs to be installed
from the EPEL repository

- The init script for kamailio has been changed from the old method to
the fully compliant method for system unit for RHEL 7 for example:

With the 5.0.1 level we have the “/etc/rc.d/init.d/kamailio”

With the 5.0.7 level we have now the “/usr/lib/systemd/system/kamailio.service”

So my questions/comments are :

- Why the mod_perl module is required between 5.0.1 and 5.0.7
(question posted in the attached message) ?

- In the previous kamailo init script, I added a condition to start
MySQL before kamailio by adding this entry in the script : # Required-Start:
$syslog $network $mysqld

The new script contains the After command :

[Unit]

Description=Kamailio (OpenSER) - the Open Source SIP Server

After=network.target

Should I change the After line with this : After=network.target mysql.target to
have the same condition?

In all the cases, some documentation must be changed to provide more details.

Thanks in advance for the answers.

Cordialement.

Patrick GINHOUX

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

2018-08-07 Thread Ginhoux, Patrick

Hi Sergey,

 

Thanks for the link that shows the mod_perl use.

 

But I’m interested to understand why such change between the 5.0.1 and 5.0.7 
level. And also why the use of mod_perl which is removed from official distro.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : sr-users  De la part de Sergey Safarov
Envoyé : mardi 7 août 2018 11:37
À : Kamailio (SER) - Users Mailing List 
Objet : Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

 

Hello Patrick

Please review packaging PR https://github.com/kamailio/kamailio/pull/1615

вт, 7 авг. 2018 г. в 9:52, Ginhoux, Patrick mailto:patrick.ginh...@fr.unisys.com> >:

Hi,

 

Following a problem with the kamcmd htable.reload with Kamailio 5.0.1 (see 
related thread for this), I have upgraded to the 5.0.7 level (with some 
difficulties due to my specific environment).

My server runs the RHEL 7.4 distribution.

 

Now the upgrade is complete, I notice that that are changes not really 
documented:

 

-  The kamailio-perl-5.0.7-1.el7.x86_64.rpm requires to install the 
mod_perl module that doesn’t exist anymore in RHEL 7. It needs to be installed 
from the EPEL repository

-  The init script for kamailio has been changed from the old method to 
the fully compliant method for system unit for RHEL 7 for example:

 

With the 5.0.1 level we have the “/etc/rc.d/init.d/kamailio”

With the 5.0.7 level we have now the “/usr/lib/systemd/system/kamailio.service”

 

So my questions/comments are :

 

-  Why the mod_perl module is required between 5.0.1 and 5.0.7  
(question posted in the attached message) ?

-  In the previous kamailo init script, I added a condition to start 
MySQL before kamailio by adding this entry in the script : # Required-Start: 
$syslog $network $mysqld

The new script contains the After command :

[Unit]

Description=Kamailio (OpenSER) - the Open Source SIP Server

After=network.target

 

Should I change the After line with this : After=network.target mysql.target to 
have the same condition?

 

In all the cases, some documentation must be changed to provide more details.

 

Thanks in advance for the answers.

 

Cordialement.

Patrick GINHOUX

 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> 
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Questions about changes between 5.0.1 and 5.0.7

2018-08-07 Thread Ginhoux, Patrick

Hi,

 

Following a problem with the kamcmd htable.reload with Kamailio 5.0.1 (see
related thread for this), I have upgraded to the 5.0.7 level (with some
difficulties due to my specific environment).

My server runs the RHEL 7.4 distribution.

 

Now the upgrade is complete, I notice that that are changes not really
documented:

 

-  The kamailio-perl-5.0.7-1.el7.x86_64.rpm requires to install the
mod_perl module that doesn't exist anymore in RHEL 7. It needs to be
installed from the EPEL repository

-  The init script for kamailio has been changed from the old method
to the fully compliant method for system unit for RHEL 7 for example:

 

With the 5.0.1 level we have the "/etc/rc.d/init.d/kamailio"

With the 5.0.7 level we have now the
"/usr/lib/systemd/system/kamailio.service"

 

So my questions/comments are :

 

-  Why the mod_perl module is required between 5.0.1 and 5.0.7
(question posted in the attached message) ?

-  In the previous kamailo init script, I added a condition to start
MySQL before kamailio by adding this entry in the script : # Required-Start:
$syslog $network $mysqld

The new script contains the After command :

[Unit]

Description=Kamailio (OpenSER) - the Open Source SIP Server

After=network.target

 

Should I change the After line with this : After=network.target mysql.target
to have the same condition?

 

In all the cases, some documentation must be changed to provide more
details.

 

Thanks in advance for the answers.

 

Cordialement.

Patrick GINHOUX

 



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

2018-08-03 Thread Ginhoux, Patrick

Unfortunately, I use the perl module in my kamailio.cfg.

So you're correct, I could install the mod_perl from the EPEL project. This
is possible on my test server in my lab.
At the moment, I had collected manually all rpm packages required for 5.0.1
(like Perl or snmp packages), that' was already a huge work.

Now if at each stream there is new dependencies, I would have to solve the
dependencies for other repo like with the EPEL repo.

But in a next step, I have to do the same installation on a customer site on
preimaged server with the following restrictions :
- from this site, I have no access to the internet (That's why, up to new, I
only download the packages I need)
- the preimaged server are RHEL 7.4 server without no required package
removed.

As said, I configured the EPEL repo on my test server and then try to
installed to mod_perl module. I starts ok but fails for other dependencies
(see attached).

So upgrading from Kamailio 5.0.1 to 5.0.7 is not as simple as I expected.

I hope I'm clear in my explanation.

Cordialement.
Patrick GINHOUX 
Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com


-Message d'origine-
De : Henning Westerholt  
Envoyé : vendredi 3 août 2018 08:43
À : Ginhoux, Patrick 
Cc : sr-users@lists.kamailio.org
Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Am Freitag, 3. August 2018, 07:56:28 CEST schrieb Ginhoux, Patrick:
> Instead of installing a new server, I tried to upgrade the one running the
> 5.0.1 level. It has the following packages installed:
> 
> kamailio-perl-5.0.1-1.1.x86_64
> kamailio-5.0.1-1.1.x86_64
> kamailio-mysql-5.0.1-1.1.x86_64
> kamailio-snmpstats-5.0.1-1.1.x86_64
> 
> So I have download the 5.0.7 packages into a separate folder:
> kamailio-rpms_5.0.7
> 
> kamailio-5.0.7-1.el7.x86_64.rpm
> kamailio-mysql-5.0.7-1.el7.x86_64.rpm
> kamailio-perl-5.0.7-1.el7.x86_64.rpm
> kamailio-snmpstats-5.0.7-1.el7.x86_64.rpm
> kamailio-ims-5.0.7-1.el7.x86_64.rpm
> 
> The update command rpm -Uvh --force kamailio* detects a dependency on
the
> mod_perl package :
> 
> warning: kamailio-5.0.7-1.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature,
key
> ID 941fdbdd: NOKEY
> 
> error: Failed dependencies:
> mod_perl is needed by kamailio-perl-5.0.7-1.el7.x86_64
> I try to find this mod_perl package but it does no longer exist for RedHat
> 7. We can find multiple articles referencing this change in RHEL.
> 
> It seems there is an alternative way to get this module in a EPEL
repository
> (https://huntingbears.nl/2013/12/17/no-mod_perl-in-rhel-7-and-centos-7/).
> 
> It is to me a huge work to simply update my current Kamailio to 5.0.7.
> 
> Does this mod_perl change makes sense to you ?
> 
> Have you an idea to get rid of this dependency?

Hello Patrick,

probably a stupid question, but do you actually use the perl module inside 
your kamailio cfg? If not - I would suggest to just remove the 5.0.1 perl 
module, and also not install it for 5.0.7. 

If you need it - the quoted artice states that its actually not difficult to

install mod_perl from the EPEL repository. This looks quite ok: "EPEL is the

high-quality RPM collection for RHEL and CentOS linux, maintened by the
Fedora 
project.".

Best regards,

Henning

-- 
Henning Westerholt
https://skalatan.de/blog/
[root@vm-siprouter74 yum.repos.d]# yum install -y mod_perl
Resolving Dependencies
--> Running transaction check
---> Package mod_perl.x86_64 0:2.0.10-2.el7 will be installed
--> Processing Dependency: httpd-mmn = 20120211x8664 for package: 
mod_perl-2.0.10-2.el7.x86_64
--> Processing Dependency: perl(Linux::Pid) for package: 
mod_perl-2.0.10-2.el7.x86_64
--> Processing Dependency: perl(ExtUtils::MakeMaker) for package: 
mod_perl-2.0.10-2.el7.x86_64
--> Processing Dependency: perl(BSD::Resource) for package: 
mod_perl-2.0.10-2.el7.x86_64
--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: 
mod_perl-2.0.10-2.el7.x86_64
--> Processing Dependency: libapr-1.so.0()(64bit) for package: 
mod_perl-2.0.10-2.el7.x86_64
--> Running transaction check
---> Package apr.x86_64 0:1.4.8-3.el7 will be installed
---> Package apr-util.x86_64 0:1.5.2-6.el7 will be installed
---> Package httpd.x86_64 0:2.4.6-67.el7 will be installed
--> Processing Dependency: httpd-tools = 2.4.6-67.el7 for package: 
httpd-2.4.6-67.el7.x86_64
---> Package perl-BSD-Resource.x86_64 0:1.29.07-1.el7 will be installed
---> Package perl-ExtUtils-MakeMaker.noarch 0:6.68-3.el7 will be installed
--> Processing Dependency: perl(ExtUtils::Install) for package: 
perl-ExtUtils-MakeMaker-6.68-3.el7.noarch
--> Processing Dependency: perl(ExtUtils::Installed) for package: 
perl-ExtUtils-MakeMaker-6.68-3.el7.noarch
--> Processing Dependency: perl(ExtUtils::Manifest) for package: 
perl-ExtUtils-MakeMaker-6.68-3.el7.noarch
--> Pro

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

2018-08-02 Thread Ginhoux, Patrick

Hi Henning,

 

Instead of installing a new server, I tried to upgrade the one running the
5.0.1 level. It has the following packages installed: 

 

kamailio-perl-5.0.1-1.1.x86_64

kamailio-5.0.1-1.1.x86_64

kamailio-mysql-5.0.1-1.1.x86_64

kamailio-snmpstats-5.0.1-1.1.x86_64

 

So I have download the 5.0.7 packages into a separate folder:
kamailio-rpms_5.0.7

 

kamailio-5.0.7-1.el7.x86_64.rpm 

kamailio-mysql-5.0.7-1.el7.x86_64.rpm

kamailio-perl-5.0.7-1.el7.x86_64.rpm

kamailio-snmpstats-5.0.7-1.el7.x86_64.rpm

kamailio-ims-5.0.7-1.el7.x86_64.rpm

 

The update command rpm -Uvh --force kamailio* detects a dependency on the
mod_perl package :

 

warning: kamailio-5.0.7-1.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key
ID 941fdbdd: NOKEY

error: Failed dependencies:

mod_perl is needed by kamailio-perl-5.0.7-1.el7.x86_64

 

I try to find this mod_perl package but it does no longer exist for RedHat
7. We can find multiple articles referencing this change in RHEL.

It seems there is an alternative way to get this module in a EPEL repository
(https://huntingbears.nl/2013/12/17/no-mod_perl-in-rhel-7-and-centos-7/).

 

It is to me a huge work to simply update my current Kamailio to 5.0.7.

 

Does this mod_perl change makes sense to you ? 

Have you an idea to get rid of this dependency?

 

Thank in advance for your suggestion .

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

-Message d'origine-
De : Ginhoux, Patrick 
Envoyé : jeudi 2 août 2018 09:33
À : 'Henning Westerholt' 
Cc : sr-users@lists.kamailio.org
Objet : RE: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Hi Henning,

 

Thanks for your review.

 

As you said, that's strange behavior.

 

So I'm going to upgrade to 5.0.7, the time to set up a server. I'll keep you

posted asap.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 |
<mailto:patrick.ginh...@unisys.com> patrick.ginh...@unisys.com

 

-Message d'origine-

De : Henning Westerholt < <mailto:h...@kamailio.org> h...@kamailio.org> 

Envoyé : jeudi 2 août 2018 09:02

À :  <mailto:sr-users@lists.kamailio.org> sr-users@lists.kamailio.org

Cc : Ginhoux, Patrick < <mailto:patrick.ginh...@fr.unisys.com>
patrick.ginh...@fr.unisys.com>

Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

 

Am Dienstag, 24. Juli 2018, 10:20:01 CEST schrieb Ginhoux, Patrick:

> 

> I run Kamailio 5.0.1 with MariaDB database.

> 

> There is no issue at the initialization, meaning the db is opened by

> kamailio and the hash tables loaded from the db tables.

 

Hello Patrick,

 

this is strange. Normally if it can initialize correctly during startup,

then 

it also should be able to use the database later on. 

 

I did a quick check of the htable module in the repository. There have been

a 

few fixes related to rpc commands and also a bit related to the database in 

the last year. But I did not saw from the git logs anything like you 

described.

 

Nevertheless, you should try to setup the latest 5.0 release (5.0.7) - maybe

 

on a test system and see if the error is also happening there. There should

be 

no changes in database or configuration comparing to 5.0.1.

 

Best regards,

 

Henning

 

> Example:

> 

> # kamcmd htable.dump propertiesHash

> [..]

> 

> But the htable.reload command fails:

> 

> error: 500 - Failed to open htable db connection

> 

> 

> 

> The Kamailio log reports that it can't connect the db :

> 

> DEBUG: ctl [../../core/io_wait.h:380]: io_watch_add(): DBG:

> io_watch_add(0x7f68c74ab300, 10, 3, 0xdc9410), fd_no=1

> 

> DEBUG: ctl [io_listener.c:442]: handle_new_connect(): handle_stream read:

> new connection (1) on /var/run/kamailio//kamailio_ctl

> 

> DEBUG:  [core/sr_module.c:694]: find_mod_export_record():

> find_export_record: found  in module db_mysql

> [/usr/lib64/kamailio/modules/db_mysql.so]

> 

> DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

> 

> DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f68cc354c10 not

found

> in pool

> 

> DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening

> connection: mysql://:@/siprouter

> 

> ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver

error:

> Can't connect to local MySQL server through socket

> '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

> 

> ERROR:  [db.c:318]: db_do_init2(): could not add connection to the

> pool

> 

> ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the

> database

> 

> 

> 

> My local db is located at /myqdata/mysiprdb/data where is the

mysiprdb.sock

> file. But the log shows that Kamailio is looking for

>

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

2018-08-02 Thread Ginhoux, Patrick

Hi Henning,

Thanks for your review.

As you said, that's strange behavior.

So I'm going to upgrade to 5.0.7, the time to set up a server. I'll keep you
posted asap.

Cordialement.
Patrick GINHOUX 
Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

-Message d'origine-
De : Henning Westerholt  
Envoyé : jeudi 2 août 2018 09:02
À : sr-users@lists.kamailio.org
Cc : Ginhoux, Patrick 
Objet : Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Am Dienstag, 24. Juli 2018, 10:20:01 CEST schrieb Ginhoux, Patrick:
> 
> I run Kamailio 5.0.1 with MariaDB database.
> 
> There is no issue at the initialization, meaning the db is opened by
> kamailio and the hash tables loaded from the db tables.

Hello Patrick,

this is strange. Normally if it can initialize correctly during startup,
then 
it also should be able to use the database later on. 

I did a quick check of the htable module in the repository. There have been
a 
few fixes related to rpc commands and also a bit related to the database in 
the last year. But I did not saw from the git logs anything like you 
described.

Nevertheless, you should try to setup the latest 5.0 release (5.0.7) - maybe

on a test system and see if the error is also happening there. There should
be 
no changes in database or configuration comparing to 5.0.1.

Best regards,

Henning

> Example:
> 
> # kamcmd htable.dump propertiesHash
> [..]
> 
> But the htable.reload command fails:
> 
> error: 500 - Failed to open htable db connection
> 
> 
> 
> The Kamailio log reports that it can't connect the db :
> 
> DEBUG: ctl [../../core/io_wait.h:380]: io_watch_add(): DBG:
> io_watch_add(0x7f68c74ab300, 10, 3, 0xdc9410), fd_no=1
> 
> DEBUG: ctl [io_listener.c:442]: handle_new_connect(): handle_stream read:
> new connection (1) on /var/run/kamailio//kamailio_ctl
> 
> DEBUG:  [core/sr_module.c:694]: find_mod_export_record():
> find_export_record: found  in module db_mysql
> [/usr/lib64/kamailio/modules/db_mysql.so]
> 
> DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql
> 
> DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f68cc354c10 not
found
> in pool
> 
> DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening
> connection: mysql://:@/siprouter
> 
> ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver
error:
> Can't connect to local MySQL server through socket
> '/var/lib/mysql/mysql.sock' (2 "No such file or directory")
> 
> ERROR:  [db.c:318]: db_do_init2(): could not add connection to the
> pool
> 
> ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the
> database
> 
> 
> 
> My local db is located at /myqdata/mysiprdb/data where is the
mysiprdb.sock
> file. But the log shows that Kamailio is looking for
> /var/lib/mysql/mysql.sock.
> 
> 
> 
> Does this error make sense to you ?
> 
> Is it possible to fix this problem by configuration in Kamailio ?
> 
> 
> 
> My kamailio.cfg script contains :
> 
> 
> 
> # - htable
> 
> modparam("htable", "db_url", "mysql://[kamailio]/siprouter")
> 
> 
> 
> modparam("htable", "fetch_rows", 1000)
> 
> modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")
> 
> modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;")
> 
> modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;")
> 
> modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;")
> 
> 
> 
> In the /myqdata/mysiprdb/data/my.cnf, I added the following entries for
> Kamailio:
> 
> [kamailio]
> 
> socket = /myqdata/mysiprdb/data/mysiprdb.sock
> 
> user = siprouter
> 
> password = ##
> 
> default-character-set = utf8
> 
> 
> 
> Thanks all for help.
> 
> 
> 
> Cordialement.
> 
> Patrick GINHOUX


-- 
Henning Westerholt
https://skalatan.de/blog/


smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

2018-08-02 Thread Ginhoux, Patrick

Does anybody encounter a problem with the kamcmd htable.reload
propertiesHash command ?

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : sr-users  De la part de Ginhoux,
Patrick
Envoyé : mardi 24 juillet 2018 10:20
À : Kamailio (SER) - Users Mailing List 
Objet : [SR-Users] kamcmd htable.reload propertiesHash problem

 

Hi,

 

I run Kamailio 5.0.1 with MariaDB database.

 

There is no issue at the initialization, meaning the db is opened by
kamailio and the hash tables loaded from the db tables.

Example:

# kamcmd htable.dump propertiesHash

{

entry: 1

size: 1

slot: {

item: {

name: cfg.env

 

But the htable.reload command fails:

error: 500 - Failed to open htable db connection

 

The Kamailio log reports that it cant connect the db :

DEBUG: ctl [../../core/io_wait.h:380]: io_watch_add(): DBG:
io_watch_add(0x7f68c74ab300, 10, 3, 0xdc9410), fd_no=1

DEBUG: ctl [io_listener.c:442]: handle_new_connect(): handle_stream read:
new connection (1) on /var/run/kamailio//kamailio_ctl

DEBUG:  [core/sr_module.c:694]: find_mod_export_record():
find_export_record: found  in module db_mysql
[/usr/lib64/kamailio/modules/db_mysql.so]

DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f68cc354c10 not found
in pool

DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening
connection: mysql://:@/siprouter

ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error:
Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2 "No such file or directory")

ERROR:  [db.c:318]: db_do_init2(): could not add connection to the
pool

ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the
database

 

My local db is located at /myqdata/mysiprdb/data where is the mysiprdb.sock
file. But the log shows that Kamailio is looking for
/var/lib/mysql/mysql.sock.

 

Does this error make sense to you ?

Is it possible to fix this problem by configuration in Kamailio ?

 

My kamailio.cfg script contains :

 

# - htable

modparam("htable", "db_url", "mysql://[kamailio]/siprouter")

 

modparam("htable", "fetch_rows", 1000)

modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")

modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;")

modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;")

modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;") 

 

In the /myqdata/mysiprdb/data/my.cnf, I added the following entries for
Kamailio:

[kamailio]

socket = /myqdata/mysiprdb/data/mysiprdb.sock

user = siprouter

password = ##

default-character-set = utf8

 

Thanks all for help.

 

Cordialement.

Patrick GINHOUX

 



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] kamcmd htable.reload propertiesHash problem

2018-07-24 Thread Ginhoux, Patrick

Hi,

 

I run Kamailio 5.0.1 with MariaDB database.

 

There is no issue at the initialization, meaning the db is opened by
kamailio and the hash tables loaded from the db tables.

Example:

# kamcmd htable.dump propertiesHash

{

entry: 1

size: 1

slot: {

item: {

name: cfg.env

 

But the htable.reload command fails:

error: 500 - Failed to open htable db connection

 

The Kamailio log reports that it can't connect the db :

DEBUG: ctl [../../core/io_wait.h:380]: io_watch_add(): DBG:
io_watch_add(0x7f68c74ab300, 10, 3, 0xdc9410), fd_no=1

DEBUG: ctl [io_listener.c:442]: handle_new_connect(): handle_stream read:
new connection (1) on /var/run/kamailio//kamailio_ctl

DEBUG:  [core/sr_module.c:694]: find_mod_export_record():
find_export_record: found  in module db_mysql
[/usr/lib64/kamailio/modules/db_mysql.so]

DEBUG:  [db.c:209]: db_bind_mod(): using db bind api for db_mysql

DEBUG:  [db.c:314]: db_do_init2(): connection 0x7f68cc354c10 not found
in pool

DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening
connection: mysql://:@/siprouter

ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error:
Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2 "No such file or directory")

ERROR:  [db.c:318]: db_do_init2(): could not add connection to the
pool

ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the
database

 

My local db is located at /myqdata/mysiprdb/data where is the mysiprdb.sock
file. But the log shows that Kamailio is looking for
/var/lib/mysql/mysql.sock.

 

Does this error make sense to you ?

Is it possible to fix this problem by configuration in Kamailio ?

 

My kamailio.cfg script contains :

 

# - htable

modparam("htable", "db_url", "mysql://[kamailio]/siprouter")

 

modparam("htable", "fetch_rows", 1000)

modparam("htable", "htable", "mbxrangeHash=>size=4;dbtable=mbxrange;")

modparam("htable", "htable", "abpqHash=>size=12;dbtable=abpq;")

modparam("htable", "htable", "zabpqHash=>size=12;dbtable=zabpq;")

modparam("htable", "htable", "propertiesHash=>size=4;dbtable=properties;") 

 

In the /myqdata/mysiprdb/data/my.cnf, I added the following entries for
Kamailio:

[kamailio]

socket = /myqdata/mysiprdb/data/mysiprdb.sock

user = siprouter

password = ##

default-character-set = utf8

 

Thanks all for help.

 

Cordialement.

Patrick GINHOUX

 



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Question on the new Kamailio v5.x Releases

2018-06-27 Thread Ginhoux, Patrick

Hi,

 

I always read your email regarding new stable releases.

 

I am currently working on a project upgrade of multiples servers to the most
recent OS (Windows, RedHat) and middleware. 

In this project, I have upgraded SIP Proxies server running on old version
of Kamailio, to the 5.0.1 release (over RedHat 7.4).

Effort to make that upgrade and tests have been done with success in the
last months.

 

So considering to upgrade to the 5.0.7 or 5.1.4 would be a subsequent work I
need to evaluate.

I could read all the release notes, but it is also a big challenge to
determine if fixes are interesting for me.

 

Based on your experience, is there particular cases, fixed in the new
release I need to pay attention?

 

Any comments are welcome.

 

Regards

Patrick GINHOUX



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Upgrade issue from 4.4.7 to 5.1.3

2018-06-01 Thread Ginhoux, Patrick

Hi,

Do you update your MODULEPATH define like this :  !!define MODULEPATH 
"/usr/lib64/kamailio/modules/" ?

Cordialement.

Patrick 
-Message d'origine-
De : sr-users  De la part de Kevin Greene
Envoyé : vendredi 1 juin 2018 02:20
À : sr-users@lists.kamailio.org
Objet : [SR-Users] Upgrade issue from 4.4.7 to 5.1.3

Hello List users:

I am trying to upgrade to the current version of Kamailio from the older 
4.4 version to the current version. The 4.4 is functional but there are 
some features of 5.1 that we wanted to test with.

It seems that my version of Linux (RHEL 6.9 or Oracle 6.9) has an issue 
with a library file.

Any help would be useful.

Thank you.

Kevin

Notes:

I used the "yum update kamailio" function.

(edited for clarity - it showed a long list of modules to be updated)

"--> Finished Dependency Resolution
Error: Package: kamailio-http-utils-4.4.7-1.1.x86_64 
(@home_kamailio_v4.4.x-rpms)
Requires: kamailio = 4.4.7
Removing: kamailio-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms)
kamailio = 4.4.7-1.1
Updated By: kamailio-5.1.3-1.el6.x86_64 
(home_kamailio_v5.1.x-rpms)
kamailio = 5.1.3-1.el6
Error: Package: kamailio-http-utils-4.4.7-1.1.x86_64 
(@home_kamailio_v4.4.x-rpms)
Requires: libkmi.so.1()(64bit)
Removing: kamailio-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms)
libkmi.so.1()(64bit)
Updated By: kamailio-5.1.3-1.el6.x86_64 
(home_kamailio_v5.1.x-rpms)
Not found
Error: Package: kamailio-xml-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms)
Requires: kamailio = 4.4.7
Removing: kamailio-4.4.7-1.1.x86_64 (@home_kamailio_v4.4.x-rpms)
kamailio = 4.4.7-1.1
Updated By: kamailio-5.1.3-1.el6.x86_64 
(home_kamailio_v5.1.x-rpms)
kamailio = 5.1.3-1.el6
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest"

However the "missing" library is there in /usr/lib64.

[root@sipserver tmp]# find / -name libkmi.so.1
/usr/lib64/kamailio/libkmi.so.1
/usr/lib64/libkmi.so.1
/lib64/libkmi.so.1

To provide additional help, See:

[root@sipserver tmp]# kamailio -version
version: kamailio 4.4.7 (x86_64/linux) 35d8ab
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, 
USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, 
F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, 
FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 35d8ab
compiled on 15:38:14 Feb 26 2018 with gcc 4.4.7






___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Link problem between kamailio and MariaDB

2018-05-28 Thread Ginhoux, Patrick

Hi Henning,

 

Thanks for your answer.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : Henning Westerholt <h...@kamailio.org> 
Envoyé : jeudi 24 mai 2018 08:40
À : sr-users@lists.kamailio.org
Cc : Ginhoux, Patrick <patrick.ginh...@fr.unisys.com>
Objet : Re: [SR-Users] Link problem between kamailio and MariaDB

 

Am Mittwoch, 23. Mai 2018, 15:34:41 CEST schrieb Ginhoux, Patrick:

> At the moment, I'm trying to replace MySQL by MariaDB on my Kamailio
server

> (5.0.1) . In previous post I have been told that Kamailio supports MariaDB

> and there is no special module to load.

> 

> This work is done on a new server running RHEL 7.4 and MariaDB 10.2.14
that

> is installed under /opt/mysql/na/10.2.14 folder.

> 

> I encounter different problem:

> 

> - Without changing anything in the kamailio script, kamailio failed

> to find the libmysqlclient.so.18 library.

> 

> - So I thought that I could get rid of the above error by changing

> the MODULEPATH in the Kamailio-local.cfg as follows :

> 

> MODULEPATH="/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/"

> 

> But with this, I get 2 problem:

> [..]

 

Hello Patrick,

 

the Kamailio module path is not related to the system library path. 

 

So the correct configuration is to point in the Kamailio cfg the module path
to the installed location for the Kamailio modules, not include the system
library path here.

 

If you have an issue that the db_mysql module can't find the libmysql system
library, you can either fix the system library search path or use a symlink
approach as you described in the earlier post as well.

 

Best regards,

 

Henning



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Link problem between kamailio and MariaDB

2018-05-23 Thread Ginhoux, Patrick

Hi,

 

At the moment, I'm trying to replace MySQL by MariaDB on my Kamailio server
(5.0.1) . In  previous post I have been told that Kamailio supports MariaDB
and there is no special module to load.

 

This work is done on a new server running RHEL 7.4 and MariaDB 10.2.14 that
is installed under /opt/mysql/na/10.2.14 folder.

 

I encounter different problem:

 

-  Without changing anything in the kamailio script, kamailio failed
to find the libmysqlclient.so.18 library.

-  So I thought that I could get rid of the above error by changing
the MODULEPATH in the Kamailio-local.cfg as follows :

MODULEPATH="/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/"

But with this, I get 2 problem:

The kamailio.log that was written in a /opt/log/Kamailio folder is no longer
updated.

I can only find the errors in the /var/log/messages file:

May 23 11:19:19 vm-siprouter74 systemd: Starting SYSV: Kamailio is a fast,
reliable and flexible SIP Server

May 23 11:19:19 vm-siprouter74 kamailio: Not starting : invalid
configuration file!

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID
[DEFINE_LOG_FACILITY] value [LOG_LOCAL0]

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID [LOCAL_LISTEN]
value [udp:129.227.82.109:5060]

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID
[LOCAL_LISTEN_2] value [udp:127.0.0.1:5060]

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID [MODULEPATH]
value ["/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/"]

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.y:1632]: yyparse(): loading modules under
/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.y:1613]: yyparse(): loading module db_mysql.so

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/sr_module.c:575]: load_module(): trying to load


May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) ERROR: 
[core/sr_module.c:582]: load_module(): could not open module
: libmysqlclient.so.18: cannot open
shared object file: No such file or directory

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) CRITICAL: 
[core/cfg.y:3401]: yyerror_at(): parse error in config file
//etc/kamailio/kamailio.cfg, line 191, column 12-24: failed to load module

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/cfg.y:1613]: yyparse(): loading module jsonrpcs.so

May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: 
[core/sr_module.c:575]: load_module(): trying to load


 

To work around the problem we have created 2 symbol links:

<<< ln -s /opt/mysql/na/10.2.14/lib64/libmysqlclient.so.18.0.0
/usr/lib64/libmysqlclient.so.18 >>> the libmysqlclient error

<<< ln -s /myqdata/mysiprdb/data/my.cnf /etc/my.cnf >>> to fix the issue to
open the db

 

It seems that kamailio is always looking for the my.cnf in the /etc/
directory.

 

My concern are to share this job with people who have much more experience
with Kamailio.

 

I would like to know 

-  If the different workaround (ln) makes sense to you or is there
better change to do

-  How to explain the logging issue when changing the modulepath
variable

-  Is it true that kamailio is always looking for the my.cnf in the
/etc/ directory?

 

Any thoughts are welcome.

 

Thanks in advance.

 

Cordialement.

Patrick GINHOUX



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Use of MariaDB to replace MySQL

2018-04-23 Thread Ginhoux, Patrick

Hi Charles,

 

Thanks for the answer.

 

So that this makes me confident to migrate soon.

 

Cordialement.

Patrick GINHOUX 

Unisys | +33 1 46 69 52 12 | +33 6 60 32 24 74 | patrick.ginh...@unisys.com

 

De : sr-users <sr-users-boun...@lists.kamailio.org> De la part de Charles Chance
Envoyé : samedi 21 avril 2018 11:18
À : Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Objet : Re: [SR-Users] Use of MariaDB to replace MySQL

 

Hello,

 

MariaDB is a drop-in replacement, so simply continue using the db_mysql module 
as you are now.

 

Cheers,

 

Charles

 

On Sat, 21 Apr 2018 at 07:53, Ginhoux, Patrick <patrick.ginh...@fr.unisys.com 
<mailto:patrick.ginh...@fr.unisys.com> > wrote:

Hi,

 

Currently, my Kamailio proxy uses a MySql DB to get configuration data.  We 
have a plan to migrate MySQL to MariaDB.

 

Is  there MariaDB modules with Kamailio ?

 

Thanks in advance for your answer.

 

P. Ginhoux

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> 
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 

Charles Chance
Managing Director

 

t. 0330 120 1200m. 07932 063 891

 

Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered 
office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham 
Science Park, Birmingham B7 4BB.



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Use of MariaDB to replace MySQL

2018-04-21 Thread Ginhoux, Patrick

Hi,

 

Currently, my Kamailio proxy uses a MySql DB to get configuration data.  We
have a plan to migrate MySQL to MariaDB.

 

Is  there MariaDB modules with Kamailio ?

 

Thanks in advance for your answer.

 

P. Ginhoux



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Perl module missing in kamailio 5.0.3

2017-09-29 Thread Ginhoux, Patrick

Hi,

 

Now I get the Perl package, I was going to upgrade to 5.0.3. I discovered that 
this new Kamailio level 5.0.3 requires to install the 
“kamailio-ims-5.0.3-10.el7.x86_64.rpm”.

 

The only packages I need for my installation are :

kamailio-5.0.3-10.el7.x86_64.rpm

kamailio-ims-5.0.3-10.el7.x86_64.rpm

kamailio-mysql-5.0.3-10.el7.x86_64.rpm

kamailio-perl-5.0.3-10.el7.x86_64.rpm

kamailio-snmpstats-5.0.3-10.el7.x86_64.rpm

 

Doing this upgrade manually, I encounter a dependency issue between the main 
kamailio rpm and the ims module.

 

If I start to install the mail rpm, I get an depency error with an ims lib:

 

[root@vm-vse02-siprouter2 Package-kamailio-5.0.3]# rpm -Uvh 
kamailio-5.0.3-10.el7.x86_64.rpm

warning: kamailio-5.0.3-10.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 
941fdbdd: NOKEY

error: Failed dependencies:

libkamailio_ims.so.0()(64bit) is needed by kamailio-5.0.3-10.el7.x86_64

kamailio-mysql < 5.0.3 conflicts with kamailio-5.0.3-10.el7.x86_64

kamailio-perl < 5.0.3 conflicts with kamailio-5.0.3-10.el7.x86_64

kamailio-snmpstats < 5.0.3 conflicts with kamailio-5.0.3-10.el7.x86_64

kamailio = 5.0.1 is needed by (installed) 
kamailio-mysql-5.0.1-1.1.x86_64

kamailio = 5.0.1 is needed by (installed) kamailio-perl-5.0.1-1.1.x86_64

kamailio = 5.0.1 is needed by (installed) 
kamailio-snmpstats-5.0.1-1.1.x86_64

 

if I try to install first the ims rpm I get another dependency problem :

 

[root@vm-vse02-Package-kamailio-5.0.3]# rpm -Uvh 
kamailio-ims-5.0.3-10.el7.x86_64.rpm

warning: kamailio-ims-5.0.3-10.el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, 
key ID 941fdbdd: NOKEY

error: Failed dependencies:

kamailio = 5.0.3 is needed by kamailio-ims-5.0.3-10.el7.x86_64

 

So I have created a local repository for yum to do this installation easily but 
the installation failed due to mod_perl is missing : 

 

]# yum install kamailio

Local-kamailio  
  | 2.9 kB  00:00:00

Local-kamailio/primary_db   
  | 6.4 kB  00:00:00

Resolving Dependencies

--> Running transaction check

---> Package kamailio.x86_64 0:5.0.1-1.1 will be updated

--> Processing Dependency: kamailio = 5.0.1 for package: 
kamailio-snmpstats-5.0.1-1.1.x86_64

--> Processing Dependency: kamailio = 5.0.1 for package: 
kamailio-mysql-5.0.1-1.1.x86_64

--> Processing Dependency: kamailio = 5.0.1 for package: 
kamailio-perl-5.0.1-1.1.x86_64

---> Package kamailio.x86_64 0:5.0.3-10.el7 will be an update

--> Processing Dependency: libkamailio_ims.so.0()(64bit) for package: 
kamailio-5.0.3-10.el7.x86_64

--> Running transaction check

---> Package kamailio-ims.x86_64 0:5.0.3-10.el7 will be installed

---> Package kamailio-mysql.x86_64 0:5.0.1-1.1 will be updated

---> Package kamailio-mysql.x86_64 0:5.0.3-10.el7 will be an update

---> Package kamailio-perl.x86_64 0:5.0.1-1.1 will be updated

---> Package kamailio-perl.x86_64 0:5.0.3-10.el7 will be an update

--> Processing Dependency: mod_perl for package: 
kamailio-perl-5.0.3-10.el7.x86_64

---> Package kamailio-snmpstats.x86_64 0:5.0.1-1.1 will be updated

---> Package kamailio-snmpstats.x86_64 0:5.0.3-10.el7 will be an update

--> Finished Dependency Resolution

Error: Package: kamailio-perl-5.0.3-10.el7.x86_64 (Local-kamailio)

   Requires: mod_perl

You could try using --skip-broken to work around the problem

You could try running: rpm -Va --nofiles --nodigest

 

It seems that the mod_perl is missing in the kamailio-perl-5.0.3 package.

 

Do you have any idea about the problems I encounter at the different try to 
upgrade ?

 

Thanks in advance for answers.

 

Cordialement

Patrick GINHOUX

 

PS : Could you please let me know if sending issue to the above email is 
correct ?

 

De : Ginhoux, Patrick 
Envoyé : mercredi 20 septembre 2017 20:27
À : Kamailio users (sr-users@lists.kamailio.org) <sr-users@lists.kamailio.org>
Objet : RE: [SR-Users] Perl module missing in kamailio 5.0.3

 

Hi Sergey,

 

Great thanks for your action.

 

I really appreciate the help provided and see that they are always people that 
answer to user’s requests. 

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de Sergey 
Safarov
Envoyé : mercredi 20 septembre 2017 14:13
À : Kamailio users (sr-users@lists.kamailio.org 
<mailto:sr-users@lists.kamailio.org> ) <sr-users@lists.kamailio.org 
<mailto:sr-users@lists.kamailio.org> >
Objet : Re: [SR-Users] Perl module missing in kamailio 5.0.3

 

I pushed changes to RHEL repo builder.

After 20 min you download packages with perl module

 

Sergey

 

ср, 20 сент. 2017 г. в 12:03, Ginhoux, Patrick <patrick

Re: [SR-Users] Perl module missing in kamailio 5.0.3

2017-09-20 Thread Ginhoux, Patrick

Hi Sergey,

 

Great thanks for your action.

 

I really appreciate the help provided and see that they are always people that 
answer to user’s requests. 

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de Sergey 
Safarov
Envoyé : mercredi 20 septembre 2017 14:13
À : Kamailio users (sr-users@lists.kamailio.org) <sr-users@lists.kamailio.org>
Objet : Re: [SR-Users] Perl module missing in kamailio 5.0.3

 

I pushed changes to RHEL repo builder.

After 20 min you download packages with perl module

 

Sergey

 

ср, 20 сент. 2017 г. в 12:03, Ginhoux, Patrick <patrick.ginh...@fr.unisys.com 
<mailto:patrick.ginh...@fr.unisys.com> >:

Hi,

 

I’m thinking to upgrade my kamailio 5.0.1 running on a Rhel 7.1 server to 5.0.3 
.

 

Looking at the repository for Rhel7 to download the rpm, I don’t find the perl 
rpm.

 

For 5.0.1, it is kamailio-perl-5.0.1-1.1.x86_64.rpm.

 

Can you help to get it for 5.0.3 ?

 

Thanks in avance.

 

Cordialement

Patrick GINHOUX

 

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org <mailto:sr-users@lists.kamailio.org> 
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Perl module missing in kamailio 5.0.3

2017-09-20 Thread Ginhoux, Patrick

Hi,

 

I'm thinking to upgrade my kamailio 5.0.1 running on a Rhel 7.1 server to
5.0.3 .

 

Looking at the repository for Rhel7 to download the rpm, I don't find the
perl rpm.

 

For 5.0.1, it is kamailio-perl-5.0.1-1.1.x86_64.rpm.

 

Can you help to get it for 5.0.3 ?

 

Thanks in avance.

 

Cordialement

Patrick GINHOUX

 



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] cpl.load

2017-06-21 Thread Ginhoux, Patrick

Hi,

 

This may help : 
http://www.kamailio.org/docs/modules/5.0.x/modules/cplc.html#cpl.r.load 

 

5. RPC Commands

5.1. cpl.load

For the given user, loads the XML cpl file, compiles it into binary format and 
stores both format into database. 

Name: cpl.load 

Parameters:

· username : name of the user

· cpl_filename: file name 

RPC Command format: 

...

kamcmd cpl.load username cpl_filename

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de 
frédéric Gaisnon
Envoyé : mercredi 21 juin 2017 16:17
À : sr-users@lists.kamailio.org
Objet : [SR-Users] cpl.load

 

Hi,

 

In latest kamailio version "cpl.load" command is obsolete. What is the 
procedure to import CPL into mysql database?

 

Regards,

 

Frédéric Gaisnon

 



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Cannot get service to start

2017-04-28 Thread Ginhoux, Patrick

Hi Stephen,

 

I had similar issues fix by changes in the kamailio.cfg and kamctlrc files, but 
also in the Kamailio rpm as well recently fixed. Are you using the latest 
Kamailio 5.0.1 release?

 

If so please review you config file as I think your problem is related to such 
entries:

 

In my Kamailio.cfg I have the following :

 

!!define DEFINE_FIFO_NAME "/var/run/kamailio/kamailio_rpc_fifo"

 

loadmodule "jsonrpcs.so"

 

modparam("jsonrpcs", "pretty_format", 1)

modparam("jsonrpcs", "transport", 2)

modparam("jsonrpcs", "fifo_name", DEFINE_FIFO_NAME)

modparam("jsonrpcs", "fifo_mode", 0755)

modparam("jsonrpcs", "fifo_group", "kamailio")

modparam("jsonrpcs", "fifo_user", "kamailio")

 

you should have also in the kamctlrc file this enty that matches the one in the 
Kamailio.cfg :

 

## path to FIFO file for engine RPCFIFO

# RPCFIFOPATH="/var/run/kamailio/kamailio_rpc_fifo"

 

In the latest 5.0.1, the Kamailio script has been change to handle the rights 
on the /var/run/Kamailio folder.

 

I hope this helps.

 

Cordialement

Patrick GINHOUX

 

De : sr-users [mailto:sr-users-boun...@lists.kamailio.org] De la part de 
Stephen Tyers
Envoyé : vendredi 28 avril 2017 13:31
À : sr-users@lists.kamailio.org
Objet : [SR-Users] Cannot get service to start

 

Hi Apologies,

 

I was a bit hasty in my previous email, I forgot to run the Chown command

 

I still can’t get the service to start and I’m getting the below error. I’ve 
gone through all the steps multiple times, please help.

 

/etc/init.d/kamailio start

[] Starting kamailio (via systemctl): kamailio.serviceFailed to start 
kamailio.service: Unit kamailio.service failed to load: No such file or 
directory.

 failed!

 

Kind regards

Stephen tyers



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Mails received twice in my Inbox

Re: [SR-Users] Mails received twice in my Inbox

[SR-Users] Mails received twice in my Inbox

Re: [SR-Users] How to not write logs to journald with kamailio

Re: [SR-Users] How to not write logs to journald with kamailio

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

Re: [SR-Users] Can't connect to local MySQL server (13 "Permission denied")

[SR-Users] Can't connect to local MySQL server (13 "Permission denied")

Re: [SR-Users] Fail to reload htable

Re: [SR-Users] Fail to reload htable

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

Re: [SR-Users] Questions about changes between 5.0.1 and 5.0.7

[SR-Users] Questions about changes between 5.0.1 and 5.0.7

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

Re: [SR-Users] kamcmd htable.reload propertiesHash problem

[SR-Users] kamcmd htable.reload propertiesHash problem

[SR-Users] Question on the new Kamailio v5.x Releases

Re: [SR-Users] Upgrade issue from 4.4.7 to 5.1.3

Re: [SR-Users] Link problem between kamailio and MariaDB

[SR-Users] Link problem between kamailio and MariaDB

Re: [SR-Users] Use of MariaDB to replace MySQL

[SR-Users] Use of MariaDB to replace MySQL

Re: [SR-Users] Perl module missing in kamailio 5.0.3

Re: [SR-Users] Perl module missing in kamailio 5.0.3

[SR-Users] Perl module missing in kamailio 5.0.3

Re: [SR-Users] cpl.load

Re: [SR-Users] Cannot get service to start

33 matches

Site Navigation

Mail list logo

Footer information