[Spce-user] memory allocation proxy

Fri Sep 23 17:18:02 EDT 2016

Hello,

After a good months of use, I couldnt receive or make calls and searching
the logs I saw a memory allocation error. I checked the memory and had
plenty of free.

I restarted the proxy and all is well but next time it happens is there
some counter I could check and/or increase?

root at sip:/var/log/ngcp# cat /etc/sipwise_ngcp_version
System installed. NGCP version mr4.4.1 on 2016-09-03 03:19:37
root at sip:/var/log/ngcp#

Sep 23 17:13:00 sip proxy[13419]: NOTICE: <script>: Request leaving server
via local route - R=sip:7877197888 at 74.85.156.17:5060;transport=udp ID=
621F5FB2 at 10.246.9.8 UA='<null>'
Sep 23 17:13:00 sip proxy[13419]: ERROR: tm [t_reply.c:533]:
_reply_light(): ERROR: _reply_light: can't generate 487 reply when a final
480 was sent out
Sep 23 17:13:01 sip proxy[13413]: ERROR: <core> [msg_translator.c:2421]:
build_res_buf_from_sip_req(): out of memory; needs 766
Sep 23 17:13:01 sip proxy[13415]: ERROR: <core> [parser/msg_parser.c:158]:
get_hdr_field(): get_hdr_field: out of memory
Sep 23 17:13:01 sip proxy[13415]: ERROR: tm [t_lookup.c:1050]:
t_check_msg(): ERROR: reply cannot be parsed
Sep 23 17:13:01 sip proxy[13415]: ERROR: <core> [msg_translator.c:2264]:
generate_res_buf_from_sip_res(): out of mem
Sep 23 17:13:01 sip proxy[13415]: ERROR: <core> [forward.c:760]:
do_forward_reply(): building failed
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:158]:
get_hdr_field(): get_hdr_field: out of memory
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2513]:
parse_via(): ERROR:parse_via: mem. allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2708]:
parse_via(): ERROR: parse_via on: <SIP/2.0/UDP
196.12.170.244:5060;rport=5060;branch=z9hG4bK5h4ma120b8dqsa42c920.1#015#012Allow-Events:
message-summary, refer, dialog, line-seize, presence, call-info,
as-feature-event, calling-name#015#012Max-Forwards: 68#015#012Call-ID:
A9B4C172 at 10.246.9.8#015#012From:
<sip:metaswitch at 196.12.170.244:5060>;tag=10.246.9.8+1+7cd08+d5ede4e9#015#012CSeq:
164593911 OPTIONS#015#012Organization: MetaSwitch#015#012Supported:
resource-priority, siprec, 100rel#015#012Content-Length: 0#015#012Contact:
<sip:metaswitch at 196.12.170.244:5060;transport=udp>#015#012To: <
sip:metaswitch at 74.85.156.17:5060>#015#012P-NGCP-Src-Ip:
196.12.170.244#015#012P-NGCP-Src-Port: 5060#015#012P-NGCP-Src-Proto:
udp#015#012P-NGCP-Src-Af: 4#015#012P-Sock-Info: udp:
74.85.156.17:5060#015#012#015#012>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/parse_via.c:2712]:
parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP
196.12.170.244:5060;>
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:125]:
get_hdr_field(): ERROR: get_hdr_field: bad via
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [msg_translator.c:2329]:
build_res_buf_from_sip_req(): alas, parse_headers failed
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:329]:
parse_headers(): ERROR:parse_headers: memory allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: pv [pv_core.c:436]:
pv_get_to_attr(): cannot parse To header
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:329]:
parse_headers(): ERROR:parse_headers: memory allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:329]:
parse_headers(): ERROR:parse_headers: memory allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:329]:
parse_headers(): ERROR:parse_headers: memory allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [parser/msg_parser.c:329]:
parse_headers(): ERROR:parse_headers: memory allocation error
Sep 23 17:13:01 sip proxy[13417]: ERROR: <core> [msg_translator.c:2329]:
build_res_buf_from_sip_req(): alas, parse_headers failed
Sep 23 17:13:01 sip proxy[13417]: WARNING: sanity [sanity.c:275]:
check_required_headers(): sanity_check(): check_required_headers(): failed
to send 400 via sl reply

-- 
*Abel Alejandro*

787 586 8313 | 787 705 0555
<joquendo at alliedtechnologygrouppr.com>

400 Calle Calaf 477
San Juan, PR 00918
aalejandro at alliedtechnologygrouppr.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160923/4d1c3405/attachment.html>