As soon as the next result finishes, update immediately to report the result and you should get no further work this time if your setting is 0.1 days.
~15m left on the current unit. I'll see what happens, if I get annother unit anyway I'll hit the no new work button and see what happens.
Uploaded 1, downloaded 3! WTH!
About dialog says 5.27, result says client version 4.45. Again, WTH!
Disabled requests for new work.
Dan,
I would wait for a response from Gary before acting on this. But, I just wanted to say that I had a problem when I first installed BOINC 5.2.7 (from 5.2.6). If I remember correctly some .dll file didn't load correctly (although there were no error messages from the installer - only from BOINC Manager on start-up). At first, I tried to correct the problem by doing an installer "Repair". That didn't help, so I tried an installer "Remove" and re"Install". That didn't work either, so I downloaded the installer again and did another "Remove" and "Install". That worked.
My point is: Maybe you have had a similar "BOINC 5.2.7 installer" problem. I should say that my installer problem was the first such problem I had ever encountered and I had previously upgraded successfully from 4.19 to 4.45, 4.45 to 5.2.2, 5.2.2 to 5.2.5, 5.2.5 to 5.2.6. EDIT: All these upgrades were simple installs over the previous version (i.e. I never uninstalled the previous version first).
About dialog says 5.27, result says client version 4.45. Again, WTH!
Disabled requests for new work.
You might be running 5.2.7 BOINC Manager but you are running 4.45 BOINC core client. Did you properly uninstall 4.45 before installing 5.2.7? It almost looks like you just copied over the 5.2.7 BOINC Manager.
You also have to be running with a 10 day cache. You need to take a good detailed look at your message logs as the story will be in there somewhere.
In the meantime have a look (with a text editor) through the file global_prefs.xml and see if you have sections there for home, school or work. You must have more than just the defaults. Have a look for the setting work_buf_min_days. I'll bet it's 10 somewhere. It's probably there in several places. Have a look right at the end of the file for the venue pref. What is it set to? Some screwy things can happen when you are adding and subtracting venues.
You should be able to fix things up by editing the .xml file (after shutting down BOINC of course). Report back before doing anything drastic. These things must be due to 4.45 bugs that nobody will be interested in anymore. The quickest thing may well be a complete uninstall, delete global_prefs.xml, and then a reinstall of 5.2.7. BOINC should download a new set from the website.
About dialog says 5.27, result says client version 4.45. Again, WTH!
Disabled requests for new work.
You might be running 5.2.7 BOINC Manager but you are running 4.45 BOINC core client. Did you properly uninstall 4.45 before installing 5.2.7? It almost looks like you just copied over the 5.2.7 BOINC Manager.
A properly written installer should remove the old version automatically, if it didn't do so, or prompt me to I probably did.
Quote:
You also have to be running with a 10 day cache. You need to take a good detailed look at your message logs as the story will be in there somewhere.
In the meantime have a look (with a text editor) through the file global_prefs.xml and see if you have sections there for home, school or work. You must have more than just the defaults. Have a look for the setting work_buf_min_days. I'll bet it's 10 somewhere. It's probably there in several places. Have a look right at the end of the file for the venue pref. What is it set to? Some screwy things can happen when you are adding and subtracting venues.
Nope. Only entry for work_buf_min_days, and it's at .1.
If the forum software doesn't eat it I'm posting the complete contents below:
OK, global preferences look fine. I made a mistake in my previous message when I said that the venue pref was down the bottom of global_prefs.xml. It is actually down the bottom of client_state.xml. Please have a look in client_state.xml, second line from the end and see what host_venue is set to, thanks.
A properly written installer should remove the old version automatically, if it didn't do so, or prompt me to I probably did.
It won't do this ever if you run BOINC as a service and didn't stop it when you went for a newer install. Else the installer will just install 5.2.7 over 4.45 ... It won't uninstall it by default.
If you still run BOINC as 4.45, but the Manager shows up as 5.2.7 (mind, the numbering has changed), it looks as if you have got it running as a service. You either have to stop the service from running through the Services window, or by using the Net Stop BOINC command on the Command Line Interface, before installing the newer version.
Point of interest Jord. What would the 5.2.7 installer do if it was invoked whilst 4.45 was running? Irrespective of whether or not it was running as a service? I've been trying to think up ways that an installation could install the new Manager but leave the BOINC client alone. I'm not a programmer but I imagine the old executable would be perhaps marked for deletion when it actually stops and at that point the new executable would become active upon a restart. I imagine any OS is going to be rather protective about on disk copies of what is actually executing in memory :).
I've managed to do it once, where I forgot to cancel running BOINC as a service and ending up with 4.72 as being the manager, but 4.45 still running as the daemon. It didn't do anything else bad to my system. Must've been lucky there. ;)
OK, global preferences look fine. I made a mistake in my previous message when I said that the venue pref was down the bottom of global_prefs.xml. It is actually down the bottom of client_state.xml. Please have a look in client_state.xml, second line from the end and see what host_venue is set to, thanks.
A properly written installer should remove the old version automatically, if it didn't do so, or prompt me to I probably did.
It won't do this ever if you run BOINC as a service and didn't stop it when you went for a newer install. Else the installer will just install 5.2.7 over 4.45 ... It won't uninstall it by default.
Bleh. I should've known. It looked like a duck, it quacked like a duck, but it's still an OS app with shoddy windows standards compliance.
Quote:
If you still run BOINC as 4.45, but the Manager shows up as 5.2.7 (mind, the numbering has changed), it looks as if you have got it running as a service. You either have to stop the service from running through the Services window, or by using the Net Stop BOINC command on the Command Line Interface, before installing the newer version.
Unless it's using a name other than boinc it's not running as a service. I did try installing 527 as one, but the installer errored out so I went back to the standard setup. Doesn't matter much since I'm the only user on the pc.
I really think this is the problem. Here's what I'd do if I were you.
* Stop BOINC and confirm through task manager that nothing is running
* Use control panel to uninstall BOINC
* edit both client_state and client_state_prev to delete "home" as the venue
* reinstall BOINC 5.2.7
* BOINC should pick up from where it left off and resume normal crunching.
You should now be able to allow EAH to be unsuspended. I notice you have already aborted one "close to the deadline" result. You can repeat that later on if it really becomes necessary. I imagine this new BOINC is going to put on a bit of a performance when it wakes up and notices just how much work you have given it to manage :). It's an excellent opportunity to see how good the new scheduling stuff in 5.x.x is compared to 4.xx. You may get some messages in your logs that might be of interest to the Wiki people (Paul D Buck).
RE: RE: RE: As soon as
)
Dan,
I would wait for a response from Gary before acting on this. But, I just wanted to say that I had a problem when I first installed BOINC 5.2.7 (from 5.2.6). If I remember correctly some .dll file didn't load correctly (although there were no error messages from the installer - only from BOINC Manager on start-up). At first, I tried to correct the problem by doing an installer "Repair". That didn't help, so I tried an installer "Remove" and re"Install". That didn't work either, so I downloaded the installer again and did another "Remove" and "Install". That worked.
My point is: Maybe you have had a similar "BOINC 5.2.7 installer" problem. I should say that my installer problem was the first such problem I had ever encountered and I had previously upgraded successfully from 4.19 to 4.45, 4.45 to 5.2.2, 5.2.2 to 5.2.5, 5.2.5 to 5.2.6. EDIT: All these upgrades were simple installs over the previous version (i.e. I never uninstalled the previous version first).
Stick
RE: Uploaded 1, downloaded
)
You might be running 5.2.7 BOINC Manager but you are running 4.45 BOINC core client. Did you properly uninstall 4.45 before installing 5.2.7? It almost looks like you just copied over the 5.2.7 BOINC Manager.
You also have to be running with a 10 day cache. You need to take a good detailed look at your message logs as the story will be in there somewhere.
In the meantime have a look (with a text editor) through the file global_prefs.xml and see if you have sections there for home, school or work. You must have more than just the defaults. Have a look for the setting work_buf_min_days. I'll bet it's 10 somewhere. It's probably there in several places. Have a look right at the end of the file for the venue pref. What is it set to? Some screwy things can happen when you are adding and subtracting venues.
You should be able to fix things up by editing the .xml file (after shutting down BOINC of course). Report back before doing anything drastic. These things must be due to 4.45 bugs that nobody will be interested in anymore. The quickest thing may well be a complete uninstall, delete global_prefs.xml, and then a reinstall of 5.2.7. BOINC should download a new set from the website.
Cheers,
Gary.
RE: RE: Uploaded 1,
)
A properly written installer should remove the old version automatically, if it didn't do so, or prompt me to I probably did.
Nope. Only entry for work_buf_min_days, and it's at .1.
If the forum software doesn't eat it I'm posting the complete contents below:
http://einstein.phys.uwm.edu/
http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
1132540269
3
60
.1
2
60
2
100
0
75
0
0
OK, global preferences look
)
OK, global preferences look fine. I made a mistake in my previous message when I said that the venue pref was down the bottom of global_prefs.xml. It is actually down the bottom of client_state.xml. Please have a look in client_state.xml, second line from the end and see what host_venue is set to, thanks.
Cheers,
Gary.
RE: A properly written
)
It won't do this ever if you run BOINC as a service and didn't stop it when you went for a newer install. Else the installer will just install 5.2.7 over 4.45 ... It won't uninstall it by default.
If you still run BOINC as 4.45, but the Manager shows up as 5.2.7 (mind, the numbering has changed), it looks as if you have got it running as a service. You either have to stop the service from running through the Services window, or by using the Net Stop BOINC command on the Command Line Interface, before installing the newer version.
Point of interest Jord. What
)
Point of interest Jord. What would the 5.2.7 installer do if it was invoked whilst 4.45 was running? Irrespective of whether or not it was running as a service? I've been trying to think up ways that an installation could install the new Manager but leave the BOINC client alone. I'm not a programmer but I imagine the old executable would be perhaps marked for deletion when it actually stops and at that point the new executable would become active upon a restart. I imagine any OS is going to be rather protective about on disk copies of what is actually executing in memory :).
Cheers,
Gary.
I've managed to do it once,
)
I've managed to do it once, where I forgot to cancel running BOINC as a service and ending up with 4.72 as being the manager, but 4.45 still running as the daemon. It didn't do anything else bad to my system. Must've been lucky there. ;)
RE: OK, global preferences
)
home
RE: RE: A properly
)
Bleh. I should've known. It looked like a duck, it quacked like a duck, but it's still an OS app with shoddy windows standards compliance.
Unless it's using a name other than boinc it's not running as a service. I did try installing 527 as one, but the installer errored out so I went back to the standard setup. Doesn't matter much since I'm the only user on the pc.
RE: home I really think
)
I really think this is the problem. Here's what I'd do if I were you.
* Use control panel to uninstall BOINC
* edit both client_state and client_state_prev to delete "home" as the venue
* reinstall BOINC 5.2.7
* BOINC should pick up from where it left off and resume normal crunching.
You should now be able to allow EAH to be unsuspended. I notice you have already aborted one "close to the deadline" result. You can repeat that later on if it really becomes necessary. I imagine this new BOINC is going to put on a bit of a performance when it wakes up and notices just how much work you have given it to manage :). It's an excellent opportunity to see how good the new scheduling stuff in 5.x.x is compared to 4.xx. You may get some messages in your logs that might be of interest to the Wiki people (Paul D Buck).
Cheers,
Gary.