<HTML>
<HEAD>
<TITLE>Re: [App_rpt-users] Problem with Stats and Mapping Servers.</TITLE>
</HEAD>
<BODY>
<FONT FACE="Arial"><SPAN STYLE='font-size:13pt'>A follow up to my message regarding trying to update the stats servers.<BR>
<BR>
I would suggest that for node 2425 and 27499, there will be similar entries.<BR>
<BR>
<a href="2425=radio@104.247.241.75:4569/2425">2425=radio@104.247.241.75:4569/2425</a>,104.247.241.75<BR>
<BR>
<a href="27499=radio@99.243.133.111:4569/27499">27499=radio@99.243.133.111:4569/27499</a>,99.243.133.111<BR>
<BR>
<BR>
Keith<BR>
<BR>
<BR>
VE3RTR-AllStar.47553 > cyclonus.mozone.net.http: Flags [.], cksum 0x8cd3 (incorrect -> 0x99e1), seq 224, ack 258, win 237, options [nop,nop,TS val 997713 ecr 3108775738], length 0<BR>
09:25:12.128425 IP (tos 0x0, ttl 64, id 5042, offset 0, flags [DF], proto TCP (6), length 52)<BR>
VE3RTR-AllStar.47553 > cyclonus.mozone.net.http: Flags [F.], cksum 0x8cd3 (incorrect -> 0x99df), seq 224, ack 258, win 237, options [nop,nop,TS val 997714 ecr 3108775738], length 0<BR>
09:25:12.204495 IP (tos 0x0, ttl 57, id 30949, offset 0, flags [DF], proto TCP (6), length 304)<BR>
cyclonus.mozone.net.http > VE3RTR-AllStar.47554: Flags [P.], cksum 0x52fb (correct), seq 1:253, ack 334, win 54, options [nop,nop,TS val 3108775758 ecr 997383], length 252: HTTP, length: 252<BR>
HTTP/1.1 200 OK<BR>
Date: Fri, 11 Sep 2015 13:25:12 GMT<BR>
Server: Apache<BR>
Pragma: no-cache<BR>
Keep-Alive: timeout=5, max=100<BR>
Connection: Keep-Alive<BR>
Transfer-Encoding: chunked<BR>
Content-Type: text/plain<BR>
<BR>
<FONT COLOR="#FF0000">2e<BR>
Error! Not Authorized from IP 216.168.118.153<BR>
</FONT> <BR>
09:25:12.204931 IP (tos 0x0, ttl 64, id 58550, offset 0, flags [DF], proto TCP (6), length 52)<BR>
<BR>
<BR>
<BR>
On 9/11/15 9:10 AM, "Keith Goobie" <<a href="keith@goobie.org">keith@goobie.org</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Arial"><SPAN STYLE='font-size:13pt'>Good day all!<BR>
<BR>
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. <BR>
<BR>
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. <BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Andale Mono"><SPAN STYLE='font-size:10pt'>Node Mode Callsign Channel CTCSS Location<BR>
2258 N/A N/A N/A N/A N/A<BR>
<FONT COLOR="#3001EE"><U>2344 </U></FONT> Transceive VE3YYZ 443.050+ 103.5 Toronto, ON<BR>
<FONT COLOR="#3001EE"><U>2359 </U></FONT> Transceive VE3RQQ 146.550 156.7 Little Current ON<BR>
<FONT COLOR="#3001EE"><U>2377 </U></FONT> Transceive VE3SNM 442.850+ 136.5 Ballantrae ON<BR>
<FONT COLOR="#3001EE"><U>2416 </U></FONT> Transceive VE3SUE 444.400+ 114.8 London ON<BR>
<FONT COLOR="#3001EE"><U>2417 </U></FONT> Transceive VA3NEG 444.425+ 103.5 Oakville ON<BR>
2425 N/A N/A N/A N/A N/A<BR>
<FONT COLOR="#3001EE"><U>27211 </U></FONT> Transceive VE3LSR 442.575+ 103.5 Edgar, Ontario<BR>
<FONT COLOR="#3001EE"><U>27285 </U></FONT> Transceive VE3DSX 442.625+ 131.8 Hamilton ON<BR>
27499 N/A N/A N/A N/A N/A<BR>
<FONT COLOR="#3001EE"><U>28708 </U></FONT> Transceive VE3CKL 444.650+ 162.2 Lindsay, ON<BR>
<FONT COLOR="#3001EE"><U>29373 </U></FONT> Transceive VE3ORC 444.550+ 156.7 Orillia, ON<BR>
</SPAN></FONT></FONT><FONT FACE="Arial"><SPAN STYLE='font-size:13pt'><BR>
>From the allstarlink.org node listings, if I drill in on 2257 or 2258 I get:<BR>
<FONT COLOR="#0000FF"><BR>
</FONT></SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="5"><FONT FACE="Verdana Bold"><SPAN STYLE='font-size:24pt'>Node 2258<BR>
</SPAN></FONT></FONT><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'><BR>
<BR>
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).<BR>
<BR>
</SPAN></FONT></FONT></FONT><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'><BR>
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.<BR>
<BR>
Thanks in advance to the guys that will diagnose and correct the issue.<BR>
<BR>
Keith<BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'><BR>
</SPAN></FONT></FONT><FONT FACE="Arial"><SPAN STYLE='font-size:13pt'>-- <BR>
<a href="keith@goobie.org">keith@goobie.org</a><BR>
Keith Goobie<BR>
Richmond Hill, ON, CANADA<BR>
</SPAN></FONT>
</BODY>
</HTML>