[arm-allstar] Supermon manager error

[Andy KB7B]

Rory,
You might look in /var/log/apache2/ (or wherever it is on hamvoip) before and after you bring up supermon. It's been a while since I found the "!" problem for a friend, but I think the apache logs gave me a cryptic clue.


-Andy

      From: Rory Bowers via arm-allstar <arm-allstar at hamvoip.org>
 To: ARM Allstar <arm-allstar at hamvoip.org> 
Cc: Rory Bowers <k6cks01 at gmail.com>
 Sent: Friday, May 11, 2018 7:38 PM
 Subject: Re: [arm-allstar] Supermon manager error
   
Thanks Andy... I hate exclamation points in passwords, I wouldn't do that.
But thanks for the tip!!

Rory, K5CKS

On Fri, May 11, 2018 at 12:25 PM, "Andy KB7B via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Rory,
> Make sure you do not use an exclamation point ! in your manager
> password.Asterisk can handle it, but allmon2/supermon can't.
>
> -Andy, KB7B42432
>
>      From: Rory Bowers via arm-allstar <arm-allstar at hamvoip.org>
>  To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Rory Bowers <k6cks01 at gmail.com>
>  Sent: Friday, May 11, 2018 5:27 PM
>  Subject: Re: [arm-allstar] Supermon manager error
>
> Thanks Doug,
> Here is my allmon.ini...
>
> [48089]
> host=70.178.132.224:5038
> user=admin
> passwd=(my password)
> menu=yes
> hideNodeURL=no
> [48135]
> host=70.178.132.224:5038
> user=admin
> passwd=(my password again)
> menu=yes
> hideNodeURL=no
>
>
> [All Nodes]
> nodes=48089, 48135
> menu=yes
>
> [lsNodes]
> url="/cgi-bin/lsnodes_web?node=48089"
> menu=yes
>
> [IRLP Status]
> url="http://status.irlp.net"
> menu=yes
>
> [HAMVOIP]
> url="http://HamVOIP.org"
> menu=yes
>
> Here is where I get a little fuzzy... my manager.conf file
>
> [general]
>
> displaysystemname = yes
>
> enabled = yes
>
> webenabled = yes
>
> port = 5038
>
>
>
> httptimeout = 60
>
> ; a) httptimeout sets the Max-Age of the http cookie
>
> ; b) httptimeout is the amount of time the webserver waits
>
> ;    on a action=waitevent request (actually its httptimeout-10)
>
> ; c) httptimeout is also the amount of time the webserver keeps
>
> ;    a http session alive after completing a successful action
>
>
>
> bindaddr = 192.168.0.2  ; Local interface only!
>
> ;bindaddr = 0.0.0.0    ; Not secure
> ;
> displayconnects = yes
>
> ;
>
> ; Add a Unix epoch timestamp to events (not action responses)
>
> ;
>
> timestampevents = yes
>
>
>
> [admin]
>
> secret = (my password again)
>
> read = all,system,call,log,verbose,command,agent,user,config
>
> write = all,system,call,log,verbose,command,agent,user,config
>
> The bindaddr is set to the lan ip address of the Pi... not the Public ip
> address.  Is this correct??
>
> Rory, K5CKS
>
> On Fri, May 11, 2018 at 8:43 AM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Rory,
> >
> >  The message about the Supermon error did not go out because it had a
> > graphics file in it. So I am answering without your original message.
> >
> > If you cannot connect to the manager it is usually a problem with
> > authentication. You allmon.ini file must have a stanza or stanza's that
> > contain the nodes you want to view and a user/pass to the manager. Here
> is
> > an example:
> >
> > [40000]
> > host=127.0.0.1:5038
> > user=admin
> > passwd=managerpass
> > menu=yes
> > hideNodeURL=no
> >
> > The /etc/asterisk/manager.conf file credentials must match this -
> >
> > [admin]
> >
> > secret = managerpass
> >
> > In both places change the password to one of your choice. They MUST
> match!
> >
> > In addition if you are trying to manager a node on a different server the
> > host address in that stanza must be the IP address of that server and
> very
> > important the bindaddress must be changed in not on that server.
> >
> > bindaddr = 127.0.0.1  ; Local interface
> > only!
> > ;bindaddr = 0.0.0.0    ; Not secure
> >
> > The above would be correct for nodes on the server you are running
> Supermon
> > on but if you are trying to manage a node on another server you would
> need
> > to comment out the 127.0.0.1 address and un-comment the 0,0,0,0 address.
> If
> > the server address you were managing was out on the Internet then in
> > addition you would need to port forward the manager port and also
> institute
> > a firewall rule.
> >
> > All of this is covered in the howto found on the hamvoip.org web page.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3 web page - http://hamvoip.org