THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#178 - Kamailio 3.2.0 postgresql 9.1.1 connection problems.
User who did this - Nick Altmann (nikbyte)
----------
0(435) ERROR: db_postgres [km_pg_con.c:82]: connection pointer is NULL
0(435) ERROR: db_postgres [km_pg_con.c:95]: cleaning up 0x7fb7c8970e10=pkg_free()
0(435) ERROR: <core> [db.c:302]: could not add connection to the pool 0(435) ERROR: usrloc [ul_mod.c:360]: child(0): failed to connect to database
0(435) ERROR: <core> [sr_module.c:882]: init_mod_child(): Error while initializing module usrloc (//lib64/kamailio/modules_k/usrloc.so)
0(435) ERROR: <core> [main.c:1388]: ERROR: main_dontfork: init_child(PROC_MAIN) -- exiting
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=178#comment359
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#178 - Kamailio 3.2.0 postgresql 9.1.1 connection problems.
User who did this - Nick Altmann (nikbyte)
----------
I had working server with 3.2.0 and postgresql 9.0. Fedora 14. SELinux disabled, firewall has not rate limit rules. Postgresql on the same server. Mysql also connected to this configuration. Nothing changes. I upgraded to postgresql 9.1.1 and kamailio doesn't start. :-( I tries to disable module by module and when I disable usrloc it starts. After, I upgrade kamailio to 3.3.0 from git and it starts and works. No changes in configuration. 3.2.0 doesn't start, 3.3.0 does start. Mystical problem. :-)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=178#comment358
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Timo Reimann (tr)
----------
Hey Bayan,
sorry for not replying any sooner. I was quite busy in the last couple of days and couldn't dedicate too much time to the project. Your issue is quite on the top of my priority list, however, and I'll try to get to it as soon as I can.
The dump you gave me looks different this time -- will scrutinze it further.
What would prove really helpful as well (if your resources permit to do so) is a SIP trace (using ngrep for example) together with another dump and more debug-level logging. That way, I could possibly correlate the dump content to the failing dialog and figure out what lead to the faulty situation. If setting log verbosity to DEBUG is too heavy for you, what you can do alternatively is change all "LM_DBG" strings in modules_k/dialog/*.{h,c} to LM_<whatever level you usually log>.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment357
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Bayan Towfiq (btowfiq)
----------
Hi Timo,
Kamailio is still crashing frequently. Have you had a chance to look into it? Would you like any other tests?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment356
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Module: sip-router
Branch: master
Commit: 96c35ff6afeca6320d7299cf9ecebc721d246e30
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=96c35ff…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Mon Nov 14 22:07:08 2011 +0100
pua: fixed wrong docbook tag name
---
modules_k/pua/doc/pua_admin.xml | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/modules_k/pua/doc/pua_admin.xml b/modules_k/pua/doc/pua_admin.xml
index bd22321..4c553f8 100644
--- a/modules_k/pua/doc/pua_admin.xml
+++ b/modules_k/pua/doc/pua_admin.xml
@@ -24,13 +24,13 @@
<para>
It can be used with the following modules: pua_mi and pua_usrloc,
pua_bla and pua_xmpp.
- The <emphasize>pua_mi</emphasize> offer the possibility to publish any kind of information
+ The <emphasis>pua_mi</emphasis> offer the possibility to publish any kind of information
or subscribing to a resource through the manager interface.
- The <emphasize>pua_usrloc</emphasize> module calls a function exported by pua modules to publish
+ The <emphasis>pua_usrloc</emphasis> module calls a function exported by pua modules to publish
elementary presence information, such as basic status "open" or "closed",
for clients that do not implement client-to-server presence.
- Through <emphasize>pua_bla</emphasize> , BRIDGED LINE APPEARANCE features are added to openser.
- The <emphasize>pua_xmpp</emphasize> module represents a gateway between SIP and XMPP, so that
+ Through <emphasis>pua_bla</emphasis> , BRIDGED LINE APPEARANCE features are added to openser.
+ The <emphasis>pua_xmpp</emphasis> module represents a gateway between SIP and XMPP, so that
jabber and SIP clients can exchange presence information.
</para>
<para>