Hi all,
I've setup for testing purpose an xcap server with Kamailio v3.1.4 backed with a postgresql v8.4.8 all in 64bits versions. On that configuration, I'm getting the errors below and consequently the presence doesn't correctly reports the status. Does anyone has the same problem?
Best regards, Roberto Fichera.
Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: pua_usrloc [ul_publish.c:211]: should not send ul publish Jul 19 10:31:52 roberto /usr/sbin/kamailio[2015]: ERROR: <script>: ===== xhttp: xcap-caps : <null> Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: resource-lists : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/resource-lists/users/sip:roberto@192.168.2.92/index Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: pres-rules : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/pres-rules/users/sip:roberto@192.168.2.92/presrules Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 19 10:31:52 roberto /usr/sbin/kamailio[2004]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:roberto@192.168.2.92 for event presence.winfo Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:mattia@192.168.2.92 for event presence *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "sender" violates not-null constraint#012* *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: WARNING: db_postgres [km_dbase.c:473]: unexpected result returned*
Hello,
On 7/19/11 10:41 AM, Roberto Fichera wrote:
Hi all,
I've setup for testing purpose an xcap server with Kamailio v3.1.4 backed with a postgresql v8.4.8 all in 64bits versions. On that configuration, I'm getting the errors below and consequently the presence doesn't correctly reports the status. Does anyone has the same problem?
Best regards, Roberto Fichera.
Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: pua_usrloc [ul_publish.c:211]: should not send ul publish Jul 19 10:31:52 roberto /usr/sbin/kamailio[2015]: ERROR: <script>: ===== xhttp: xcap-caps : <null> Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: resource-lists : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/resource-lists/users/sip:roberto@192.168.2.92/index Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: pres-rules : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/pres-rules/users/sip:roberto@192.168.2.92/presrules Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 19 10:31:52 roberto /usr/sbin/kamailio[2004]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:roberto@192.168.2.92 for event presence.winfo Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:mattia@192.168.2.92 for event presence *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "sender" violates not-null constraint#012* *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: WARNING: db_postgres [km_dbase.c:473]: unexpected result returned*
are there any other errors/warnings in syslog after this line related to same message? It should show where in presence modules the query was executed.
Cheers, Daniel
On 07/19/2011 11:36 AM, Daniel-Constantin Mierla wrote:
Hello,
On 7/19/11 10:41 AM, Roberto Fichera wrote:
Hi all,
I've setup for testing purpose an xcap server with Kamailio v3.1.4 backed with a postgresql v8.4.8 all in 64bits versions. On that configuration, I'm getting the errors below and consequently the presence doesn't correctly reports the status. Does anyone has the same problem?
Best regards, Roberto Fichera.
Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: pua_usrloc [ul_publish.c:211]: should not send ul publish Jul 19 10:31:52 roberto /usr/sbin/kamailio[2015]: ERROR: <script>: ===== xhttp: xcap-caps : <null> Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: resource-lists : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/resource-lists/users/sip:roberto@192.168.2.92/index Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: pres-rules : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/pres-rules/users/sip:roberto@192.168.2.92/presrules Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 19 10:31:52 roberto /usr/sbin/kamailio[2004]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:roberto@192.168.2.92 for event presence.winfo Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:mattia@192.168.2.92 for event presence *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "sender" violates not-null constraint#012* *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: WARNING: db_postgres [km_dbase.c:473]: unexpected result returned*
are there any other errors/warnings in syslog after this line related to same message? It should show where in presence modules the query was executed.
No! Actually I don't see anything else. I just started Kamailio and than afterwards Jitsi, that's it! Please tell me if I've to do something in order to discover where the problem is.
Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello,
can you set the debug=5 in the config file, restart, do the same scenario and send all the log messages. The error is printed by db store result function, which is kind of strange considering that the error message is related to a null constraint.
Cheers, Daniel
On 7/19/11 11:44 AM, Roberto Fichera wrote:
On 07/19/2011 11:36 AM, Daniel-Constantin Mierla wrote:
Hello,
On 7/19/11 10:41 AM, Roberto Fichera wrote:
Hi all,
I've setup for testing purpose an xcap server with Kamailio v3.1.4 backed with a postgresql v8.4.8 all in 64bits versions. On that configuration, I'm getting the errors below and consequently the presence doesn't correctly reports the status. Does anyone has the same problem?
Best regards, Roberto Fichera.
Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: pua_usrloc [ul_publish.c:211]: should not send ul publish Jul 19 10:31:52 roberto /usr/sbin/kamailio[2015]: ERROR: <script>: ===== xhttp: xcap-caps : <null> Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: resource-lists : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/resource-lists/users/sip:roberto@192.168.2.92/index Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: pres-rules : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/pres-rules/users/sip:roberto@192.168.2.92/presrules Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 19 10:31:52 roberto /usr/sbin/kamailio[2004]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:roberto@192.168.2.92 for event presence.winfo Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:mattia@192.168.2.92 for event presence *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "sender" violates not-null constraint#012* *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: WARNING: db_postgres [km_dbase.c:473]: unexpected result returned*
are there any other errors/warnings in syslog after this line related to same message? It should show where in presence modules the query was executed.
No! Actually I don't see anything else. I just started Kamailio and than afterwards Jitsi, that's it! Please tell me if I've to do something in order to discover where the problem is.
Cheers, Daniel -- Daniel-Constantin Mierla --http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin:http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/19/2011 11:10 PM, Daniel-Constantin Mierla wrote:
Hello,
can you set the debug=5 in the config file, restart, do the same scenario and send all the log messages. The error is printed by db store result function, which is kind of strange considering that the error message is related to a null constraint.
Mmmhhh! debug=5 doesn't show anything as log messages, the log still the same. Anyway if found the problem looking under PostgreSQL logs. As I can see, the problem is under the query which basically doesn't uses the sender field, see below:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Cheers, Daniel
On 7/19/11 11:44 AM, Roberto Fichera wrote:
On 07/19/2011 11:36 AM, Daniel-Constantin Mierla wrote:
Hello,
On 7/19/11 10:41 AM, Roberto Fichera wrote:
Hi all,
I've setup for testing purpose an xcap server with Kamailio v3.1.4 backed with a postgresql v8.4.8 all in 64bits versions. On that configuration, I'm getting the errors below and consequently the presence doesn't correctly reports the status. Does anyone has the same problem?
Best regards, Roberto Fichera.
Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: pua_usrloc [ul_publish.c:211]: should not send ul publish Jul 19 10:31:52 roberto /usr/sbin/kamailio[2015]: ERROR: <script>: ===== xhttp: xcap-caps : <null> Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: resource-lists : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/resource-lists/users/sip:roberto@192.168.2.92/index Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: pres-rules : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/pres-rules/users/sip:roberto@192.168.2.92/presrules Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 19 10:31:52 roberto /usr/sbin/kamailio[2004]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:roberto@192.168.2.92 for event presence.winfo Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:mattia@192.168.2.92 for event presence *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "sender" violates not-null constraint#012* *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: WARNING: db_postgres [km_dbase.c:473]: unexpected result returned*
are there any other errors/warnings in syslog after this line related to same message? It should show where in presence modules the query was executed.
No! Actually I don't see anything else. I just started Kamailio and than afterwards Jitsi, that's it! Please tell me if I've to do something in order to discover where the problem is.
Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
regards Klaus
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
how does look the corresponding presentity mysql table, does it has the same constraint or not?
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
how does look the corresponding presentity mysql table, does it has the same constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera kernel@tekno-soft.it wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
how does look the corresponding presentity mysql table, does it has the same constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
________________________________ From: Daniel-Constantine Mierla miconda@gmail.com To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org Cc: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org Sent: Wednesday, July 20, 2011 6:53 PM Subject: Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera kernel@tekno-soft.it wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
how does look the corresponding presentity mysql table, does it has the same constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
indeed there was some inconsistency. I just committed a patch to store empty string if the sender parameter is not set. That for the fact that later (about line 450) there is a query and the sender value is taken from db and strlen used. All over, these checks are used for SLA/BLA case.
Cheers, Daniel
On 7/20/11 7:00 PM, Bucur Marius wrote:
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
*From:* Daniel-Constantine Mierla miconda@gmail.com *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org *Sent:* Wednesday, July 20, 2011 6:53 PM *Subject:* Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera <kernel@tekno-soft.it mailto:kernel@tekno-soft.it> wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values
('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml
version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple
id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the
statement
is buggy.
how does look the corresponding presentity mysql table, does it has
the same
constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/21/2011 08:21 AM, Daniel-Constantin Mierla wrote:
Hello,
indeed there was some inconsistency. I just committed a patch to store empty string if the sender parameter is not set. That for the fact that later (about line 450) there is a query and the sender value is taken from db and strlen used. All over, these checks are used for SLA/BLA case.
Could you please send me the diff so that I can apply it to my local v3.1.4 for rebuilding the rpms?
Cheers, Daniel
On 7/20/11 7:00 PM, Bucur Marius wrote:
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
*From:* Daniel-Constantine Mierla miconda@gmail.com *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org *Sent:* Wednesday, July 20, 2011 6:53 PM *Subject:* Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera <kernel@tekno-soft.it mailto:kernel@tekno-soft.it> wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple
id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
how does look the corresponding presentity mysql table, does it has the same constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b39747e2...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=403ba772...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=460fc8bf...
Am 21.07.2011 13:13, schrieb Roberto Fichera:
On 07/21/2011 08:21 AM, Daniel-Constantin Mierla wrote:
Hello,
indeed there was some inconsistency. I just committed a patch to store empty string if the sender parameter is not set. That for the fact that later (about line 450) there is a query and the sender value is taken from db and strlen used. All over, these checks are used for SLA/BLA case.
Could you please send me the diff so that I can apply it to my local v3.1.4 for rebuilding the rpms?
Cheers, Daniel
On 7/20/11 7:00 PM, Bucur Marius wrote:
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
*From:* Daniel-Constantine Mierla miconda@gmail.com *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org *Sent:* Wednesday, July 20, 2011 6:53 PM *Subject:* Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera <kernel@tekno-soft.it mailto:kernel@tekno-soft.it> wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera: > ERROR: null value in column "sender" violates not-null constraint > STATEMENT: insert into presentity > (domain,username,event,etag,expires,body,received_time ) values >
('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml
> version="1.0" encoding="UTF-8" standalone="no"?><presence > xmlns="urn:ietf:params:xml:ns:pidf" > xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" > xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" > entity="sip:roberto@192.168.2.92">dm:person id="p3619">rpid:activities/</dm:person><tuple >
id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the
statement
is buggy.
how does look the corresponding presentity mysql table, does it
has the same
constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
regards Klaus
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/21/2011 01:55 PM, Klaus Darilion wrote:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b39747e2...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=403ba772...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=460fc8bf...
I've applied all the listed patches than regenerated and installed the rpms and set back to not null the sender constraint in the db. After restarting kamailio I'm still getting the problem as before.
Am 21.07.2011 13:13, schrieb Roberto Fichera:
On 07/21/2011 08:21 AM, Daniel-Constantin Mierla wrote:
Hello,
indeed there was some inconsistency. I just committed a patch to store empty string if the sender parameter is not set. That for the fact that later (about line 450) there is a query and the sender value is taken from db and strlen used. All over, these checks are used for SLA/BLA case.
Could you please send me the diff so that I can apply it to my local v3.1.4 for rebuilding the rpms?
Cheers, Daniel
On 7/20/11 7:00 PM, Bucur Marius wrote:
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
*From:* Daniel-Constantine Mierla miconda@gmail.com *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org *Sent:* Wednesday, July 20, 2011 6:53 PM *Subject:* Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera <kernel@tekno-soft.it mailto:kernel@tekno-soft.it> wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote:
On 07/20/2011 05:18 PM, Klaus Darilion wrote: > Am 20.07.2011 17:00, schrieb Roberto Fichera: >> ERROR: null value in column "sender" violates not-null constraint >> STATEMENT: insert into presentity >> (domain,username,event,etag,expires,body,received_time ) values >>
('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml
>> version="1.0" encoding="UTF-8" standalone="no"?><presence >> xmlns="urn:ietf:params:xml:ns:pidf" >> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" >> xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" >> entity="sip:roberto@192.168.2.92">dm:person > id="p3619">rpid:activities/</dm:person><tuple >>
id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
> Seems like the statement does not insert the "sender" although it is > mandatory. If "sender" is really mandatory, then it seems the
statement
> is buggy. how does look the corresponding presentity mysql table, does it
has the same
constraint or not?
Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
> regards > Klaus > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
> sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/21/2011 05:00 PM, Roberto Fichera wrote:
On 07/21/2011 01:55 PM, Klaus Darilion wrote:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b39747e2...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=403ba772...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=460fc8bf...
I've applied all the listed patches than regenerated and installed the rpms and set back to not null the sender constraint in the db. After restarting kamailio I'm still getting the problem as before.
Mmmhhh! The sender still null, but after removing the not null constraint again from the sender field, I just see another problem:
Jul 21 17:02:37 roberto /usr/sbin/kamailio[24781]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 21 17:02:37 roberto /usr/sbin/kamailio[24781]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 21 17:02:37 roberto /usr/sbin/kamailio[24780]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted *Jul 21 17:02:37 roberto /usr/sbin/kamailio[24780]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "expires" violates not-null constraint#012*
so since the expires isn't present in the same query than the db trigger the not null problem. New query is below:
ERROR: null value in column "expires" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,sender,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311260173.24780.4.0','','<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3387"rpid:activities/</dm:person><tuple id="t8698"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311260557)
Am 21.07.2011 13:13, schrieb Roberto Fichera:
On 07/21/2011 08:21 AM, Daniel-Constantin Mierla wrote:
Hello,
indeed there was some inconsistency. I just committed a patch to store empty string if the sender parameter is not set. That for the fact that later (about line 450) there is a query and the sender value is taken from db and strlen used. All over, these checks are used for SLA/BLA case.
Could you please send me the diff so that I can apply it to my local v3.1.4 for rebuilding the rpms?
Cheers, Daniel
On 7/20/11 7:00 PM, Bucur Marius wrote:
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
*From:* Daniel-Constantine Mierla miconda@gmail.com *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org *Sent:* Wednesday, July 20, 2011 6:53 PM *Subject:* Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera <kernel@tekno-soft.it mailto:kernel@tekno-soft.it> wrote:
On 07/20/2011 05:34 PM, Roberto Fichera wrote: > On 07/20/2011 05:18 PM, Klaus Darilion wrote: >> Am 20.07.2011 17:00, schrieb Roberto Fichera: >>> ERROR: null value in column "sender" violates not-null constraint >>> STATEMENT: insert into presentity >>> (domain,username,event,etag,expires,body,received_time ) values >>>
('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml
>>> version="1.0" encoding="UTF-8" standalone="no"?><presence >>> xmlns="urn:ietf:params:xml:ns:pidf" >>> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" >>> xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" >>> entity="sip:roberto@192.168.2.92">dm:person >> id="p3619">rpid:activities/</dm:person><tuple >>>
id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
>> Seems like the statement does not insert the "sender" although it is >> mandatory. If "sender" is really mandatory, then it seems the
statement
>> is buggy. > how does look the corresponding presentity mysql table, does it
has the same
> constraint or not? Anyway I can confirm that removing the constraint the problem of presence backed by postgresql seems solved.
>> regards >> Klaus >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
>> sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
> sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/21/2011 05:10 PM, Roberto Fichera wrote:
On 07/21/2011 05:00 PM, Roberto Fichera wrote:
On 07/21/2011 01:55 PM, Klaus Darilion wrote:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b39747e2...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=403ba772...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=460fc8bf...
I've applied all the listed patches than regenerated and installed the rpms and set back to not null the sender constraint in the db. After restarting kamailio I'm still getting the problem as before.
Mmmhhh! The sender still null, but after removing the not null constraint again from the sender field, I just see another problem:
Jul 21 17:02:37 roberto /usr/sbin/kamailio[24781]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 21 17:02:37 roberto /usr/sbin/kamailio[24781]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 21 17:02:37 roberto /usr/sbin/kamailio[24780]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted *Jul 21 17:02:37 roberto /usr/sbin/kamailio[24780]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "expires" violates not-null constraint#012*
so since the expires isn't present in the same query than the db trigger the not null problem. New query is below:
ERROR: null value in column "expires" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,sender,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311260173.24780.4.0','','<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3387"rpid:activities/</dm:person><tuple id="t8698"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311260557)
My fault, I've used cutted the n_query_cols++; before the column expires in the source code. Going to rebuild and testing again!
Am 21.07.2011 13:13, schrieb Roberto Fichera:
On 07/21/2011 08:21 AM, Daniel-Constantin Mierla wrote:
Hello,
indeed there was some inconsistency. I just committed a patch to store empty string if the sender parameter is not set. That for the fact that later (about line 450) there is a query and the sender value is taken from db and strlen used. All over, these checks are used for SLA/BLA case.
Could you please send me the diff so that I can apply it to my local v3.1.4 for rebuilding the rpms?
Cheers, Daniel
On 7/20/11 7:00 PM, Bucur Marius wrote:
Hi,
It think there is something wrong with the sql scripts, hence the code obviously accepts a null sender.
presentity.c:357 if( presentity->sender) { query_cols[n_query_cols] = &str_sender_col; query_vals[n_query_cols].type = DB1_STR; query_vals[n_query_cols].nul = 0; query_vals[n_query_cols].val.str_val.s = presentity->sender->s; query_vals[n_query_cols].val.str_val.len = presentity->sender->len; n_query_cols++; }
>From a logical point of view, I believe the sender should not be mandatory hence it could be generated by a machine - whose identity/location is not needed.
Regards, Marius
*From:* Daniel-Constantine Mierla miconda@gmail.com *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List sr-users@lists.sip-router.org *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List sr-users@lists.sip-router.org *Sent:* Wednesday, July 20, 2011 6:53 PM *Subject:* Re: [SR-Users] Kamailio presence server problem with PostgreSQL
Hello,
Thanks for troubleshooting further. What intrigues me is that the error message from syslog is printed from store result function, which is used after doing a select query. So something else might have to be reviewed as well.
Anyhow, missing sender value should be checked, since it is a constraint for non-null. Interesting it was not risen with mysql.
Cheers, Daniel
On Jul 20, 2011, at 5:46 PM, Roberto Fichera <kernel@tekno-soft.it mailto:kernel@tekno-soft.it> wrote:
> On 07/20/2011 05:34 PM, Roberto Fichera wrote: >> On 07/20/2011 05:18 PM, Klaus Darilion wrote: >>> Am 20.07.2011 17:00, schrieb Roberto Fichera: >>>> ERROR: null value in column "sender" violates not-null constraint >>>> STATEMENT: insert into presentity >>>> (domain,username,event,etag,expires,body,received_time ) values >>>> ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml >>>> version="1.0" encoding="UTF-8" standalone="no"?><presence >>>> xmlns="urn:ietf:params:xml:ns:pidf" >>>> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" >>>> xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" >>>> entity="sip:roberto@192.168.2.92">dm:person >>> id="p3619">rpid:activities/</dm:person><tuple >>>> id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624) >>> Seems like the statement does not insert the "sender" although it is >>> mandatory. If "sender" is really mandatory, then it seems the statement >>> is buggy. >> how does look the corresponding presentity mysql table, does it has the same >> constraint or not? > Anyway I can confirm that removing the constraint the problem > of presence backed by postgresql seems solved. > >>> regards >>> Klaus >>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 07/21/2011 05:30 PM, Roberto Fichera wrote:
On 07/21/2011 05:10 PM, Roberto Fichera wrote:
On 07/21/2011 05:00 PM, Roberto Fichera wrote:
On 07/21/2011 01:55 PM, Klaus Darilion wrote:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b39747e2...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=403ba772...
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=460fc8bf...
I've applied all the listed patches than regenerated and installed the rpms and set back to not null the sender constraint in the db. After restarting kamailio I'm still getting the problem as before.
Mmmhhh! The sender still null, but after removing the not null constraint again from the sender field, I just see another problem:
Jul 21 17:02:37 roberto /usr/sbin/kamailio[24781]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 21 17:02:37 roberto /usr/sbin/kamailio[24781]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 21 17:02:37 roberto /usr/sbin/kamailio[24780]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted *Jul 21 17:02:37 roberto /usr/sbin/kamailio[24780]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "expires" violates not-null constraint#012*
so since the expires isn't present in the same query than the db trigger the not null problem. New query is below:
ERROR: null value in column "expires" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,sender,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311260173.24780.4.0','','<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3387"rpid:activities/</dm:person><tuple id="t8698"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311260557)
My fault, I've used cutted the n_query_cols++; before the column expires in the source code. Going to rebuild and testing again!
Ok! Now everything works fine!
Thanks!
Am 20.07.2011 17:34, schrieb Roberto Fichera:
On 07/20/2011 05:18 PM, Klaus Darilion wrote:
Am 20.07.2011 17:00, schrieb Roberto Fichera:
ERROR: null value in column "sender" violates not-null constraint STATEMENT: insert into presentity (domain,username,event,etag,expires,body,received_time ) values ('192.168.2.92','roberto','presence','a.1311173612.4970.2.0',1311177224,'<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="sip:roberto@192.168.2.92">dm:person id="p3619"rpid:activities/</dm:person><tuple id="t9285"><status><basic>open</basic></status><contact>sip:roberto@192.168.2.92</contact><note>Online</note></tuple></presence>',1311173624)
Seems like the statement does not insert the "sender" although it is mandatory. If "sender" is really mandatory, then it seems the statement is buggy.
how does look the corresponding presentity mysql table, does it has the same constraint or not?
You find the data base scripts for comparison in:
utils/kamctl/mysql and utils/kamctl/postgres
regards klaus
-
Bucur Marius -
Daniel-Constantin Mierla -
Daniel-Constantine Mierla
-
Klaus Darilion -
Roberto Fichera