[asterisk-bugs] [JIRA] (ASTERISK-25092) xmpp connection failure causes continuous error messages

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-25092:
---------------------------------------

    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 even they should not repeat continuously, but instead should be sent at a MUCH less frequent interval.

  was:
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:

[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...)

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 even they should not repeat continuously, but instead should be sent as MUCH less frequent intervals.


> xmpp connection failure causes continuous error messages
> --------------------------------------------------------
>
>                 Key: ASTERISK-25092
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25092
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_xmpp
>    Affects Versions: 11.17.1
>         Environment: FreePBX Distro 12.0.64
>            Reporter: Cam
>
> 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 even they should not repeat continuously, but instead should be sent at a MUCH less frequent interval.



--
This message was sent by Atlassian JIRA
(v6.2#6252)