Re: [SR-Users] [pua] Question to DB Mode 0

I can confirm I am seeing the same issue, I'm not setting db_mode parameter, but according to the docs it defaults to 0 (caching mode). I'm running kamailio v4.3.3

Log: Oct 9 11:06:27 kam_proxy01[20890]: ERROR: db_sqlite [dbase.c:489]: db_sqlite_commit(): sqlite commit failed: constraint failed Oct 9 11:06:27 kam_proxy01[20890]: ERROR: db_sqlite [dbase.c:138]: db_sqlite_cleanup_query(): finalize failed: pua.call_id may not be NULL Oct 9 11:06:27 kam_proxy01[20890]: ERROR: pua [pua.c:1179]: db_update(): while inserting in db table pua

Associated Process: Process:: ID=76 PID=20890 Type=slow timer

Kamailio Version: version: kamailio 4.3.3 (x86_64/linux) e275bc

Thanks

On 03/10/2015 11: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