13 Oct
2022
13 Oct
'22
2:56 p.m.
On 13 Oct 2022, at 13:50, Alex Balashov
<abalashov(a)evaristesys.com> wrote:
Hi,
When there are no stored transactions for an AOR, it logs this error:
Oct 13 07:48:18 gw1 /usr/sbin/kamailio[14758]: ERROR: tsilo [ts_append.c:64]:
ts_append(): failed to retrieve record for sip:abalashov@sip.evaristesys.com
But not having transactions ts_store()’d is a rather normal occurrence, right? It is the
expected case the vast majority of the time that someone registers.
Does that mean one is simply destined to have this scary-looking error, to the syslog
ERROR facility, for a normal runtime condition? Is there not some principle against using
attention-grabbing error messages this way? Would a patch to fix be welcome?
I think that’s a bad sysadm experience… Could be a WARNING or a DEBUG.
Do you get an error code indicating that your silo is empty?
/O