An inadvertent and catastrophic piece of mistyping when upgrading from client 4.02 to 4.05 was:

boinc_gui -uninstall

(at least I think it was -uninstall - it was -something).

Of course, I meant boinc_cli -uninstall, to uninstall the service.


That resulted in the loss of my only decent run with an exit code of -1, and sadly no backup (I don\'t have the room on my tapes to backup BOINC, though I may try, especially after this, to at least make a nightly disk based backup of the BOINC folder).


I figured I may as well reset the project to pick up a new 4.03 based run. I had a couple of runs lying around with a few execution hours from multi-processor testing (this is a dual processor machine with Hyperthreading), but nothing with enough execution to be worth keeping, and I detected, possibly incorrectly, that with the bugs in the 4.02 clinet it was probably better to reset such runs.


I then made a similar typing mistake (not my night - but maybe it\'s produced a useful result) installing the 4.05 client as a service - typing

boinc_gui -install

instead of:

boinc_cli -install


and promptly lost my new 4.03 run under the 4.05 client also with an exit code of -1. If this is a bug (and it sure looks like one to me), it\'s in the release code.


I\'ve now got the new run set up as a service - and I\'m not seeing anything appearing in the application event log - unlike with the 4.02 client. I had picked up that people wanted BOINC to be less verbose in the event log - but I\'d expected something!


Is it wise to clear up all the garbage in my BOINC folder manually - 4.02 project files, also all the folders relating to my failed runs?



David

They must have trimmed the EventLog writing, if you bring up TaskManager do you see a "hadsm3_4.03*" and "hadsm3um_4.03*" and the "boinc_cli.exe" running?

> They must have trimmed the EventLog writing, if you bring up TaskManager do
> you see a "hadsm3_4.03*" and "hadsm3um_4.03*" and the "boinc_cli.exe"
> running?


Everything is present and correct, Carl - the model is running.


Any comments on the other observations?



David

Before v4.04, they turned off the logging: "Comment out event logging to the Windows Event log until we can refactor the various messages."

The cli uses a lockfile, so you can only run one instance in a directory. But unfortunately the gui doesn't have any checks, nor a lockfile, so the cli doesn't know if the gui is running.

The installer should automatically stop the gui if it's running, but does nothing with the cli.

Since AFAIK they're making a stand-alone gui that should take over for the current, they'll probably not make any changes in this behaviour.
Also remember the BOINC-client is still beta.

BTW, there's no reason to uninstall the service, if you're not moving to another directory. Just stop it in the service control panel before installing new client.

I had another circumstance that seems to have caused a -1 exit code. I updated the BOINC client. It started a CPDN workunit then paused it almost immediately to run CPU benchmarks. When the benchmarks finished the workunit errored out.
<br>John Keck -- BOINCing since 2002/12/08 -- <a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=191"><img border="0" height="80" src="http://191.cpdn.sig.boinc.dk?188"></a>