IIRC the maximum timeout has been reduced in the development version of the boinc client. If you want to beta(alpha?) test it you're more than welcome to. A third option is to have all your machines have enough work to crunch through the maximum timeout period. This is something I do every time I leave my machines unattended.
So if anybody knows of an easier way to update 200 machines, I'd love to hear about it. I'm getting mighty sick of doing it manually. The machines are in two separate locations (my home and my work) and are spread over several rooms. The work location has 180+ on a single subnet sharing (through about 15 hubs/switches each from 8 to 24 ports) a single ADSL internet connection. As long as the project is up and stable, everything works fine and everything is very much set and forget. However these recent outages and server flakiness problems have been giving me real headaches.
The one week backoff looks like it was introduced somewhere in the 5.3.x or later series of BOINC. I have a couple of boxes still on 5.2.13 which have managed to recover by themselves, although there were still quite a few hours of lost crunching time. At least it wasn't a week for them.
Actually, for all v5.2.14 and earlier clients, the backoff was 2 weeks, the backoffs was introduction 19.12.2002, this is pre-v0.14.
This was decreased to only 1 week 06.12.2005, for the v5.3.3-version.
And finally, decreased again to 1 day, 29.07.2006 for v5.5.10 and later.
Quote:
For example, whilst the project is offline, the inability to contact the scheduling server quickly leads to the one week backoff.
10 failed Scheduler-requests, and client tries to re-download master-URL. If this also fails 3 times, you'll get hit with the long deferral.
Basically, scheduling-server going down isn't a problem, it's only if also the web-server goes down you'll be hit with the long deferral. So, using separate web-server is an advantage, if can also put this on separate internet-connection and power-source, even better.
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
So if anybody knows of an easier way to update 200 machines, I'd love to hear about it.
Hmm, use boinccmd, and make a batch-file, or 2... boinccmd.exe is located in your boinc-directory, atleast under windows.
If 2 batch-files, #1 would basically be list_of_boinc_computers.cmd:
call update_boinc.cmd computername0001 password0001
call update_boinc.cmd computername0002 password0002
...
// continue listing all computers & their password
#2 is update_boinc.cmd, and includes 1 line:
boinccmd --host %1 --passwd %2 --project http://einstein.phys.uwm.edu/ update
Batch-file #1 will run batch-file #2 for each computer, and therefore can very quickly update all computers.
So, the time-consuming is to make the list of all the computer-names, or possibly easier, the ip-numbers. If all computers uses the same password, can put this directly in #2 instead of %2, and don't need to list password0001 and so on in batch-file #1.
Oh, and the advantage of using 2 batch-files is, can easily change #2 to also do other things. ;)
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
Hmm, use boinccmd, and make a batch-file, or 2...Oh, and the advantage of using 2 batch-files is, can easily change #2 to also do other things. ;)
Here's my two cents:
- Gary has two separated subnets, ~ 180 PC's at work and ~ 20 PC's at home.
- Set up BOINView on ONE computer per subnet, call these machines 'WORK_BV' and 'HOME_BV' for this discussion. There will be considerable jiggery-pokery with 'gui_rpc_auth.cfg' and 'remote_hosts.cfg' on EACH computer in EACH subnet - but it's do-able and only needs to be done once.
- both subnets are obviously connected to the internet, so you make a VPN ( virtual private network ) tunnel over the internet ( ie. encrypted ) between WORK_BV and HOME_BV. When 'up' this tunnel will make WORK_BV and HOME_BV appear to be connected as if on the same local net ( network address translation is part of the VPN deal, you can browse each other thru 'My Network Places' or somesuch ). Now I don't know Gary's details here, but later Windows XP ( ? Pro with latest SP's ) will cope with this. One particular pain in the A might be user privileges/identities at either end. Possibly complex. However this mob GoToMyPC has a good product which covers this area well and setting the VPN is actually quite painless, but @ ~ $180 AUD PER LICENSE PER YEAR. You'd only need ONE license in this scenario, for the computer ( I suggest WORK_BV ) which will serve the remote-access calls. You give WORK_BV the detail on who/what/where/when is going to 'dial-in' to it, ie. HOME_BV, and away you go...
- Then I'd assume Gary could sit at home on HOME_BV managing the home subnet directly using it's BOINCView, and could open up a Remote Desktop Connection ( so definitely XP Pro required ) to WORK_BV and thus use it's BOINView installation for those 180+ other PC's at work.
- of course I've not commented on many possible showstoppers here - firewalls, proxies etc that are specific to Gary's setups.
Cheers, Mike.
NB. I have no shares in GoToMyPC! I use it and it works well.
( edit ) BOINView has a terrific GUI which enables sorting and flagging of all kinds of conditions - so that you could quickly overview and diagnose problems over a large set of machines. Try it at home on the smaller ( ~ 20 ) set of boxes - if he's not already.. :-)
( edit ) Also there's no requirement that I'm aware of for the hexadecimal password in the 'gui_rpc_auth.cfg' to be distinct amongst any/all the machines. Grab a version of 'gui_rpc_auth.cfg' from some machine and copy it to the BOINC install directories of ALL the others in a given subnet. Now use that single password for the location setup dialog box in BOINView as you introduce each machine to it. Otherwise you'd not have not alot of hope at tracking 200+ hexadecimal passwords!! In addition, for a given subnet, 'remote_hosts.cfg' is going to contain the same entry - the name or IP address of the BOINView machine for that subnet - so copy that to all the BOINC install directories in the various machines in a subnet.
( edit ) As a further bonus, the VPN tunnel and remote access call allow you to do whatever you could have done at work according to the profile/privileges of your login identity. So if you already had, or can/will enable, other functions besides BOINView on WORK_BV!! So you may be able to monitor your 180+ work machines in other ways too...
( edit ) and another point ...... the will be lag with a VPN, dependent on your bandwidths at either end. Asymmetric broadbands, by definition, have a different upload/download speeds and with a VPN you will be limited by the LOWEST of those. However it shouldn't be too bad - you're sending keyboard/mouse input one way and getting video output information coming the other way. When invoking the Remote Desktop from HOME_BV choose sensible display settings ( size, color depth, background, themes, window animations, bitmaps etc ) and be minimal in the 'local resources' ( printers, serial ports, disk drives, sound etc ) of WORK_BV that you enable for access from the HOME_BV.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
LOL I must keep that method in mind for people I don't like... server-voodoo, not bad :-D and the best is it's kinda impossible to prove... I wonder if when Wurgl burns the papermachette servers in order to get rid of the evidence there'll be a fire in the server room...?
Regarding the troll mood -- well it wouldn't be RAID0 -- but you are close, with a single live drive, I'd think it would be RADIO -- Not sure if it would be FM or AM though....
IIRC the maximum timeout has
)
IIRC the maximum timeout has been reduced in the development version of the boinc client. If you want to beta(alpha?) test it you're more than welcome to. A third option is to have all your machines have enough work to crunch through the maximum timeout period. This is something I do every time I leave my machines unattended.
RE: So if anybody knows of
)
Have you tried BOINCVIEW?
Seti Classic Final Total: 11446 WU.
RE: The one week backoff
)
Actually, for all v5.2.14 and earlier clients, the backoff was 2 weeks, the backoffs was introduction 19.12.2002, this is pre-v0.14.
This was decreased to only 1 week 06.12.2005, for the v5.3.3-version.
And finally, decreased again to 1 day, 29.07.2006 for v5.5.10 and later.
10 failed Scheduler-requests, and client tries to re-download master-URL. If this also fails 3 times, you'll get hit with the long deferral.
Basically, scheduling-server going down isn't a problem, it's only if also the web-server goes down you'll be hit with the long deferral. So, using separate web-server is an advantage, if can also put this on separate internet-connection and power-source, even better.
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
RE: So if anybody knows of
)
Hmm, use boinccmd, and make a batch-file, or 2... boinccmd.exe is located in your boinc-directory, atleast under windows.
If 2 batch-files, #1 would basically be list_of_boinc_computers.cmd:
call update_boinc.cmd computername0001 password0001
call update_boinc.cmd computername0002 password0002
...
// continue listing all computers & their password
#2 is update_boinc.cmd, and includes 1 line:
boinccmd --host %1 --passwd %2 --project http://einstein.phys.uwm.edu/ update
Batch-file #1 will run batch-file #2 for each computer, and therefore can very quickly update all computers.
So, the time-consuming is to make the list of all the computer-names, or possibly easier, the ip-numbers. If all computers uses the same password, can put this directly in #2 instead of %2, and don't need to list password0001 and so on in batch-file #1.
Oh, and the advantage of using 2 batch-files is, can easily change #2 to also do other things. ;)
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
RE: Hmm, use boinccmd, and
)
Here's my two cents:
- Gary has two separated subnets, ~ 180 PC's at work and ~ 20 PC's at home.
- Set up BOINView on ONE computer per subnet, call these machines 'WORK_BV' and 'HOME_BV' for this discussion. There will be considerable jiggery-pokery with 'gui_rpc_auth.cfg' and 'remote_hosts.cfg' on EACH computer in EACH subnet - but it's do-able and only needs to be done once.
- both subnets are obviously connected to the internet, so you make a VPN ( virtual private network ) tunnel over the internet ( ie. encrypted ) between WORK_BV and HOME_BV. When 'up' this tunnel will make WORK_BV and HOME_BV appear to be connected as if on the same local net ( network address translation is part of the VPN deal, you can browse each other thru 'My Network Places' or somesuch ). Now I don't know Gary's details here, but later Windows XP ( ? Pro with latest SP's ) will cope with this. One particular pain in the A might be user privileges/identities at either end. Possibly complex. However this mob GoToMyPC has a good product which covers this area well and setting the VPN is actually quite painless, but @ ~ $180 AUD PER LICENSE PER YEAR. You'd only need ONE license in this scenario, for the computer ( I suggest WORK_BV ) which will serve the remote-access calls. You give WORK_BV the detail on who/what/where/when is going to 'dial-in' to it, ie. HOME_BV, and away you go...
- Then I'd assume Gary could sit at home on HOME_BV managing the home subnet directly using it's BOINCView, and could open up a Remote Desktop Connection ( so definitely XP Pro required ) to WORK_BV and thus use it's BOINView installation for those 180+ other PC's at work.
- of course I've not commented on many possible showstoppers here - firewalls, proxies etc that are specific to Gary's setups.
Cheers, Mike.
NB. I have no shares in GoToMyPC! I use it and it works well.
( edit ) BOINView has a terrific GUI which enables sorting and flagging of all kinds of conditions - so that you could quickly overview and diagnose problems over a large set of machines. Try it at home on the smaller ( ~ 20 ) set of boxes - if he's not already.. :-)
( edit ) Also there's no requirement that I'm aware of for the hexadecimal password in the 'gui_rpc_auth.cfg' to be distinct amongst any/all the machines. Grab a version of 'gui_rpc_auth.cfg' from some machine and copy it to the BOINC install directories of ALL the others in a given subnet. Now use that single password for the location setup dialog box in BOINView as you introduce each machine to it. Otherwise you'd not have not alot of hope at tracking 200+ hexadecimal passwords!! In addition, for a given subnet, 'remote_hosts.cfg' is going to contain the same entry - the name or IP address of the BOINView machine for that subnet - so copy that to all the BOINC install directories in the various machines in a subnet.
( edit ) As a further bonus, the VPN tunnel and remote access call allow you to do whatever you could have done at work according to the profile/privileges of your login identity. So if you already had, or can/will enable, other functions besides BOINView on WORK_BV!! So you may be able to monitor your 180+ work machines in other ways too...
( edit ) and another point ...... the will be lag with a VPN, dependent on your bandwidths at either end. Asymmetric broadbands, by definition, have a different upload/download speeds and with a VPN you will be limited by the LOWEST of those. However it shouldn't be too bad - you're sending keyboard/mouse input one way and getting video output information coming the other way. When invoking the Remote Desktop from HOME_BV choose sensible display settings ( size, color depth, background, themes, window animations, bitmaps etc ) and be minimal in the 'local resources' ( printers, serial ports, disk drives, sound etc ) of WORK_BV that you enable for access from the HOME_BV.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Believe me! I do not know
)
Believe me!
I do not know anything about voodoo or something like it. It was not me!
RE: Believe me! I do not
)
ROFL !!! :-)
We do have quite a circumstantial case, though, so thank heavens for reasonable doubt, eh? ..... :-)
You do know about prophets never being appreciated in their own times, don't you? :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Quick, search his room for
)
Quick, search his room for papermachette servers!
LOL I must keep that method
)
LOL I must keep that method in mind for people I don't like... server-voodoo, not bad :-D and the best is it's kinda impossible to prove... I wonder if when Wurgl burns the papermachette servers in order to get rid of the evidence there'll be a fire in the server room...?
Regarding the troll mood --
)
Regarding the troll mood -- well it wouldn't be RAID0 -- but you are close, with a single live drive, I'd think it would be RADIO -- Not sure if it would be FM or AM though....