• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 964
  • Last Modified:

Extraneous Logging in Asterisk –How to Stop

Hi all.

It seems I have non-stop logging of the following messages about every 60-seconds or so:

From: /var/log/asterisk/full

Apr 10 06:07:49 DEBUG[1396]: Setting NAT on RTP to 0
Apr 10 06:07:49 DEBUG[1396]: Stopping retransmission on '497a055045f468c916facc9c3d1bbe25@192.168.1.202' of Request 102: Found
Apr 10 06:07:51 DEBUG[1396]: Stopping retransmission on '695a165e20f45e0553a656db058c5eea@192.168.1.202' of Request 102: Found
Apr 10 06:07:56 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 06:08:05 DEBUG[1396]: Auto destroying call '52e98997-b437dec4@192.168.1.102'

Apr 10 06:08:44 DEBUG[1396]: Setting NAT on RTP to 0
Apr 10 06:08:44 DEBUG[1396]: Stopping retransmission on '10d72c33358886291961c3697c20e53c@192.168.1.202' of Request 102: Found
Apr 10 06:08:51 DEBUG[1396]: Stopping retransmission on '6d10188d2b1db034319d475e137145e5@192.168.1.202' of Request 102: Found
Apr 10 06:08:54 DEBUG[1396]: Manager received command 'Command'
Apr 10 06:08:54 DEBUG[1396]: Manager received command 'Command'
Apr 10 06:08:56 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 06:09:03 DEBUG[1396]: Auto destroying call '52e98997-b437dec4@192.168.1.102'

Is this normal behavior?   I have no idea of what it means, or how to turn it off.  Moreover, it doesn’t make the log file terribly useful, since you need to sift through all this nonsense just to find what you want.  I’ve tried turning verbosity down to 1, but it only affects what displays on the console.  All I want to see are the inbound/ outbound call processes –nothing else.  

Also… Why are all actions marked as DEBUG [1396]? This seems to be the current PID, but it stays the same for everything.   What good is this if you’re looking for the activity of a particular call?   For example, Postfix uses unique ID’s for each process, i.e.,:  postfix/smtpd[15066].  This makes it easy to track a particular action.   Is there any way to make Asterisk’s logging a little more useful, or at least quieter?

Any insight would be appreciated :)

Dave

Asterisk 1.5
Sipura SPA-3000
0
dholingw
Asked:
dholingw
  • 7
  • 5
1 Solution
 
Vinod_VijayanVinCommented:
>>Apr 10 06:08:54 DEBUG[1396]: Manager received command 'Command'
>>Apr 10 06:08:54 DEBUG[1396]: Manager received command 'Command'

Try to change the manager password in manager.conf if it wouldn't affect any other
applications running on remote m/c that is dependent on asterisk like FOP, AMP etc.


>>Asterisk 1.5
is it Asterisk 1.2.5 you meant?
0
 
dholingwAuthor Commented:
>Try to change the manager password in manager.conf if it wouldn't affect any other
applications running on remote m/c that is dependent on asterisk like FOP, AMP etc.

Thanks Vinod,

Hmmm… Not sure what or why you’re asking me to do this.  Yep, I have that file open.  It reads:


--------------------------------------------------------------------------
;
; Asterisk Call Management support
;
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0

[admin]
secret = amp111
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

#include manager_custom.conf

--------------------------------------------------------------------------------------------

Change the password from amp111?  What’s supposed to happen then?  

>is it Asterisk 1.2.5 you meant?

You see, Asterisk likes to be called many different things.  For example, on http://asteriskathome.sourceforge.net/, my version is referred to as 1.5.  Yet login to Asterisk at the shell and you’ll see:  Connected to Asterisk 1.0.9  It's just another wonderful way to confuse people :)

Many thanks,

Dave
0
 
Vinod_VijayanVinCommented:

Well Dave its your AMP application that is connecting to the Asterisk server.
If you are fine with stopping the AMP application then change the password.

Actually the AMP uses manager api that allows you to run applications on remote
m/cs that get the asterisk events and can also send events.
So whenever it happens you have the messages displayed on Asterisk CLI.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
Vinod_VijayanVinCommented:
>>Yet login to Asterisk at the shell and you’ll see:  Connected to Asterisk 1.0.9  It's just >>another wonderful way to confuse people

Asterisk@Home and Asterisk are different projects.

Asterisk@Home projects goal is to minimise the installation difficulty of Asterisk and other
applications that provide an interface to asterisk.
So it contains Asterisk, AMP, FOP and other packages.
the disadvantage beign that it cannot keep up with the new developments in asterik and
other packages and hence lagging behind and doesn't contain the lastest version of asterisk.

The current version of asterisk is 1.2.*
The version 1.2.* has many features and enhancements added over the 1.0.* version.
0
 
