Any idea where this kind of error message could come from:
Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 61 Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core> [core/io_wait.h:607]: io_watch_del(): trying to delete already erased entry 61 in the hash(-1, 0, 0x7f689c16a868) flags 0) Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core> [core/io_wait.h:607]: io_watch_del(): trying to delete already erased entry 64 in the hash(-1, 0, 0x7f68c063b0f0) flags 0) Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: CRITICAL: <core> [core/pass_fd.c:191]: send_fd(): sendmsg failed sending 79 on 64: Broken pipe (32) Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core> [core/tcp_main.c:4225]: send2child(): send_fd failed for 0x7f689c18a0b0 (flags 0x4018), fd 79
Debug does not give any hints.
-- Juha
Hello Juha,
the error message looks related to the TCP support in core. There was a mismatch in the internal TCP hash table, and it also could not send out a message on a (network) file descriptor.
If you only saw it once it is probably not worth to dig that deep into it, might be also caused from some external factors.
Cheers,
Henning
Henning Westerholt writes:
If you only saw it once it is probably not worth to dig that deep into it, might be also caused from some external factors.
It has appeared several times and may be related to json request. Perhaps tcp connection is broken before K has delivered the result.
-- Juha
-
Henning Westerholt -
Juha Heinanen