| Summary: | ASTERISK-25092: xmpp connection failure causes continuous error messages | ||
| Reporter: | Cam (cam) | Labels: | |
| Date Opened: | 2015-05-15 04:26:56 | Date Closed: | 2015-06-03 14:57:13 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_xmpp |
| Versions: | 11.17.1 | Frequency of Occurrence | One Time |
| Related Issues: | |||
| Environment: | FreePBX Distro 12.0.64 | Attachments: | |
| Description: | One of the users on my system changed the password on his Google Voice account without telling me first. This caused Asterisk to be unable to connect, and when I went to the CLI it was streaming a continuous wall of text with error messages. It was scrolling so quickly that I could barely read it, let alone copy the error messages to paste them here as I would have liked to. Once I got the new password from the user and entered it the errors stopped, but in the meantime it had created a huge log file, which contains a huge block of repeating lines like these:
{noformat} [2015-05-14 21:52:43] ERROR[1791] res_xmpp.c: xmpp_action_hook was called without a packet [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: Parsing failure: Hook returned an error. [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: JABBER: socket read error [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: Parsing failure: Hook returned an error. [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: Parsing failure: Invalid XML. [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: JABBER: socket read error [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: Parsing failure: Hook returned an error. [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: Parsing failure: Invalid XML. [2015-05-14 21:52:43] WARNING[1791] res_xmpp.c: JABBER: socket read error [2015-05-14 21:52:44] WARNING[1791] res_xmpp.c: Parsing failure: Hook returned an error. [2015-05-14 21:52:44] WARNING[1791] res_xmpp.c: Parsing failure: Invalid XML. (...the last three lines just keep repeating until the system was rebooted...) {noformat} This apparently drove the CPU usage so high that I had to reboot the system to gain control. I can understand Asterisk warning periodically about a failure, but note that none of these lines indicate the actual cause of the failure (incorrect password), and in any event they should not repeat continuously, but instead should be sent at a MUCH less frequent interval. | ||
| Comments: | By: Rusty Newton (rnewton) 2015-05-19 19:14:42.269-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2015-06-03 14:57:05.108-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||