dholingwAuthor Commented:
Ouch!  That password change disabled my inbound 204 extension.   I just tried calling from my cell phone.  privacy-unident kicked it, so I left my name…  Asterisk says, please wait while connect your call… Music starts to play…   But my phone never rings ):

I did however, observe this in the console:

      -- Executing NoOp("Local/222@from-internal-514a,2", "Returned from dialparties with no extensions to call") in new stack
    -- Executing SetVar("Local/222@from-internal-514a,2", "DIALSTATUS=BUSY") in new stack
      Executing Macro("Local/222@from-internal-514a,2", "hangupcall") in new stack

I switched it back to the default amp111, and everything works again.   Did I muck up your instructions, or was this an unintended result?


Hey Vinod…   Maybe it would help if I understood what all of this redundant chatter meant:

Apr 10 04:02:34 DEBUG[1396]: Stopping retransmission on '2cbbc77f260ebdc57487a5065a1e7b13@192.168.1.202' of Request 102: Found
Apr 10 04:02:45 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 04:02:48 DEBUG[1396]: Stopping retransmission on '65053ae36e912f7844b59eaa6c4df531@192.168.1.202' of Request 102: Found
Apr 10 04:02:54 DEBUG[1396]: Manager received command 'Command'
Apr 10 04:02:54 DEBUG[1396]: Manager received command 'Command'
Apr 10 04:03:19 DEBUG[1396]: Auto destroying call '52e98997-b437dec4@192.168.1.102'
Apr 10 04:03:40 DEBUG[1396]: Setting NAT on RTP to 0
Apr 10 04:03:40 DEBUG[1396]: Stopping retransmission on '5d95d89d00ab20f5319be81153102ccb@192.168.1.202' of Request 102: Found
Apr 10 04:03:46 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 04:03:48 DEBUG[1396]: Stopping retransmission on '349e281424bb2aa216554fed69f89436@192.168.1.202' of Request 102: Found
Apr 10 04:04:17 DEBUG[1396]: Auto destroying call '52e98997-b437dec4@192.168.1.102'
Apr 10 04:04:35 DEBUG[1396]: Setting NAT on RTP to 0
Apr 10 04:04:35 DEBUG[1396]: Stopping retransmission on '71ce36797bc8b7da13e5e23c0d03c747@192.168.1.202' of Request 102: Found
Apr 10 04:04:46 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 04:04:48 DEBUG[1396]: Stopping retransmission on '22ecea4267f1973102c8d56161576ad2@192.168.1.202' of Request 102: Found
Apr 10 04:04:54 DEBUG[1396]: Manager received command 'Command'
Apr 10 04:04:54 DEBUG[1396]: Manager received command 'Command'
Apr 10 04:05:15 DEBUG[1396]: Auto destroying call '52e98997-b437dec4@192.168.1.102'
Apr 10 04:05:41 DEBUG[1396]: Setting NAT on RTP to 0
Apr 10 04:05:41 DEBUG[1396]: Stopping retransmission on '62e2ef7a00f0710363079bf754decaf2@192.168.1.202' of Request 102: Found
Apr 10 04:05:46 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 04:05:48 DEBUG[1396]: Stopping retransmission on '57f1ad7a19589f1a41ce220e775a5d65@192.168.1.202' of Request 102: Found
Apr 10 04:06:13 DEBUG[1396]: Auto destroying call '52e98997-b437dec4@192.168.1.102'
Apr 10 04:06:36 DEBUG[1396]: Setting NAT on RTP to 0

Could be a dumb question, but is the above normal?  This doesn’t indicate a problem with my configuration, does it?   All of the ‘above’  repeat babble is just normal operation?  Man.. What a mess of the log file this creates.  

I was hoping there was a way to remove the:

Apr 10 04:06:36 DEBUG[1396]: Stopping retransmission on '45f3d6d351e485e955a8799072f5153f@192.168.1.202' of Request 102: Found
Apr 10 04:06:46 DEBUG[1396]: Auto destroying call 'E60F28560F104975BAFA646C93AF2DE3@192.168.1.202'
Apr 10 04:06:48 DEBUG[1396]: Stopping retransmission on '218bd1b64fa011da32434b6e0d0ba355@192.168.1.202' of Request 102: Found

From showing up every 60-seconds.  Maybe turn the verbosity down?  

In the manager.conf file, how about this stuff:

read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

If you play around with these, can you change the verbosity of the logging?  Sorry if I’m somehow misunderstanding or confusing this whole thing.  

Dave
0
 
dholingwAuthor Commented:
Going to hold off on this momentarily.  Loading up 2.8 to see if I have better luck.  Had issues with 2.7, but let’s see if they’re fixed.   Should be running a newer version anyway, so let’s see what happens.    Will report back to this posting shortly.  

D.    
0
 
