Great, please let me know if you find anything or if you need any further information.

Regards,
Maciej

2015-10-06 8:03 GMT+02:00 Daniel-Constantin Mierla <miconda@gmail.com>:
OK -- it is clear now where to look in the code, I will do it as soon as I get a chance.

Daniel


On 05/10/15 20:09, Maciej Marczyński wrote:
The process is: slow timer

Thanks,
Maciej
W dniu 2015-10-05 o 15:23, Daniel-Constantin Mierla pisze:
Hello,

to confirm it is timer or not, can you do:

kamctl ps

That will show the type of the process.

Cheers,
Daniel

On 05/10/15 09:29, Maciej Marczyński wrote:
Hi, sure:

Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [publish.c:75]: msg_presentity_clean(): cleaning expired presentity information
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: db_sqlite [dbase.c:183]: db_sqlite_submit_query(): submit_query: select username,domain,etag,event from presentity where expires<?1 AND expires>?2 order by username
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 56 bytes for result set at 0x7f3dc8e479e8
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [publish.c:116]: msg_presentity_clean(): found n= 0 expires messages#012
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0x7f3dc8e479e8
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: db_sqlite [dbase.c:183]: db_sqlite_submit_query(): submit_query: delete from presentity where expires<?1 AND expires>?2
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [subscribe.c:734]: msg_watchers_clean(): cleaning pending subscriptions
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: db_sqlite [dbase.c:183]: db_sqlite_submit_query(): submit_query: delete from watchers where inserted_time<?1 AND status=?2
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [subscribe.c:2318]: timer_db_update(): db_update timer
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [subscribe.c:1984]: update_db_subs_timer_dbnone(): update_db_subs_timer_dbnone: start
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:115]: printf_subs(): pres_uri: sip:account2@sip.xyz.com
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:116]: printf_subs(): watcher_user@watcher_domain: account3@sip.xyz.com
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:117]: printf_subs(): to_user@to_domain: account2@sip.xyz.com
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:118]: printf_subs(): from_user@from_domain: account3@sip.xyz.com
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:119]: printf_subs(): callid/from_tag/to_tag: GEHx1WHLMkpUoupFOXCVsil0C645AlOM/w89WvllNIi9BUryy9VDt3Zx4Tppz8-J6/a6a1c5f60faecf035a1ae5b6e96e979a-5550
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:120]: printf_subs(): local_cseq/remote_cseq: 3/30284
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:121]: printf_subs(): local_contact/contact: sip:172.17.0.1:5060;transport=tcp/sip:account3@172.17.0.7:39388;transport=TCP;ob;alias=172.17.42.1~42912~2
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:122]: printf_subs(): record_route:
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:123]: printf_subs(): sockinfo_str: tcp:172.17.0.1:5060
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:125]: printf_subs(): event: presence
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:126]: printf_subs(): status: active
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:127]: printf_subs(): reason:
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:128]: printf_subs(): version: 3
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:129]: printf_subs(): expires: 1444029183
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: presence [notify.c:131]: printf_subs(): updated/updated_winfo: 0/0
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: pua [pua.c:1098]: db_update(): INSERTDB_FLAG
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: DEBUG: db_sqlite [dbase.c:183]: db_sqlite_submit_query(): submit_query: insert into pua (pres_uri,pres_id,flag,event,watcher_uri,call_id,to_tag,from_tag,etag,tuple_id,cseq,expires,desired_expires,record_route,contact,remote_contact,version,extra_headers ) values (?1,?2,?3,?4,?5,?6,?7,?8,?9,?10,?11,?12,?13,?14,?15,?16,?17,?18)
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: ERROR: db_sqlite [dbase.c:489]: db_sqlite_commit(): sqlite commit failed: NOT NULL constraint failed: pua.call_id
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: ERROR: db_sqlite [dbase.c:138]: db_sqlite_cleanup_query(): finalize failed: NOT NULL constraint failed: pua.call_id
Oct  5 07:04:36 028e61eb5dc7 kamailio[286]: ERROR: pua [pua.c:1179]: db_update(): while inserting in db table pua

The log appears probably on a timer as there's no SIP message at the time. The scenario is: A Subscribes B presentity, empty NOTIFY to A, B Registers + NOTIFY to A, B Unregister + NOTIFY to A, [...] some time later - bang - above logs.

regards,
Maciej

2015-10-05 7:30 GMT+02:00 Daniel-Constantin Mierla <miconda@gmail.com>:
Hello,

I think that even in db_mode 0 some records are stored in database, just that a cache of some data is kept in memory (to check if worth querying the database).

Can you set debug=3 and send over the log messages from syslog for processing a sip message that ends up in such errors?

Cheers,
Daniel


On 03/10/15 12:06, Maciej Marczyński wrote:
Hi Guys,
I have a question regarding pua module parameter 'db mode'.
I run Kamailio (4.3.2) with sqlite and I tried to set the parameter to 0 but even then I received:
ERROR: db_sqlite [dbase.c:489]: db_sqlite_commit(): sqlite commit failed: NOT NULL constraint failed: pua.call_id
ERROR: db_sqlite [dbase.c:138]: db_sqlite_cleanup_query(): finalize failed: NOT NULL constraint failed: pua.call_id
ERROR: pua [pua.c:1179]: db_update(): while inserting in db table pua
As far as I checked the documentation, it says that '0' means:
high speed memory based storage
Does it still writes to DB anyway (on timer or whatever?) or just keep it in memory? Is there any way to disable writing to DB?

The second thing is the reason of the ERRORs above. Why does pua think that my call_id is null?


If you need any more information please let me know.

Best regards and have a good weekend,
Maciej


_______________________________________________
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://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

_______________________________________________
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://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat


-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat