Bug #371

AM: uses massive amounts of memory

Added by Christoph Dwertmann over 1 year ago. Updated 2 months ago.

Status:New Start date:30/08/2010
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:OMF Software
Target version:-

Description

Today the ruby process of the 5.3 AM reached more than 2GB of physical memory usage and caused norbit to swap heavily. The log file shows:

2010-08-30 14:40:48 DEBUG service::web: WEBrick::HTTPServlet::ProcHandler is invoked.
2010-08-30 14:40:49 DEBUG service::web: close: 203.143.174.94:52291
2010-08-30 14:43:48 DEBUG service::web: accept: 203.143.174.94:46535
2010-08-30 14:43:49 DEBUG service::web: accept: 203.143.174.94:47804
2010-08-30 14:43:53 WARN service::OMF::XMPP::Connection: Trying to ping XMPP server: execution expired
2010-08-30 14:43:55 WARN service::OMF::XMPP::Connection: Error(2) pinging XMPP server
2010-08-30 14:43:57 DEBUG service::web: WEBrick::HTTPServlet::ProcHandler is invoked.
2010-08-30 14:43:57 DEBUG service::web: WEBrick::HTTPServlet::ProcHandler is invoked.
2010-08-30 14:45:33 WARN service::OMF::XMPP::Connection: Trying to ping XMPP server: execution expired
2010-08-30 14:45:38 WARN service::OMF::XMPP::Connection: Error(3) pinging XMPP server
2010-08-30 14:46:41 WARN service::OMF::XMPP::Connection: Trying to ping XMPP server: not owner
2010-08-30 14:46:43 WARN service::OMF::XMPP::Connection: Error(4) pinging XMPP server
2010-08-30 14:47:27 WARN service::OMF::XMPP::Connection: Trying to ping XMPP server: not owner
2010-08-30 14:47:28 WARN service::OMF::XMPP::Connection: Error(5) pinging XMPP server
2010-08-30 14:48:03 WARN service::OMF::XMPP::Connection: Trying to ping XMPP server: not owner
2010-08-30 14:48:07 WARN service::OMF::XMPP::Connection: Error(6) pinging XMPP server
2010-08-30 14:48:09 WARN service::OMF::XMPP::Connection: Reached XMPP server ping retry limit -- disconnected from server
2010-08-30 14:55:06 DEBUG service::web: accept: 203.143.174.94:37561
2010-08-30 14:55:42 DEBUG service::web: WEBrick::HTTPServlet::ProcHandler is invoked.

Apparently the connection to XMPP was lost, although ejabberd is running fine and accepts connections. A restart of the AM resolved the issue. However, we should have a closer look what happens when the XMPP connection is lost, why it didn't reconnect and why the memory usage exploded.

History

#1
Updated by Christoph Dwertmann over 1 year ago

I was able to reproduce this situation by restarting ejabberd. The AM does not reconnect successfully and prints "Reached XMPP server ping retry limit -- disconnected from server". However this time there was no memory leak.

#2
Updated by Jolyon White about 1 year ago

  • Status changed from New to Assigned
  • Assignee set to Jolyon White

#3
Updated by Christoph Dwertmann 2 months ago

  • Status changed from Assigned to New
  • Assignee deleted (Jolyon White)

Also available in: Atom PDF