Hi, Dawid!
That log appears when you have traffic. If you stop the traffic and
you're still seeing those debug messages, then that might be a problem.
BR
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 11/03/2016 10:24 AM, Dawid Mielnik wrote:
Hi Razvan,
I know they are debug level but because they only happen from time to
time and they really flood the log I was worried this might be some
loop error.
Ok then, thank you for the info!
BR,
Dawid
On Thu, Nov 3, 2016 at 9:11 AM, Răzvan Crainea <[email protected]
<mailto:[email protected]>> wrote:
Hi, Dawid!
Those are simply debug messages from the process's internal
reactor. There is nothing wrong with them, it simply proves the
TCP interface (for bin replication) is working properly. Unless
there is no ERROR, WARNING, CRITICAL logs, there is nothing to
worry about.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com <http://www.opensips-solutions.com>
On 11/02/2016 11:16 PM, Dawid Mielnik wrote:
Hi,
I have a reduntant OpenSIPS 2.2.1 setup with clusterer and binary
interface replication. TCP is not used for SIP. A few times I
have observed debug log being flooded with messages like these below.
What is causing them ? Should I be worried ? How to get rid of
this issue ?
Oct 17 11:25:56.281436 DEB 4315 DBG:maxfwd:is_maxfwd_present:
value = 70
Oct 17 11:25:56.281481 DEB 4315 DBG:uri:has_totag: no totag
Oct 17 11:25:56.281492 DEB 4315 DBG:siptrace:sip_trace_w: can't
trace dialog! Will try to trace transaction
Oct 17 11:25:56.281498 DEB 4315 DBG:siptrace:sip_trace_w:
tracing transaction!
Oct 17 11:25:56.281502 DEB 4315 DBG:core:parse_to_param:
tag=as09518802
Oct 17 11:25:56.281507 DEB 4315 DBG:core:parse_to: end of header
reached, state=29
Oct 17 11:25:56.281511 DEB 4315 DBG:core:parse_to:
display={"asterisk"}, ruri={sip:[email protected]
<mailto:sip:[email protected]>.253}
Oct 17 11:25:56.281516 DEB 4315 DBG:core:parse_headers: flags=40
Oct 17 11:25:56.281521 DEB 4315 DBG:siptrace:sip_trace:
sip_trace called
Oct 17 11:25:56.281525 DEB 4315 DBG:siptrace:pipport2su: proto
17, host XX.XX.XXX.253 , port 5060
Oct 17 11:25:56.281530 DEB 4315 DBG:siptrace:pipport2su: proto
17, host XX.XX.XXX.250 , port 5060
Oct 17 11:25:56.281535 DEB 4315 DBG:core:mk_proxy: doing DNS
lookup...
Oct 17 11:25:56.281539 DEB 4315 DBG:core:comp_scriptvar: int 20
: 5060 / 5060
Oct 17 11:25:56.281543 DEB 4315 DBG:core:parse_headers:
flags=ffffffffffffffff
Oct 17 11:25:56.281548 DEB 4315 DBG:core:check_ip_address:
params XX.XX.XXX.253, XX.XX.XXX.253, 0
Oct 17 11:25:56.281552 DEB 4315 DBG:core:parse_headers: flags=40
Oct 17 11:25:56.281570 DEB 4315 DBG:siptrace:pipport2su: proto
17, host XX.XX.XXX.250 , port 5060
Oct 17 11:25:56.281576 DEB 4315 DBG:siptrace:pipport2su: proto
17, host XX.XX.XXX.253 , port 5060
Oct 17 11:25:56.281581 DEB 4315 DBG:core:mk_proxy: doing DNS
lookup...
Oct 17 11:25:56.281664 DEB 4315 DBG:core:destroy_avp_list:
destroying list (nil)
Oct 17 11:25:56.281673 DEB 4315 DBG:core:receive_msg: cleaning up
Oct 17 11:25:58.515305 DEB 4335 DBG:core:handle_tcpconn_ev: data
available on 0x7f2da0d453c8 48
Oct 17 11:25:58.515378 DEB 4335 DBG:core:io_watch_del:
[TCP_main] io_watch_del op on index 1 48 (0x83b1c0, 48, 1,
0x0,0x1) fd_no=36 called
Oct 17 11:25:58.515387 DEB 4335 DBG:core:send2child: to tcp
child 0 0(4327), 0x7f2da0d453c8 rw 1
Oct 17 11:25:58.515792 DEB 4327 DBG:core:handle_io: We have
received conn 0x7f2da0d453c8 with rw 1 on fd 8
Oct 17 11:25:58.515814 DEB 4327 DBG:core:io_watch_add:
[TCP_worker] io_watch_add op (8 on 6) (0x83b1c0, 8, 19,
0x7f2da0d453c8,1), fd_no=2/1024
Oct 17 11:25:58.515820 DEB 4327 DBG:core:tcp_receive_timeout:
0x7f2da0d453c8 expired - (221, 222) lt=221
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
