Tonight I had a user tell me that one of my nodes wouldn’t connect
anywhere. Verified, rebooted the server, still nothing. Tried
running the rc.updatenodelist script manually and it just sits
there.
However, after running the following command I do get an update and
can now connect to other nodes.
/usr/bin/wget -O /var/lib/asterisk/rpt_extnodes
When I checked two other nodes they had the same problem and same
work-around.
I ran that same command for nodes2 and it works. When I run it for
nodes3 it times out.
Could a problem with nodes3.allstarlink.org be causing the
rc.updatenodelist script to choke? And could that have been causing
my nodes to not be able to connect to others?
You are not alone in complaining about this problem. I’m not sure what is happening but something appears to be amiss. Yes nodes3 has been down for a while but that shouldn’t break anything.
There are a few different versions of rc.updatenodlist out there. One version has a 2 hour sleep if no data is received repeatedly. Maybe that version is hitting nodes3 and giving up forever. I took that version and tweaked it a bit in an attempt to add diagnostics. It’s attached here. Unzip it, put it in your root directory and mark it executable. Do a killall rc.updatenodlist and then run this script. Report if you see anything interesting. Remember to reboot your node to start rc.updatenodelist when done.
You script monkeys may want to take a close look at the attached script. I suspect it has a bug as some of the if statements don’t make sense to me. And just maybe that’s the issue.
You are not alone in complaining about this problem. I’m not sure what is happening but something appears to be amiss. Yes nodes3 has been down for a while but that shouldn’t break anything.
There are a few different versions of rc.updatenodlist out there. One version has a 2 hour sleep if no data is received repeatedly. Maybe that version is hitting nodes3 and giving up forever. I took that version and tweaked it a bit in an attempt to add diagnostics. It’s attached here. Unzip it, put it in your root directory and mark it executable. Do a killall rc.updatenodlist and then run this script. Report if you see anything interesting. Remember to reboot your node to start rc.updatenodelist when done.
You script monkeys may want to take a close look at the attached script. I suspect it has a bug as some of the if statements don’t make sense to me. And just maybe that’s the issue.
Sending again, this time with the attachment.
BTW, rc.updatenodelist should ‘just sit there’ as it goes into a forever loop which gets the node list, sleeps for 10 minutes and repeats. Also, ‘registration’ is when your node announces itself to the Allstar system. Your node is registered if it’s green on the nodes list. The process we are talking about here is the distribution of the Allstar directory, i.e. registered nodes and their IP address.
It appears that the "nodes1" list may not be updating properly. When I pulled from "nodes2" list instead, it was current. In case someone wants to have a look.
It appears that the "nodes1" list may not be updating properly. When I pulled from "nodes2" list instead, it was current. In case someone wants to have a look.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
It appears that the "nodes1" list may not be updating properly. When I
pulled from "nodes2" list instead, it was current. In case someone wants to
have a look.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to
the bottom of the page. Enter your email address and press the "Unsubscribe
or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.