Currently, with most of what's listed being stuck there since late January, up to Feb (any chance to have those cleared away at some point?), if I eliminate those, I currently have 29 validate errors, 39 valids and 53 inconclusives, 23 of those with wingman results. That's not the 8% that was mentioned, it's almost half. Started around June 25 if I check my RAC graphic.

Dear Tom,

is the updated validator now running? If so, please send us a note.

Hello,

I haven't gone radio silent! I'm working on putting the validator up on the server. Not sure how long it'll take, things are already taking longer than expected. I'm hoping by the end of the week. Thanks for your patience.

Please see https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4747&postid=70966#70966 for updates on the new validator. It's currently running, hopefully things are all set.

The new validator is up and seems to be successfully validating workunits. I'd like to hear if people start to see reduced numbers of invalids, or if things are the same as before.

EDIT: The validation errors are dropping in real time, so I'm going to assume that things are fixed unless I hear otherwise.

Looks good so far, I have no new errors the last few hours.

All Linux Separation work units are failing with the following error

Task 276551426
Name de_modfit_85_bundle4_4s_south4s_gapfix_1627399316_3938308_0
Workunit 145671322
Created 1 Aug 2021, 16:42:15 UTC
Sent 1 Aug 2021, 16:53:15 UTC
Report deadline 13 Aug 2021, 16:53:15 UTC
Received 2 Aug 2021, 22:00:35 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 1 (0x00000001) Unknown error code
Computer ID 448629
Run time 2 sec
CPU time
Validate state Invalid
Credit 0.00
Device peak FLOPS 4.33 GFLOPS
Application version Milkyway@home Separation v1.46
x86_64-pc-linux-gnu
Peak disk usage 0.01 MB
Stderr output

<core_client_version>7.4.25</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.46 Linux x86_64 double </search_application>
Reading preferences ended prematurely
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 4 </number_WUs>
<number_params_per_WU> 26 </number_params_per_WU>
stream sigma 0.0 is invalid
Failed to get stream constants
07:58:52 (32011): called boinc_finish(1)

</stderr_txt

Windows is working OK on Separation WUs, N-Body works fine on same Linux computer, using just CPU for both WU types.

Conan

---

Just FYI.
Running same WUs here (CPU only) on 2 machines, 1 Win10 the other Ubuntu 18.0.4.
Not seeing any recent failures or errors on either.
My machines should be viewable if you want to compare.
Regards, Jim ...

---

Conan,

I think you'll find the problem is related to your BOINC client version...

<core_client_version>7.4.25</core_client_version>

There used to be a 1024-character constraint on command-line parameters, and it started causing various issues with 26-parameter jobs like the one you reported on...

<number_WUs> 4 </number_WUs>
<number_params_per_WU> 26 </number_params_per_WU>

There are some old threads (2018 or thereabouts) in various places on the subject but, to summarize, the fix was to move up to a newer BOINC client version (I think 7.6.x versions ran o.k. and things have moved further on since then.)

It seems you're running a 7.14 client on Windows (which is why you aren't seeing problems there!); I don't know what the situation about BOINC client versions for your Linux version is, so I don't know whether you'll be able to find a newer version easily - if you can upgrade, I think your problem will go away!

Cheers - Al.

FWIW, both my Win10 and Ubuntu boxes mentioned above are running 7.16.x BOINC client.

---

Thanks Jim and Al. That seems to make sense.

Upgrading may be an issue as I have the last version output by BOINC themselves.

The later versions seem to have a lot to do with the distributors of the various Linux versions.
I have tried some in the past but I don't like the way they store my data all over the place and I lose control as it all goes to root control.

But there is a way I think to take back that control and install a later version my way, I will have to think about it and have a go at a later date.

Conan

---

Thanks Jim and Al. That seems to make sense.

Upgrading may be an issue as I have the last version output by BOINC themselves.

I use an all-in-one BOINC version that just extracts to a directory. It was widely distributed at SETI. I can fix you up with a copy if you'd like ...
Alternately, if you want to try a PPA I can provide a link there as well.

---