[OpenSIPS-Users] HEP mi_datagram tracing

Bogdan-Andrei Iancu bogdan at opensips.org
Wed Apr 4 13:56:46 EDT 2018


Hey, I have to thank you for doing this testing and reporting - it is of 
a real help for the project and for the rest of the community.

If you consider joining us for the OpenSIPS Summit, you have a free 
ticket (training also) from us ;).

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 04/04/2018 08:54 PM, Ben Newlin wrote:
>
> Bogdan,
>
> Excellent! I have pulled the latest and verified the errors are gone. 
> Thanks so much for looking at this so quickly!
>
> Sorry to be pushing these issues so much but I am very anxious to get 
> off 1.11 and onto 2.3 and then of course to 2.4!
>
> Thanks,
>
> Ben Newlin
>
> *From: *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Date: *Wednesday, April 4, 2018 at 1:38 PM
> *To: *Ben Newlin <Ben.Newlin at genesys.com>, OpenSIPS users mailling 
> list <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] HEP mi_datagram tracing
>
> Ben,
>
> I did my own tests and I found and fixed the error - the fix is 
> already committed on all affected branches, so updating it should to 
> the trick. Shortly I will backport the other fix too.
>
> Thanks and regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    http://www.opensips-solutions.com
> OpenSIPS Summit 2018
>    http://www.opensips.org/events/Summit-2018Amsterdam
>
> On 04/04/2018 06:47 PM, Ben Newlin wrote:
>
>     No, I only have the mi_datagram backend configured as shown and
>     tracing is not enabled.
>
>     Thanks,
>
>     Ben Newlin
>
>     *From: *Bogdan-Andrei Iancu <bogdan at opensips.org>
>     <mailto:bogdan at opensips.org>
>     *Date: *Wednesday, April 4, 2018 at 11:31 AM
>     *To: *OpenSIPS users mailling list <users at lists.opensips.org>
>     <mailto:users at lists.opensips.org>, Ben Newlin
>     <Ben.Newlin at genesys.com> <mailto:Ben.Newlin at genesys.com>
>     *Subject: *Re: [OpenSIPS-Users] HEP mi_datagram tracing
>
>     Hi Ben,
>
>     Do you have tracing enabled for at least one MI backend (does not
>     matter which one) ?
>
>     Regards,
>
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>
>     http://www.opensips-solutions.com
>
>     OpenSIPS Summit 2018
>
>     http://www.opensips.org/events/Summit-2018Amsterdam
>
>     On 03/30/2018 05:43 PM, Ben Newlin wrote:
>
>         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 at lists.opensips.org<mailto:Users at lists.opensips.org>
>
>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180404/538d82fa/attachment-0001.html>


More information about the Users mailing list