James Nessen wrote:
And just to add..
I updated rc.updatenodelist on my ACID based install to use nodes1-4 and my -temp file went away, and was replaced with a freshly dated rpt_extnodes file.
Jim
On Aug 22, 2009, at 10:48 AM, James Nessen wrote:
I think I found the issue..
rc.updatenodelist on my limey linux machine looks at:
SUBDOMAINS="nodes1 nodes2 nodes3 nodes4"
whereas on an acid install it looks at:
SUBDOMAINS="nodes1"
running the command manually on my ACID based install gives me:
[root@asterisk-2144 asterisk]# wget http://nodes1.allstarlink.org/cgi-bin/nodes.pl --10:50:14-- http://nodes1.allstarlink.org/cgi-bin/nodes.pl Resolving nodes1.allstarlink.org... 209.134.25.160 Connecting to nodes1.allstarlink.org|209.134.25.160|:80... connected. HTTP request sent, awaiting response... 500 Internal Server Error 10:50:14 ERROR 500: Internal Server Error.
So, maybe an issue with this nodes1 server?
Jim, K6JWN
On Aug 22, 2009, at 8:00 AM, Stephen Rodgers wrote:
Ramesh Dhami (VA3UV) wrote:
Hi Steve / Jim;
I've noticed that the rpt_extnodes file has not been updating recently...
Here's the file info from #2200:
-rwx------ 1 root root 14713 Aug 20 21:41 rpt_extnodes -rw-r--r-- 1 root root 0 Aug 22 08:41 rpt_extnodes-temp
Here's the file info from #2461, which I have been soak testing here for the past week, and intend to send it back to its owner today:
-rwx------ 1 root root 14717 Aug 18 00:15 rpt_extnodes -rw-r--r-- 1 root root 0 Aug 22 08:44 rpt_extnodes-temp
Notice that the temp file is being created, so the script is running, but obviously failing (to connect to the server perhaps?)
Hopefully an easy fix...
Cheers,
Ramesh. _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
rpt_extnodes-temp should never show up. And the fact that it is 0 length indicates that it is likely that the resolver on your node may be inoperative. Check to make sure FQDN's resolve on these systems.
Steve WA6ZFT
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
Jim, You are abolutely correct: nodes1.allstarlink.org is having issues. This little script file can be used to see what nodes servers are up and running: #! /bin/sh TOPDOMAIN=allstarlink.org WGET=`which wget` $WGET -O - http://$1.$TOPDOMAIN/cgi-bin/nodes.pl Pass to it an argument for the specific nodes server you wish to test (i.e. nodes1, nodes2). For all acid users, I recommend they edit the rc.updatenodeslist and make sure nodes2.allstarlink.org is specified in addition to nodes1.allstarlink.org like this: SUBDOMAINS="nodes1 nodes2" ACID gets rc.updatenodelist from files.tar.gz in the allstar directory, and copies it to /etc/rc.d/rc.updatenodelist during installation. This is a different file than what limey linux uses. I since updated the file in SVN to include nodes2, but all the existing systems will not see this update as the script is already installed. Steve WA6ZFT