August 2019 - App_rpt-users - lists.keekles.org

Call for Volunteers
by Tim Sawyer 26 Aug '19

26 Aug '19

Bryan Fields, W9CR has resigned from AllStarLink. In Byran’s absence we are actively looking for volunteers who love AllStar and have skillsets including programming in C, SQL, and Web design. We have lots of other ways folks can help out. Please reply to this list or contact kuggie at kuggie dot com to let us know if you’d like to help out in some way. Thank you, AllStarLink Board Pete Elke WI6H Kevin Custer W3KKC Todd Lesser KM6RPT Tim Sawyer WD6AWP Dave Shaw WB6WTM -- Tim WD6AWP

6 5

unsubscibe
by Jim Hertel 24 Aug '19

24 Aug '19

1 0

AllStar Outage
by Tim Sawyer 20 Aug '19

20 Aug '19

The AllStar website is experiencing an outage. This began at 1655 PDT 8/20/19. We are working to correct the problem. Thank you for paticents. -- Tim WD6AWP

1 1

Asterisk unable to start
by Lu V 20 Aug '19

20 Aug '19

Well this is the first this has happened to me on a pi install. I had replaced a router and needed to restart my node. I used shutdown -r now command and now asterisks will not start. I get: Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?) root@repeater:/home/repeater# So if I execute with asterisk -vvvvvvc I get this output. See attached file. Can someone advise what might be happening before I give up and reimage this node? Thanks. Lu KA4EPS

5 13

trying it again.. it doesn't work.. $#&^!!
by Jim Hertel 18 Aug '19

18 Aug '19

Ports are open... 4560-4590 udp, port 4569 udp 5198 - 5199 ( I know it's for echolink) but not going to set it up yet node 47379.. listed to my call sign (n6kmr) registered it all looks fine etc.. pass code etc info I have gotten from others... 1) Your port forwarding on your router is not setup correctly. 2) Your network settings on your node are not entered correctly. 3) When setting up your node, you may have not entered your correct node password. Check out those 3 things and let us know if you have any luck."" (I do believe I have them correct) OR... Not familiar with your set up. I do know that you have to open port 4569 or what ever you did when you did the node setup, but that is the default and needs to be Port Forward UDP to start with. If that isn't done, no one can connect to you. Well I do want to thank all that has helped so far, but I need to send this to some one.. because this is well to mind boggling. And I am sure this is easy to some but the HELP files SUCK, I need to learn this but having time and barely a week end to work on this is very frustrating.. This is what I have so far: node 47379 Running a Pi 3, using a URIx-B, green light is on (with proper cables) with a kenwood tm-g707 I have updated the PI.. and asterick from the ASL window, I could send everything to someone who would help then tell me what I did wrong, OR sign in remotely? Send for HELP or go for more beer! I guess a step by step process is what is needed... any takers.. Jim n6kmr

2 2

Setup Problems
by Jim Korenz 18 Aug '19

18 Aug '19

OK, I've been having problems with setting AllStar. I had a workinglink till it died about a month ago. I replaced the PI and SD cardand started a new install. I've run into multiple problems on the way.In the setup script, I didn't notice that the demo node no. 19999didn't erase as I typed my node no. 28674. After setup,it wouldn'tlogin to the Allstar server. I checked the config files and foundthe node no was 1999928674. OK, now rerun the setup script.Still no luck. On further examination, the node no was now28767428674. OK, reburn the SD card and start over.Now we get to the setup screen for the network. I selectstatic IP. I enter my IP 192.168.0.100. Now the netmask,255.255.255.000. ERROR, bad entry. Now instead oflooping back and asking again, the setup exits the networksetup screen. Worse yet, reruning the asl-menu doesn'tenter the network setup screen. Reburn the SD card and try again. Next time try netmask of 255.255.255.128,no go. Reburn SD try again. This time try 255.255.255.192 ,yea, this works, but afterwards Allstar doesn't because192.168.0.100 can't be reached with this mask. OK, I finally manually edit the dhcpcd.conf file and get theinternet access working and am logged into theAllstar server. I've setup the EchoLink also.The last problem is no one can connect to theEchoLink node. I would like someone to testthe Allstar link and the Echolink node, 745361.Also, I had to use the alternate AllStar port of 4566since I have AT&T and they blocked 4569.Any help would be appreciated. JimK N8PXW

2 1

Custom Nodename
by Len Griffin 18 Aug '19

18 Aug '19

Our K2ETS repeater has suddenly stopped using my custom nodename for my 42690 node. I checked the /var/lib/asterisk/sounds/rpt/nodenames ' 42690.ulaw ' file, and it is still the custom audio, yet when connecting, K2ETS just announces ' node 42690 '. I noticed this about 2 weeks ago. No changes were made to the system.

2 1

web server outage this morning
by David McGough 17 Aug '19

17 Aug '19

Guys, Several things aren't working this morning, including: https://web-tpa.allstarlink.org/ https://allstarlink.org/cgi-bin/allmondb.pl 73, David KB4FXC

2 2

Stat server and new web server
by George Csahanin 16 Aug '19

16 Aug '19

Anybody else having issues seeing the stats server? or web-tpa? GeorgeC W2DB -- George Csahanin 10100 Carson Ranch Rd. Crowley, TX 76036 682-708-5716 home 401-338-0568 cel

2 1

AllStar Link Node List issue
by Alberto Enrique Puig 16 Aug '19

16 Aug '19

As of today the Main Stats Page is showing 3174 nodes reporting. My node number 46631 is connected but it not been show on this list for the last coupe of days. I wonder if there is any problem with this page. Regards, Alberto KP4AP 73 [https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-anima…]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>

2 1