[arm-allstar] Supermon Causes Problems

Jamey Wright jamey.wright at charter.net
Thu Jul 12 20:37:27 EST 2018 

Actually, the 7330 can't control the TM-271 as a remote base at this time.
Dave is working on the code it isn't finished yet.  

I am controlling it through the whatever is in the ACID release from 2015.
Here is what is in the rpt.conf file:


; Serial port for control
ioport = /dev/ttyS1

; Radio Type                
remote = tm271 

; Function list from link                                          
functions = functions-remote  

; Function list from phone         
phone_functions = functions-remote

; Authorization level                                         
authlevel = 2        
;


So, basically, I am controlling via COM1.  What the underlying code is to
make this work, I don't know.

Looks like I will need a USB to serial adapter in addition to another Pi and
case.  Then some time to put it all on the bench and make it play.

Jamey - WR4JW


-----Original Message-----
From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
"Doug Crompton via arm-allstar"
Sent: Wednesday, July 11, 2018 22:25
To: ARM Allstar <arm-allstar at hamvoip.org>
Cc: Doug Crompton <wa3dsp at gmail.com>
Subject: Re: [arm-allstar] Supermon Causes Problems

Jamey,

   Yes, it would be very desirable to update. The code and especially
hamvoip code has come a very long way! You didn't mention how you control
your radio but the hamvoip code has hamlib which could do it but I don't
have any setup information on that. The SCOM controller could also control
it I believe.

In any event the hamvoip code has most everything you would need built-in
and many enhancements, bug fixes, and general improvements. You should give
it a try. It is very easy to install. If you have any questions don't
hesitate to get back to us. Code and lots of information are at hamvoip.org
I don't think you will be sorry you switched! Hey you could save $100
annually on your utility bills!


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Wed, Jul 11, 2018 at 11:04 PM, "Jamey Wright via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Old enough that I can't remember when I installed it.  However, 
> according to the acid-install.log file... March of 2015
>
> So, is ACID still updated or supported? The system has been very 
> stable and other than Supermon causing it to go nuts I don't have any
issues with it.
> I don't mind upgrading the system to a Pi3 but does the Pi version 
> support the TM-271 as a frequency agile remote base?
>
> Jamey - WR4JW
>
> -----Original Message-----
> From: David McGough [mailto:kb4fxc at inttek.net]
> Sent: Monday, July 09, 2018 19:32
> To: "Jamey Wright via arm-allstar" <arm-allstar at hamvoip.org>
> Cc: Jamey Wright <jamey.wright at charter.net>
> Subject: Re: [arm-allstar] Supermon Causes Problems
>
>
> 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
> >
>
>
> ---
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
>
> _______________________________________________
>
> 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

More information about the arm-allstar mailing list