Summary:ASTERISK-08503: Console interface (-r) stops operating, with logging
Reporter:Brad Templeton (bradtem)Labels:
Date Opened:2007-01-05 14:50:48.000-0600Date Closed:2007-01-05 17:34:43.000-0600
Versions:Frequency of
Description:After a few days of operation, with no pattern I have yet to discern, the asterisk CLI console fails to operate.  If you do asterisk -r it reports "Connected to Asterisk SVN-trunk-r49074M currently running on main (pid = 26042)" and provides a CLI prompt, and you can type commands, and you get no output.  Hitting tab (command name completion) causes the session to hang.   Furthermore, it appears that logging has stopped.  In my case /var/log/asterisk/messages stops mid-message about 10 hours ago.  However, the CLI stopped working only an hour ago.   The last command typed to the CLI with success was "sip show channels"

The system is operating.  Calls work.  You can connect to the manager interface.

Sorry, I wish I had better reproducability.   The only way out so far is to kill and restart asterisk.  "Stop now" does nothing and I presume it's not really listening.  Note that when starting it does not report the current debug and verbosity levels, just the version number.

With logging also stopping this will be fun to track down, but it's severe as I need the CLI and that means regular hard restarts.
Comments:By: Brad Templeton (bradtem) 2007-01-05 14:54:49.000-0600

Whoops, I take it back.  I can reliably reproduce.  It is in fact "sip show channels" that causes the freeze up.

It outputs this:

Peer             User/ANR    Call ID      Seq (Tx/Rx)  Form  Hold     Last Message  
0 active SIP channels

I can continue to issue other commands and they work.  However, if I exit the CLI and enter it again, after issuing this command, I have lost the CLI.   And logging also freezes, perhaps I can turn off buffering on logging somehow to help if you can't reproduce?

By: Joshua C. Colp (jcolp) 2007-01-05 16:06:22.000-0600

There's something that needs clarification:

Is this trunk, or 1.4? Trunk has a non-blocking logger now while 1.4 does not.

By: Brad Templeton (bradtem) 2007-01-05 17:05:32.000-0600

It is as checked out of snv trunk on Dec 31.   I must admit, I am finding much less stability in the release-era trunk than I was with trunk from back in the summer or 1.2.   I've been seeing this bug since december and only today found out how to replicate it.  I'm also seeing random crashes of other sorts.  I may have to create a more production system but then I won't duplicate the bugs alas.   I'm trying to figure out how to blame my environment, but the summer 1.4 trunk was pretty stable, so work needs to be done to track down the causes.

By: Joshua C. Colp (jcolp) 2007-01-05 17:08:02.000-0600

I'm slightly confused and can't tell which you are using... trunk is where all active development happens, branches are feature frozen and only bug fixes go in there. Can you give me the SVN checkout line you are using?

By: Brad Templeton (bradtem) 2007-01-05 17:27:37.000-0600

1477 main>asterisk$ svn info
Path: .
URL: http://svn.digium.com/svn/asterisk/trunk
Repository UUID: 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Revision: 49411
Node Kind: directory
Schedule: normal
Last Changed Author: russell
Last Changed Rev: 49389
Last Changed Date: 2007-01-03 20:35:44 -0800 (Wed, 03 Jan 2007)
Properties Last Updated: 2007-01-03 22:24:13 -0800 (Wed, 03 Jan 2007)

Sigh.  I just recompiled so it's 49389 (I thought I had done so before but I must have forgotten to do a make clean) and now it is not duplicating.  Will report again if it happens again.

BTW I had been under the impression that trunk just after a major release was pretty close to the release, though it has some extra risk.  I was getting this bug before release, so perhaps it was cured recently.  My apologies.

(Another new thing I just did was use gcc4.0 and distcc to compile instead of gcc3.4 which is the asterisk box's stock gcc)

Looks like we may call it resolved for now.  I will re-open if it happens again.

By: Joshua C. Colp (jcolp) 2007-01-05 17:34:42.000-0600

Issue has been fixed. If you want to run 1.4 you can grab it via http://svn.digium.com/svn/asterisk/branches/1.4 - and while it's true that trunk and 1.4 are close once branched, 1.4 has been branched for a few months so trunk is quite different now.