Hi, I’m running into an issue in 2.3.3 with HEP tracing and the proto_tcp and mi_datagram modules. I am not setting the trace_destination parameter in the mi_datagram module, so I expect tracing should be disabled. I am setting the parameter in the proto_tcp module, but the trace_on parameter is disabled. However, tracing still seems to be attempting and is causing errors.
This config: #// Even though we are not receiving HEP, #// this listener is required by OpenSIPS #// to use the proto_hep module. listen=hep_udp:PRIVATE_ADDRESS:9060 listen=hep_tcp:PRIVATE_ADDRESS:9060 #// DATAGRAM Management Interface loadmodule "mi_datagram.so" modparam("mi_datagram", "unix_socket_mode", 0666) modparam("mi_datagram", "socket_name", "/tmp/opensips.sock") modparam("mi_datagram", "children_count", 1) #// PROTOcol HEP module loadmodule "proto_hep.so" modparam("proto_hep", "hep_id", "[hep_tcp] 127.0.0.1:9060; transport=tcp; version=3") modparam("proto_hep", "hep_capture_id", 1) modparam("proto_hep", "homer5_on", 1) #// PROTOcol TCP module loadmodule "proto_tcp.so" modparam("proto_tcp", "trace_destination", "hep_tcp") modparam("proto_tcp", "trace_on", 0) Generates these errors: Mar 30 13:52:25 [328] ERROR:proto_hep:build_hep3_buf: unknown IP family Mar 30 13:52:25 [328] ERROR:proto_hep:send_hep_message: failed to build hep buffer! Mar 30 13:52:25 [328] ERROR:core:trace_mi_message: failed to send trace message! Mar 30 13:52:25 [328] ERROR:mi_datagram:mi_trace_request: failed to trace mi command request! Mar 30 13:52:25 [328] ERROR:proto_hep:build_hep3_buf: unknown IP family Mar 30 13:52:25 [328] ERROR:proto_hep:send_hep_message: failed to build hep buffer! Mar 30 13:52:25 [328] ERROR:core:trace_mi_message: failed to send trace message! Mar 30 13:52:25 [328] ERROR:mi_datagram:mi_trace_reply: failed to trace mi command reply! Tracing for the mi_datagram module should not be enabled, but appears to be attempting to trace anyway. If I change the HEP config to use version 2 then the errors change: #// Even though we are not receiving HEP, #// this listener is required by OpenSIPS #// to use the proto_hep module. listen=hep_udp:PRIVATE_ADDRESS:9060 #// DATAGRAM Management Interface loadmodule "mi_datagram.so" modparam("mi_datagram", "unix_socket_mode", 0666) modparam("mi_datagram", "socket_name", "/tmp/opensips.sock") modparam("mi_datagram", "children_count", 1) #// PROTOcol HEP module loadmodule "proto_hep.so" modparam("proto_hep", "hep_id", "[hep_udp] 127.0.0.1:9060; transport=udp; version=2") modparam("proto_hep", "hep_capture_id", 1) modparam("proto_hep", "homer5_on", 1) #// PROTOcol TCP module loadmodule "proto_tcp.so" modparam("proto_tcp", "trace_destination", "hep_udp") modparam("proto_tcp", "trace_on", 0) Generates these errors: Mar 30 14:33:12 [341] ERROR:proto_hep:unpack_hepv12: unsupported family [1] Mar 30 14:33:12 [340] ERROR:proto_hep:unpack_hepv12: unsupported family [1] Mar 30 14:33:12 [341] ERROR:proto_hep:update_recv_info: invalid hep version! Mar 30 14:33:12 [340] ERROR:proto_hep:update_recv_info: invalid hep version! Mar 30 14:33:12 [340] ERROR:proto_hep:hep_udp_read_req: failed to run hep callbacks Mar 30 14:33:12 [341] ERROR:proto_hep:hep_udp_read_req: failed to run hep callbacks If I remove the trace_destination parameter from the proto_tcp module all errors stop. Interestingly, if I set the HEP listener port to something different than the destination port, the errors also stop. Thanks, Ben Newlin
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users