Summary:	ASTERISK-20930: Wrong password for google voice eventually causes asterisk to crash
Reporter:	sharan h (sharkbitz)	Labels:
Date Opened:	2013-01-12 22:13:53.000-0600	Date Closed:	2013-02-27 18:51:48.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Resources/res_xmpp
Versions:	11.0.2 11.1.2	Frequency of Occurrence	Constant
Related Issues:
Environment:	Linux	Attachments:
Description:	Wrong password or locked account for gmail generates the following errors nonstop in console: [Jan 12 23:06:00] WARNING[14120]: res_xmpp.c:3531 xmpp_client_receive: Parsing failure: Hook returned an error. [Jan 12 23:06:00] WARNING[14120]: res_xmpp.c:3528 xmpp_client_receive: Parsing failure: Invalid XML. [Jan 12 23:06:00] WARNING[14120]: res_xmpp.c:3590 xmpp_client_thread: JABBER: socket read error [Jan 12 23:06:00] WARNING[14120]: res_xmpp.c:3531 xmpp_client_receive: Parsing failure: Hook returned an error. [Jan 12 23:06:00] WARNING[14120]: res_xmpp.c:3528 xmpp_client_receive: Parsing failure: Invalid XML. [Jan 12 23:06:00] WARNING[14120]: res_xmpp.c:3590 xmpp_client_thread: JABBER: socket read error Eventually, asterisk completely crashes.
Comments:	By: Matt Jordan (mjordan) 2013-01-13 14:36:49.855-0600 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace Please also enable XMPP debugging and attach a DEBUG log file illustrating the XMPP messages received by the Asterisk instance leading up to the crash. By: Rusty Newton (rnewton) 2013-01-31 14:02:57.260-0600 Can you provide the requested debug? Or at least your sanitized configuration files (xmpp.conf) so that we can reproduce this? By: Rusty Newton (rnewton) 2013-02-27 18:51:48.839-0600 I can't reproduce this after several minutes of res_xmpp attempting with the wrong password. If you can't provide the backtrace, then we'll close this for now as it's a situation no one should realistically run into. A bad password doesn't suddenly happen, and why would you let Asterisk sit there for a long time without fixing the issue? When you can provide the backtrace or more information as to how long or how the crash happens, we can re-open.