11 Mar
2020
11 Mar
'20
10:27 a.m.
On 10.03.20 20:30, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
It seems to be the case of a retransmission timeout:
#17 0x00007f7dc04d4aca in acc_onreply (t=0x7f7d9e3b0650, req=0x7f7d9e357650,
reply=0xffffffffffffffff, code=408) at acc_logic.c:604
Code is 408 and the reply is faked value. This case is happening in
timer process.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
There is no async-insert done by acc with
db_cluster, it is always
standard (sync) insert. You would have to track why the mysql server (or
the client library) is blocking from time to time, I don't think it is
something that kamailio can do.
OK, thanks for the explanation.
One more question: why is the timer process involved with this acc
insert? Isn't accounting done by the normal worker processes that
handle requests/responses?