[arm-allstar] Supermon Causes Problems

[David McGough]

How old is your ACID software????  There have been a number of AMI 
changes, enhancements and bugs fixed.  Supermon takes advantage of these 
new features....


On Mon, 9 Jul 2018, "Jamey Wright via arm-allstar" wrote:

> I have just loaded my first Pi with the latest image.  I ran all of the
> updates and everything seems good.  I went back to the HamVoIP site and was
> reading further and decided to play with Supermon. I set up everything
> according to the documentation. I then decided to expand it further and add
> my other nodes.  The first node I added was my Conference/Echolink node
> which runs as a virtual machine in a data center and is using the DIAL
> distro.  Still, no problems.  Then I decided to  add my other node.  It is
> running ACID on a Pent IV with a gig of RAM.  It runs 2 nodes.  The first
> node is connected to a port of a SCOM 7330 repeater controller.  It is
> always connected to the Conference node over a private LAN/WAN connection.
> The other node is a 2M remote base using a TM-271.  The repeater node is
> public and the 2M remote base is private.  When Supermon starts trying to
> connect to the manager on the ACID node, the connection starts disconnecting
> and reconnecting.  I looged into it va SSH and the following was being
> dumped to the console:
> 
>  
> 
> ]0;root at JWAllstar:~[root at JWAllstar ~]# /usr/sbin/safe_asterisk: line 125:
> 20433 Segmentation fault      (core dumped) nice -n $PRIORITY
> ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
> 
> Asterisk ended with exit status 139
> 
> Asterisk exited on signal 11.
> 
> Automatically restarting Asterisk.
> 
> mpg123: no process killed
> 
> /usr/sbin/safe_asterisk: line 125: 20517 Segmentation fault      (core
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS}
> >&/dev/${TTY} < /dev/${TTY}
> 
> Asterisk ended with exit status 139
> 
> Asterisk exited on signal 11.
> 
> Automatically restarting Asterisk.
> 
> mpg123: no process killed
> 
>  
> 
> I restarted Asterisk and managed to catch the following on the console:
> 
>  
> 
> [KJWAllstar*CLI> 
> 
>   == Parsing '/etc/asterisk/gps.conf':  Found
> 
> [KJWAllstar*CLI> 
> 
>   == Parsing '/etc/asterisk/manager.conf':  Found
> 
> [KJWAllstar*CLI> 
> 
>   == Manager 'admin' logged on from 68.190.4.101
> 
> [KJWAllstar*CLI> 
> 
> Disconnected from Asterisk server
> 
> /usr/sbin/safe_asterisk: line 125: 20601 Segmentation fault      (core
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS}
> >&/dev/${TTY} < /dev/${TTY}
> 
> Asterisk ended with exit status 139
> 
> Asterisk exited on signal 11.
> 
> Executing last minute cleanups
> 
> ]0;root at JWAllstar:~[root at JWAllstar ~]# Automatically restarting Asterisk.
> 
> mpg123: no process killed
> 
>  
> 
> ]0;root at JWAllstar:~[root at JWAllstar ~]# 
> 
> ]0;root at JWAllstar:~[root at JWAllstar ~]# service asterisk stop
> 
> Shutting down asterisk: Asterisk ended with exit status 0
> 
> Asterisk shutdown normally.
> 
> [60G[[0;32m  OK  [0;39m]
> 
> ]0;root at JWAllstar:~[root at JWAllstar ~]#
> 
>  
> 
> Any insight into this?  Is ACID too old to work with Supermon?  I like the
> ability to monitor and control the nodes using Supermon so I'm hoping the
> fix is simple.
> 
>  
> 
> Thanks
> 
>  
> 
> Jamey Wright - WR4JW
> 
>  
> 
> _______________________________________________
> 
> 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
>