#43 ✓resolved
ronin-9952 (at lighthouseapp)

AMI failed authentication consumes 100% CPU

Reported by ronin-9952 (at lighthouseapp) | December 17th, 2008 @ 07:01 PM

If AMI authentication fails, asterisk drops the socket, but adhearsion doesn't catch that and repeatedly reads from the socket in a tight loop.

Comments and changes to this ticket

  • Jay Phillips

    Jay Phillips December 18th, 2008 @ 03:03 PM

    • State changed from “new” to “open”
  • Jay Phillips
  • Ben Klang

    Ben Klang July 30th, 2010 @ 12:19 PM

    • State changed from “open” to “resolved”
    • Milestone order changed from “0” to “0”

    This seems to have been fixed at some point in the past. Should authentication fail now, an exception is raised:

    DEBUG ami: Sending AMI action: 
    >>> Action: login
    >>> ActionID: uruyVaLv-LqAS-KOzU-FZ4m-Dtci5YlUSZNu
    >>> Username: adhearsion
    >>> Secret: the_wrong_password
    >>> Events: Off
    ERROR ami: Error connecting to AMI! #<Adhearsion::VoIP::Asterisk::Manager::ManagerInterface::AuthenticationFailedException: Incorrect username and password! Authentication failed>
    ERROR ami: AMI connection for ACTION disconnected !!!
    [Fri Jul 30 12:18:32 2010] Adhearsion::VoIP::Asterisk::AGI::Server::RubyServer start

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket