| Summary: | ASTERISK-18696: peer_iphash_cb empty address on sip reload | ||||
| Reporter: | rsw686 (rsw686) | Labels: | Regression | ||
| Date Opened: | 2011-10-08 16:49:58 | Date Closed: | 2011-10-31 15:22:55 | ||
| Priority: | Minor | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | Channels/chan_sip/General | ||
| Versions: | 1.8.8.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) full ( 1) peers_by_ip.diff | |||
| Description: | When issuing sip reload my log is filled with the below. The peer_iphash_cb: Empty address lines started occurring since upgrading from 1.8.7.0 to 1.8.8.0-rc1. The Lagged and Reachable messages occur on both versions and look to be a separate issue. {code} voip*CLI> sip reload Reloading SIP == Parsing '/etc/asterisk/sip.conf': == Found == Parsing '/etc/asterisk/sip_general_additional.conf': == Found == Parsing '/etc/asterisk/sip_general_custom.conf': == Found == Parsing '/etc/asterisk/sip_nat.conf': == Found == Parsing '/etc/asterisk/sip_registrations_custom.conf': == Found == Parsing '/etc/asterisk/sip_registrations.conf': == Found == Parsing '/etc/asterisk/sip_custom.conf': == Found == Parsing '/etc/asterisk/sip_additional.conf': == Found == Parsing '/etc/asterisk/sip_custom_post.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found == Using SIP TOS bits 96 == Using SIP CoS mark 4 [Oct 8 17:39:28] ERROR[17976]: chan_sip.c:29195 peer_iphash_cb: Empty address [Oct 8 17:39:28] ERROR[17976]: netsock2.c:440 ast_sockaddr_hash: Unknown address family '0'. [Oct 8 17:39:28] ERROR[17976]: chan_sip.c:29195 peer_iphash_cb: Empty address [Oct 8 17:39:28] ERROR[17976]: netsock2.c:440 ast_sockaddr_hash: Unknown address family '0'. Repeats a around 600 times for every sip peer == Parsing '/etc/asterisk/sip_notify.conf': == Found [Oct 8 17:39:31] NOTICE[17976]: chan_sip.c:20259 handle_response_peerpoke: Peer '1431' is now Lagged. (2234ms / 2000ms) [Oct 8 17:39:31] NOTICE[17976]: chan_sip.c:20259 handle_response_peerpoke: Peer '1523' is now Lagged. (2215ms / 2000ms) Repeats a around 250 times for every online sip peer.... [Oct 8 17:39:41] NOTICE[17976]: chan_sip.c:20259 handle_response_peerpoke: Peer '1523' is now Reachable. (16ms / 2000ms) [Oct 8 17:39:41] NOTICE[17976]: chan_sip.c:20259 handle_response_peerpoke: Peer '1529' is now Reachable. (21ms / 2000ms) Repeats a around 250 times for every online sip peer.... {code} | ||||
| Comments: | By: Paul Belanger (pabelanger) 2011-10-12 11:15:59.638-0500 Do you mind uploading a debug log? --- We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: rsw686 (rsw686) 2011-10-12 15:12:37.600-0500 I was able to reproduce this on a non production system. I've attached the debug log. The error is only occurring for devices with UNKNOWN status. {code} sip show peers Name/username Host Dyn Forcerport ACL Port Status 1000/1000 10.10.1.143 D N A 5060 OK (9 ms) 1001/1001 10.10.1.143 D N A 5061 OK (8 ms) 1002/1002 10.10.1.142 D N A 5060 OK (7 ms) 1003/1003 10.10.1.142 D N A 5061 OK (9 ms) 1050/1050 10.10.1.149 D N A 51460 OK (17 ms) 1051/1051 10.10.1.149 D N A 51460 OK (16 ms) 1052/1052 10.10.1.140 D N A 65462 OK (15 ms) 1053/1053 10.10.1.140 D N A 65462 OK (16 ms) 1060 (Unspecified) D N A 0 UNKNOWN 2001 (Unspecified) D N A 0 UNKNOWN 2028 (Unspecified) D N A 0 UNKNOWN 2030/2030 8.24.240.50 D N A 26878 OK (158 ms) {code} By: Terry Wilson (twilson) 2011-10-13 12:23:53.437-0500 I haven't been able to reproduce this. I'd be interested in why I can't. Any chance you could post a sample of your sip.conf (at least the general section, and an anonymized version of a peer that this problem happens with). In any case, I'm pretty sure I see where things could at least possibly go wrong, so I'll attach a patch. Please test it and let me know if it helps since you seem to be able to reproduce the issue at will. By: Terry Wilson (twilson) 2011-10-13 12:24:48.650-0500 Please let me know if peers_by_ip.diff fixes the problem for you. By: Michael Spiceland (mspiceland) 2011-10-18 09:55:56.729-0500 This issue has been closed. Due to a bug in the issue tracker system, we cannot actually mark it as so. By: Terry Wilson (twilson) 2011-10-18 09:56:55.585-0500 This issue should be closed, but due to a JIRA bug the option doesn't seem to exist. We're looking into it. Until then, just pretend this is closed. :-) By: Michael Spiceland (mspiceland) 2011-10-18 09:57:37.918-0500 I am changing the link type for the link to ASTERISK-18499, the master issue containing all of the blockers to 1.8.8.0. This will allow that master issue to still be closed, even though there is some internal bug in the issue tracker preventing this issue from being closed. | ||||