Hi,

Sorry not to have answered before, I just did a restart and there was no error.

We don't restart often so I can't tell you how often this issue appears but I will keep an eye on it.

It may be a bug in the insert or update code in db_mongodb that misses the caller_sock column but I'm not sure.

Is it possible a dialog is inserted without caller_sock field? Or, is it possible $unset is used somewhere for the caller_sock?

Mickael

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, May 07, 2015 10:23 AM
To: Kamailio (SER) - Users Mailing List; Mickael Marrache
Subject: Re: [SR-Users] db_mongodb get columns error

Hello,

On 27/04/15 23:46, Daniel-Constantin Mierla wrote:

Hello,

On 22/04/15 14:00, Mickael Marrache wrote:

Hi,

After restarting Kamailio, I got the following errors during the startup:

kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [caller_sock] not found in result iterator

kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns

kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result

kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query

kamailio[12614]: ERROR: dialog [dlg_db_handler.c:257]: select_entire_dialog_table(): Error while querying database

What may be causing the issue? I should always have a caller_sock in every dialog document.

the error is thrown when the caller_sock field is not found in the b/json document returned by mongodb.

Do you get the error every time you restart?

Any update on this? As I am spending some time with testing for 4.3, I would like to close this issue if there is something to fix.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com