dholingwAuthor Commented:
Alright… From everything I’ve tried, it looks as if this chatter is normal –even with Asterisk sitting in an idle state.  Short of killing logging completely, I don’t think there’s a way to silence these extraneous entries.

Thanks,

D.  
0
 
Vinod_VijayanVinCommented:

start asterisk in silent mode.

normally asterisk is started as

asterisk -v

where the option v stands for verbose output
If we specify more v's we get more verbose output from asterisk.

i.e specifying  asterisk -vvvvvv shows more output than asterisk -v

so to turn asterisk in silent mode just start asteruik with the asterisk command.
0
 
dholingwAuthor Commented:
Heh… I just tried a bunch of different startup commands.  There seems to be no happy medium.  I tried Asterisk –v.  This starts it with odd looking results and then it just hangs there.  It’s certainly started, but you can’t enter anything else at the command line.  

Ok.. Let’s fool around with the verbosity setting.  Try verbose 1. Yep, this kills everything.  Let’s try verbose 2.   Urrr… Now we get this again at idle.

Apr 17 07:50:02 DEBUG[26206] chan_sip.c: Stopping retransmission on '7f9ccc192ec51a724612008b362dbfbb@192.168.1.202' of Request 102: Match Found
Apr 17 07:50:06 DEBUG[26206] chan_sip.c: Stopping retransmission on '131295d22378654e7417a1c40613bccc@192.168.1.202' of Request 102: Match Found
Apr 17 07:50:13 DEBUG[26206] chan_sip.c: Auto destroying call 'BE9B9F50CF844F7D83731D175A76012A@192.168.1.202'
Apr 17 07:51:06 DEBUG[26206] chan_sip.c: Stopping retransmission on '32f107013fe1381a4dacc75d05fc94c6@192.168.1.202' of Request 102: Match Found
Apr 17 07:51:08 DEBUG[26206] chan_sip.c: Stopping retransmission on '34cd30142717d86519ec8ae017c415b1@192.168.1.202' of Request 102: Match Found
Apr 17 07:51:14 DEBUG[26206] chan_sip.c: Auto destroying call 'BE9B9F50CF844F7D83731D175A76012A@192.168.1.202'

Seriously man, I think it’s Asterisk’s strange idea of a log file.  If you want any logging at all, then expect the above chatter everything 60-seconds or less in the background.  It makes a total mess, and makes looking for stuff exceptionally difficult.  Part of the problem could be 2.8-beta, but WOW... What a total mess.

 Furthermore, starting Asterisk with –v, or –vv, etc results in bizarre startup logs –each of them uniquely different.   I mean bizarre, in that all sorts whacky error message about stuff being misconfigured, or just plain not starting.  Of course… All is well, and it runs fine.  In any event, I’m sure the developers have some master plan in mind here, but whatever that may be is beyond my comprehension I suppose.    
0
 
dholingwAuthor Commented:
Hey Vinod… Thanks for all the help.  You’re suggestions resulted in me trying a bunch of other commands, thus concluding that maybe there is a way to get the log file to behave normally, but I think we’ve done all we can in terms of trying.  It’s not worth filling up 20-pages on EE over it.   I’ve seen other complaints about this, and I’m sure they’ll consider revising it in future versions.  

Thanks again!

Dave  
0
 
Vinod_VijayanVinCommented:
>>It’s certainly started, but you can’t enter anything else at the command line

try
asterisk -vc

The above presents you with a CLI as c stands for colsole mode.

Checkout more asterisk options here:-
http://www.voip-info.org/wiki/view/Asterisk+options
0
 
dholingwAuthor Commented:
This is an interesting one too.  It disables logging –no entries in the log file, but the console in this case displays some odd stuff.  I just called my wireless phone.  Check this out:

Asterisk –vc


*CLI>   recordingcheck|20060417-092423|1145280263.0: Inbound recording not enabled
  dialparties.agi: Caller ID name is 'Wireless' number is '2000'
  dialparties.agi: Methodology of ring is  'none'
Argument "noresponse" isn't numeric in numeric eq (==) at /var/lib/asterisk/agi-bin/dialparties.agi line 83, <STDIN> line 43.
Use of uninitialized value in length at /var/lib/asterisk/agi-bin/dialparties.agi line 129, <STDIN> line 51.
Use of uninitialized value in concatenation (.) or string at /var/lib/asterisk/agi-bin/dialparties.agi line 135, <STDIN> line 54.
  dialparties.agi: Extension 204 is available...skipping checks
Argument "" isn't numeric in numeric ne (!=) at /var/lib/asterisk/agi-bin/dialparties.agi line 167, <STDIN> line 59.

Hahah… More Asterisk gibberish.   I have no idea what this is, or why the Asterisk –vc would result in a bizarre message like the above. The extension is just fine, and functions as it should.   I’m sure if we try another Asterisk command (at least in 2.8), we’ll get another barrage of insane messages.  

Many thanks,

Dave
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now