See attached info. The updates seem to affect the status server reporting.
Does anybody know which script(s) this affects?
Despite some people saying that they have done the updates, they are still on the list below as mentioned by Dave C.
Jon VA3RQ
···
All of it is contained in the new statupdate script, which is part of an update sent a week ago. I am shocked at the number of nodes that are not updating correctly.
The server was changed, and we had to change the script to match. Soon these nodes will be tagged as down, and will be subject to PGP key removal. I am trying to help people get their nodes updating on a regular basis.
If the update is not working, then there is no way that new features can be pushed to the nodes. They are essentially going to fade away and fall behind the system.
Dave Cameron
VE7LTD
--- Inirlp@yahoogroups.com, Buddy Brannan<buddy@...> wrote:
>
> So, what's the new URL, and where is it updated?
> --
> Buddy Brannan, KB5ELV - Erie, PA
> Phone: (814) 860-3194 or 888-75-BUDDY
>
> On Oct 21, 2010, at 11:19 AM, ve7ltd wrote:
>
> > Here is the list so far today. Please note that these lists are the best I can get because I am going off of log files on the status page server. These nodes have not been updated since midnight mountain time last night.
> >
> > These are nodes that are using the OLD URL to try to send status updates. I am going to send a targeted email to the owners via their status page entries to get their attention.
> >
> > 1160
> > 1250
> > 1840
> > 1882
> > 2015
> > 2020
> > 2154
> > 2184
> > 2270
> > 2304
> > 2365
> > 2414
> > 2509
> > 2537
> > 2590
> > 2600
> > 2651
> > 2736
> > 2739
> > 2882
> > 2949
> > 3018
> > 3029
> > 3059
> > 3066
> > 3075
> > 3078
> > 3088
> > 3098
> > 3102
> > 3145
> > 3152
> > 3158
> > 3170
> > 3174
> > 3192
> > 3212
> > 3225
> > 3299
> > 3330
> > 3337
> > 3396
> > 3402
> > 3415
> > 3418
> > 3440
> > 3486
> > 3500
> > 3517
> > 3530
> > 3539
> > 3629
> > 3659
> > 3667
> > 3696
> > 3727
> > 3734
> > 3744
> > 3753
> > 3759
> > 3765
> > 3767
> > 3778
> > 3793
> > 3795
> > 3826
> > 3829
> > 3865
> > 3913
> > 3917
> > 3924
> > 3927
> > 3932
> > 3962
> > 3967
> > 3969
> > 3971
> > 3976
> > 3986
> > 3994
> > 4067
> > 4068
> > 4076
> > 4077
> > 4100
> > 4103
> > 4134
> > 4147
> > 4170
> > 4200
> > 4204
> > 4280
> > 4410
> > 4467
> > 4486
> > 4494
> > 4503
> > 4529
> > 4563
> > 4606
> > 4610
> > 4650
> > 4661
> > 4671
> > 4715
> > 4722
> > 4765
> > 4777
> > 4802
> > 4835
> > 4881
> > 4922
> > 4952
> > 4967
> > 5056
> > 5070
> > 5361
> > 5429
> > 5444
> > 5466
> > 5468
> > 5503
> > 5515
> > 5588
> > 5612
> > 5660
> > 5690
> > 5717
> > 5720
> > 5776
> > 5961
> > 6122
> > 6796
> > 7001
> > 7010
> > 7011
> > 7012
> > 7013
> > 7014
> > 7015
> > 7016
> > 7018
> > 7019
> > 7020
> > 7058
> > 7149
> > 7192
> > 7550
> > 7580
> > 7661
> > 7671
> > 7689
> > 7697
> > 7718
> > 7731
> > 7820
> > 7841
> > 8038
> > 8066
> > 8190
> > 8289
> > 8322
> > 8327
> > 8365
> > 8380
> > 8484
> > 8562
> > 8720
> > 8937
Ok I will stop barking about this and await the solution.
I will have a look at my node tonight.
Jon
···
Hi,
I *think* I got it sorted out. The change was to the statupdate script.
Check for /home/irlp/update-files/scripts/statupdate and copy it to /home/irlp/scripts .
Then, you may need to edit the file to add the wget variable. You can either change $WGET to /usr/bin/wget or add this line after the line to source common functions:
WGET=/usr/bin/wget
It seems to have run. Hopefully this means my node is now correctly updated.
--
Buddy Brannan, KB5ELV - Erie, PA
Phone: (814) 860-3194 or 888-75-BUDDY
On Oct 21, 2010, at 3:23 PM, Jon Rorke wrote:
See attached info. The updates seem to affect the status server reporting.
Does anybody know which script(s) this affects?
Despite some people saying that they have done the updates, they are still on the list below as mentioned by Dave C.
Jon VA3RQ
All of it is contained in the new statupdate script, which is part of an update sent a week ago. I am shocked at the number of nodes that are not updating correctly.
The server was changed, and we had to change the script to match. Soon these nodes will be tagged as down, and will be subject to PGP key removal. I am trying to help people get their nodes updating on a regular basis.
If the update is not working, then there is no way that new features can be pushed to the nodes. They are essentially going to fade away and fall behind the system.
Dave Cameron
VE7LTD
--- Inirlp@yahoogroups.com, Buddy Brannan<buddy@...> wrote:
So, what's the new URL, and where is it updated?
--
Buddy Brannan, KB5ELV - Erie, PA
Phone: (814) 860-3194 or 888-75-BUDDY
On Oct 21, 2010, at 11:19 AM, ve7ltd wrote:
Here is the list so far today. Please note that these lists are the best I can get because I am going off of log files on the status page server. These nodes have not been updated since midnight mountain time last night.
These are nodes that are using the OLD URL to try to send status updates. I am going to send a targeted email to the owners via their status page entries to get their attention.
1160
1250
1840
1882
2015
2020
2154
2184
2270
2304
2365
2414
2509
2537
2590
2600
2651
2736
2739
2882
2949
3018
3029
3059
3066
3075
3078
3088
3098
3102
3145
3152
3158
3170
3174
3192
3212
3225
3299
3330
3337
3396
3402
3415
3418
3440
3486
3500
3517
3530
3539
3629
3659
3667
3696
3727
3734
3744
3753
3759
3765
3767
3778
3793
3795
3826
3829
3865
3913
3917
3924
3927
3932
3962
3967
3969
3971
3976
3986
3994
4067
4068
4076
4077
4100
4103
4134
4147
4170
4200
4204
4280
4410
4467
4486
4494
4503
4529
4563
4606
4610
4650
4661
4671
4715
4722
4765
4777
4802
4835
4881
4922
4952
4967
5056
5070
5361
5429
5444
5466
5468
5503
5515
5588
5612
5660
5690
5717
5720
5776
5961
6122
6796
7001
7010
7011
7012
7013
7014
7015
7016
7018
7019
7020
7058
7149
7192
7550
7580
7661
7671
7689
7697
7718
7731
7820
7841
8038
8066
8190
8289
8322
8327
8365
8380
8484
8562
8720
8937
_______________________________________________
App_rpt-users mailing list
App_rpt-users@qrvc.com
http://qrvc.com/mailman/listinfo/app_rpt-users