Module: kamailio
Branch: master
Commit: 8c4d2ca3dc6eb38ec3dd60e704aa39d65a9032b5
URL: https://github.com/kamailio/kamailio/commit/8c4d2ca3dc6eb38ec3dd60e704aa39d…
Author: Luis Martin Gil <martingil.luis(a)gmail.com>
Committer: Luis Martin Gil <martingil.luis(a)gmail.com>
Date: 2016-06-10T12:31:59+02:00
dispatcher: docs updated missing /section
---
Modified: modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/8c4d2ca3dc6eb38ec3dd60e704aa39d…
Patch: https://github.com/kamailio/kamailio/commit/8c4d2ca3dc6eb38ec3dd60e704aa39d…
---
diff --git a/modules/dispatcher/doc/dispatcher_admin.xml b/modules/dispatcher/doc/dispatcher_admin.xml
index f7e0d3e..c10b502 100644
--- a/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/modules/dispatcher/doc/dispatcher_admin.xml
@@ -1365,6 +1365,7 @@ onreply_route {
This function can be used from ANY_ROUTE.
</para>
</section>
+ </section>
<section>
<title>MI Commands</title>
Module: kamailio
Branch: master
Commit: 7287da30d4c4129353e62477fb8de049ab94bbd9
URL: https://github.com/kamailio/kamailio/commit/7287da30d4c4129353e62477fb8de04…
Author: Luis Martin Gil <martingil.luis(a)gmail.com>
Committer: Luis Martin Gil <martingil.luis(a)gmail.com>
Date: 2016-06-10T08:41:41+02:00
dispatcher: ds_reload added using from ANY_ROUTE, removed algorithm 10
---
Modified: modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/7287da30d4c4129353e62477fb8de04…
Patch: https://github.com/kamailio/kamailio/commit/7287da30d4c4129353e62477fb8de04…
---
diff --git a/modules/dispatcher/doc/dispatcher_admin.xml b/modules/dispatcher/doc/dispatcher_admin.xml
index 9bd6cc8..f7e0d3e 100644
--- a/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/modules/dispatcher/doc/dispatcher_admin.xml
@@ -1355,15 +1355,15 @@ onreply_route {
<function moreinfo="none">ds_reload()</function>
</title>
<para>
- Reloads the groups and included destinations. The command is
- disabled for call load based dispatching (algorithm 10) since
- removal of destinations may leave the list of active
- calls with broken references.
+ Reloads the groups and included destinations.
</para>
<para>
Name: <emphasis>ds_reload</emphasis>
</para>
<para>Parameters: <emphasis>none</emphasis></para>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
</section>
<section>
Module: kamailio
Branch: master
Commit: 8a724a70859f68431094acab2a8f9ce000bbd89b
URL: https://github.com/kamailio/kamailio/commit/8a724a70859f68431094acab2a8f9ce…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2016-06-13T12:50:04+02:00
kamdbctl: more error help for missing .pgpass file
---
Modified: utils/kamctl/kamdbctl.pgsql
---
Diff: https://github.com/kamailio/kamailio/commit/8a724a70859f68431094acab2a8f9ce…
Patch: https://github.com/kamailio/kamailio/commit/8a724a70859f68431094acab2a8f9ce…
---
diff --git a/utils/kamctl/kamdbctl.pgsql b/utils/kamctl/kamdbctl.pgsql
index d6452ba..cf3309c 100644
--- a/utils/kamctl/kamdbctl.pgsql
+++ b/utils/kamctl/kamdbctl.pgsql
@@ -43,8 +43,10 @@ fi
if [ -z "$DBROOTUSER" ]; then
DBROOTUSER="postgres"
if [ ! -r ~/.pgpass ]; then
- merr "~/.pgpass does not exist, please create this file and support proper credentials for user postgres."
+ merr "~/.pgpass does not exist"
+ merr "create this file and add proper credentials for user postgres"
merr "Note: you need at least postgresql>= 7.3"
+ merr "Hint: .pgpass hostname must match DBHOST"
exit 1
fi
fi
Module: kamailio
Branch: master
Commit: 631b69c43ffccbcecc3f43c3ebe4e614fe5f105d
URL: https://github.com/kamailio/kamailio/commit/631b69c43ffccbcecc3f43c3ebe4e61…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2016-06-13T12:33:28+02:00
kamdbct: fixed typo in pgpass name
---
Modified: utils/kamctl/kamdbctl.pgsql
---
Diff: https://github.com/kamailio/kamailio/commit/631b69c43ffccbcecc3f43c3ebe4e61…
Patch: https://github.com/kamailio/kamailio/commit/631b69c43ffccbcecc3f43c3ebe4e61…
---
diff --git a/utils/kamctl/kamdbctl.pgsql b/utils/kamctl/kamdbctl.pgsql
index d8250f6..d6452ba 100644
--- a/utils/kamctl/kamdbctl.pgsql
+++ b/utils/kamctl/kamdbctl.pgsql
@@ -43,7 +43,7 @@ fi
if [ -z "$DBROOTUSER" ]; then
DBROOTUSER="postgres"
if [ ! -r ~/.pgpass ]; then
- merr "~./pgpass does not exist, please create this file and support proper credentials for user postgres."
+ merr "~/.pgpass does not exist, please create this file and support proper credentials for user postgres."
merr "Note: you need at least postgresql>= 7.3"
exit 1
fi
Hi,
We have XCAP + RLS based presence setup which seems to work perfectly fine
in our dev environment, however same setup in identical production
environment gives no presence for contact list. When we do RLS subscribe,
we receive initial Notify with full contact list retrieved from XCAP
backend but aggregated presence Notify either does not come at all (most of
the time) or it comes too late (sometime and take over 3-5 minutes).
We see following error in syslogs,
--
ERROR: db_mysql [km_dbase.c:129]: db_mysql_submit_query(): ERROR: driver
error on query: Deadlock found when trying to get lock; try restarting
transaction (1213)
ERROR: <core> [db_query.c:386]: db_do_replace(): error while submitting
query
ERROR: rls [resource_notify.c:808]: rls_handle_notify(): in sql replace
--
This is quite strange since we are using db_mode = 0 in all presence
related modules e.g. presence, presence_xml, pua and rls. So ideally the
entire presence should be managed in in-memory hash tables and there should
be no DB query, right?
Tracing mysql db scoket we identified at lease following presence tables
are accessed,
- pua
- presentity
- watchers
- rls_watchers
- rls_presentity
The presence related tables are accessed / updated by both dev and
production setups but mysql deadlock appears only on production. The only
notice-able different between our dev and production setup is that on
production we have more then 25% users in contact list online (20-30 out of
80 users in contact list) while on dev setup we have too few online (5-10
out of 60 users in contact list).
So my question is,
1. What is the purpose of db_mode = 0 if presence setup is going to use db
tables any way?
2. What could be the possible cause of MySQL deadlock?
3. Is this deadlock the only possible problem for receiving no aggregate
notify at all or there may be some other reason(s)?
How can i debug these issues? These are happening ONLY in production
environment and every attempt to reproduce them in dev environment has
failed so far. :(
Platform: Debian 7.x 32bit on KVM.
Version: Kamailio v4.4.1 rev.12b048
Thank you.
Hi!
I noticed that the link to the bug tracker was wrong in our Docbook XML entities and re-generated all READMEs.
To my surprise, a lot of them contains new parameters, new text and new functions - stuff that was committed
to the XML files, but not to the text file README. I noticed while going through all the diff’s.
Prepare for a long series of commits. And when you update the XML docs, please update the README.
In worst case, I may have to do this twice, so that our 4.4 docs are also current with the code and the XML files.
Thanks,
/O