Good day all! Over the past few days, I heard from node sysops that the stats / reporting server was beginning to show signs of illness. I investigated (confirmed) and additionally it is now showing incorrect map displays. So far for us based on the stats from node 2248 (a hub), we are seeing problems for nodes 2257/2258 and 2425 and 27499. Node Mode Callsign Channel CTCSS Location 2258 N/A N/A N/A N/A N/A 2344 Transceive VE3YYZ 443.050+ 103.5 Toronto, ON 2359 Transceive VE3RQQ 146.550 156.7 Little Current ON 2377 Transceive VE3SNM 442.850+ 136.5 Ballantrae ON 2416 Transceive VE3SUE 444.400+ 114.8 London ON 2417 Transceive VA3NEG 444.425+ 103.5 Oakville ON 2425 N/A N/A N/A N/A N/A 27211 Transceive VE3LSR 442.575+ 103.5 Edgar, Ontario 27285 Transceive VE3DSX 442.625+ 131.8 Hamilton ON 27499 N/A N/A N/A N/A N/A 28708 Transceive VE3CKL 444.650+ 162.2 Lindsay, ON 29373 Transceive VE3ORC 444.550+ 156.7 Orillia, ON
From the allstarlink.org node listings, if I drill in on 2257 or 2258 I get:
Node 2258 The information related to the node for which you wish to get statistics (2258) is currently unavailable. There are potentially many reasons for this. It DOES NOT mean (necessarily) that there is a problem with the node itself, or its status on the Allstar Link Network. There may be a problem with this statistics server (which is likely if the node's statistics were available in the past, and are no longer available), or the node may be improperly configured (which is likely if it has never had it's statistics properly displayed). About ten weeks ago, we had a similar problem, which was remedied when Jim WB6NIL (or a proxy) intervened. Looks to be a similar problem. Thanks in advance to the guys that will diagnose and correct the issue. Keith -- keith@goobie.org Keith Goobie Richmond Hill, ON, CANADA