Ken Williams
2007-Mar-06 13:44 UTC
[asterisk-users] Manager.conf '127.0.0.1 unable to authenticate'
Every few seconds I get the following message: == Parsing '/etc/asterisk/manager.conf': Found == Connect attempt from '127.0.0.1' unable to authenticate I'm trying to track down where it's coming from. I've used TCPDUMP & NGREP to monitor 127.0.0.1, no data's flowing. I've tried loading Asterisk with no modules, tried loading with a naked manager.conf (only lines are [general] & enabled=yes). I've cleaned out /var/lib/asterisk. My full log shows the following every attempt: [Mar 6 13:32:39] DEBUG[28578] manager.c: Manager received command 'Challenge' [Mar 6 13:32:39] DEBUG[28578] manager.c: Manager received command 'Login' [Mar 6 13:32:39] VERBOSE[28578] logger.c: == Parsing '/etc/asterisk/manager.conf': [Mar 6 13:32:29] VERBOSE[28567] logger.c: Found [Mar 6 13:32:40] VERBOSE[28578] logger.c: == Connect attempt from '127.0.0.1' unable to authenticate I've updated from 1.2.13 to 1.4.1 and done everything I could to remove Trixbox from the picture. I thought for sure it was a module, but moving them all out of the picture didn't alleviate the problem. It seems as long as manager.conf exists I'm getting these messages. I've got 3 boxes setup with mostly identical setups (extensions.conf is different) and only one box is getting this message. From what I can tell from google searches it appears astbill and/or trixbox are likely to blame but I'm running out of places to look for these culprits. Any suggestinos would be greatly appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070306/e1329f35/attachment.htm
Alex Robar
2007-Mar-06 13:57 UTC
[asterisk-users] Manager.conf '127.0.0.1 unable to authenticate'
Hi Ken, Trixbox comes with the Flash Operator Panel. The FOP server is likely setup with incorrect authentication parameters, and hence is failing authentication everytime it attempts to use the Asterisk Manager API to update it's tracking of what's going on in your system. Check your op_server.cfg file (/var/www/html/panel/, I think). Look for the manager_user and manager_secret parameters, and make sure they match an entry in /etc/asterisk/manager.conf. Alex On 3/6/07, Ken Williams <ken@intermountainelectronics.com> wrote:> > Every few seconds I get the following message: > > * == Parsing '/etc/asterisk/manager.conf': Found > == Connect attempt from '127.0.0.1' unable to authenticate > * > I'm trying to track down where it's coming from. > > I've used TCPDUMP & NGREP to monitor 127.0.0.1, no data's flowing. > > I've tried loading Asterisk with no modules, tried loading with a naked > manager.conf (only lines are [general] & enabled=yes). > > I've cleaned out /var/lib/asterisk. > > My full log shows the following every attempt: > > *[Mar 6 13:32:39] DEBUG[28578] manager.c: Manager received command > 'Challenge' > [Mar 6 13:32:39] DEBUG[28578] manager.c: Manager received command 'Login' > [Mar 6 13:32:39] VERBOSE[28578] logger.c: == Parsing > '/etc/asterisk/manager.conf': [Mar 6 13:32:29] VERBOSE[28567] logger.c: > Found > [Mar 6 13:32:40] VERBOSE[28578] logger.c: == Connect attempt from ' > 127.0.0.1' unable to authenticate > * > I've updated from 1.2.13 to 1.4.1 and done everything I could to remove > Trixbox from the picture. I thought for sure it was a module, but moving > them all out of the picture didn't alleviate the problem. It seems as long > as manager.conf exists I'm getting these messages. I've got 3 boxes setup > with mostly identical setups (extensions.conf is different) and only one > box is getting this message. From what I can tell from google searches it > appears astbill and/or trixbox are likely to blame but I'm running out of > places to look for these culprits. > > Any suggestinos would be greatly appreciated. > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >-- Alex Robar alex.robar@gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070306/422ef9b4/attachment.htm
Ken Williams
2007-Mar-06 14:27 UTC
[asterisk-users] Manager.conf '127.0.0.1 unable to authenticate'
That was indeed the problem. I thought I had eliminated any httpd by disabling the service, but the problem was trixbox was still trying to load on startup via /usr/sbin/amportal. Once I removed that from startup, problem resolved. I did go a step further and wipe out the panel in httpd as well. Thanks for the pointer. ________________________________ From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Alex Robar Sent: Tuesday, March 06, 2007 1:57 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Manager.conf '127.0.0.1 unable to authenticate' Hi Ken, Trixbox comes with the Flash Operator Panel. The FOP server is likely setup with incorrect authentication parameters, and hence is failing authentication everytime it attempts to use the Asterisk Manager API to update it's tracking of what's going on in your system. Check your op_server.cfg file (/var/www/html/panel/, I think). Look for the manager_user and manager_secret parameters, and make sure they match an entry in /etc/asterisk/manager.conf. Alex On 3/6/07, Ken Williams <ken@intermountainelectronics.com> wrote: Every few seconds I get the following message: == Parsing '/etc/asterisk/manager.conf': Found == Connect attempt from '127.0.0.1' unable to authenticate I'm trying to track down where it's coming from. I've used TCPDUMP & NGREP to monitor 127.0.0.1, no data's flowing. I've tried loading Asterisk with no modules, tried loading with a naked manager.conf (only lines are [general] & enabled=yes). I've cleaned out /var/lib/asterisk. My full log shows the following every attempt: [Mar 6 13:32:39] DEBUG[28578] manager.c: Manager received command 'Challenge' [Mar 6 13:32:39] DEBUG[28578] manager.c: Manager received command 'Login' [Mar 6 13:32:39] VERBOSE[28578] logger.c: == Parsing '/etc/asterisk/manager.conf': [Mar 6 13:32:29] VERBOSE[28567] logger.c: Found [Mar 6 13:32:40] VERBOSE[28578] logger.c: == Connect attempt from '127.0.0.1' unable to authenticate I've updated from 1.2.13 to 1.4.1 and done everything I could to remove Trixbox from the picture. I thought for sure it was a module, but moving them all out of the picture didn't alleviate the problem. It seems as long as manager.conf exists I'm getting these messages. I've got 3 boxes setup with mostly identical setups (extensions.conf is different) and only one box is getting this message. From what I can tell from google searches it appears astbill and/or trixbox are likely to blame but I'm running out of places to look for these culprits. Any suggestinos would be greatly appreciated. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Alex Robar alex.robar@gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070306/de2a7989/attachment.htm