Siever jobs failing on 64-bit Arm SoC

[yoyo]

I assume that the wrapper doesn't start, so concentrate on the wrapper.

Can you run sievewrapper_145.03_aarch64-unknown-linux-gnu on command line?

If not run it in the debugger
gdb sievewrapper_145.03_aarch64-unknown-linux-gnu
> run

Maybe gdb says something more.

[technik007.cz]

root@rpi5:/var/lib/boinc-client/projects/www.rechenkraft.net_yoyo# ./sievewrapper_145.03_aarch64-unknown-linux-gnu
07:00:58 (623673): wrapper (7.7.26016): starting
07:00:58 (623673): can't open job file job.xml
07:00:58 (623673): can't parse job file: -108
07:00:58 (623673): called boinc_finish(-108)

[technik007.cz]

quite interestingly when I run ./ecmwrapper_705.01_aarch64-unknown-linux-gnu standalone there is no output to console

[yoyo]

Ok, the wrapper basically runs.
Can you do the same with the siever app?

[technik007.cz]

root@rpi5:/var/lib/boinc-client/projects/www.rechenkraft.net_yoyo# ./sr1sieve_1.4.5_aarch64
sr1sieve 1.4.5 -- A sieve for one sequence k*b^n+/-1.
Usage: sr1sieve -P P1 -i FILE <-o FILE | -f FILE> [OPTION ...]
-p --pmin P0
-P --pmax P1 Sieve for factors p in the range P0 <= p <= P1
-i --input FILE Read sieve from NewPGen format file FILE.
-o --output FILE Write sieve to NewPGen format file FILE.
-f --factors FILE Append new factors to file FILE.
-C --cache-file FILE Load (or save) Legendre symbol tables from (or to) FILE.
-s --save TIME Update output file every TIME (default 60) minutes.
-t --threads NUM Start NUM child threads. (Default 0).
-l --L1-cache SIZE Assume L1 data cache is SIZE Kb.
-L --L2-cache SIZE Assume L2 cache is SIZE Kb.
-B --baby METHOD Use METHOD for baby step mulmods.
-G --giant METHOD Use METHOD for giant step mulmods.
-H --hashtable SIZE Force use of a SIZE Kb hashtable.
-Q --subseq Q Force sieving k*b^n+c as subsequences (k*b^d)*(b^Q)^m+c.
-x --no-lookup Don't pre-compute Legendre symbol lookup tables.
-z --lower-priority Run at low priority. (-zz lower).
-Z --raise-priority Run at high priority. (-ZZ higher).
-A --affinity N Set affinity to CPU number N.
-d --duplicates Report factors that don't eliminate any composite.
-q --quiet Don't print found factors.
-v --verbose Print some extra messages. -vv prints more.
-h --help Print this help.


root@rpi5:/var/lib/boinc-client/projects/www.rechenkraft.net_yoyo# ./sr2sieve_1.9.3.1_aarch64
sr2sieve 1.9.3 -- A sieve for multiple sequences k*b^n+/-1 or b^n+/-k.
Read 0 terms for 0 sequences from ABCD format file `sr2data.txt'.
ERROR: Invalid or unrecognised file `sr2data.txt'.

[yoyo]

Strange. In principle wrapper, sr1sieve and sr2sieve are running. So I don't understand the error in BOINC.
Do you have a link to a failed workunit?

[technik007.cz]

In the post viewtopic.php?f=57&t=17660 a guy says certain work units are fine.

Failed work units:

https://www.rechenkraft.net/yoyo/result ... =105733998
https://www.rechenkraft.net/yoyo/result ... =105733996
https://www.rechenkraft.net/yoyo/result ... =105733637
https://www.rechenkraft.net/yoyo/result ... =105733489
https://www.rechenkraft.net/yoyo/result ... =105733348

and also this machine has completed 3 ECM work units with granted credit.

[JagDoc]

This problem exists long time:
viewtopic.php?f=56&t=17100

[technik007.cz]

Radxa Zero 2GB

Succesfull units:


https://www.rechenkraft.net/yoyo/result ... =105841651

Result ID 105841651
Name sr2_167100000000000-167200000000000-S723-1721310749-1661_1
Workunit 74916072
Created 18 Jul 2024 13:52:34 UTC
Sent 19 Jul 2024 12:06:33 UTC
Received 21 Jul 2024 5:55:07 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 514002
Report deadline 24 Jul 2024 12:06:33 UTC
CPU time 138818.7
stderr out

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<stderr_txt>
14:52:25 (11196): wrapper (7.7.26016): starting
14:52:25 (11196): wrapper (7.7.26016): starting
14:52:25 (11196): wrapper: running ../../projects/www.rechenkraft.net_yoyo/sr2sieve_1.9.3.1_aarch64 (-i in -f factors.txt --pmin 167100000000000 --pmax 167200000000000 -v)
05:54:55 (11196): sr2sieve.exe exited; CPU time 138815.322435
05:54:55 (11196): called boinc_finish(0)

</stderr_txt>
]]>

Validate state Initial
Claimed credit 4544.750288544117
Granted credit 1000
application version 145.03



https://www.rechenkraft.net/yoyo/result ... =105841858

Result ID 105841858
Name sr2_177800000000000-177900000000000-S723-1721310776-1768_0
Workunit 74916179
Created 18 Jul 2024 13:52:59 UTC
Sent 19 Jul 2024 13:08:28 UTC
Received 21 Jul 2024 6:12:40 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 514002
Report deadline 24 Jul 2024 13:08:28 UTC
CPU time 139779.9
stderr out

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<stderr_txt>
14:53:35 (11231): wrapper (7.7.26016): starting
14:53:35 (11231): wrapper (7.7.26016): starting
14:53:35 (11231): wrapper: running ../../projects/www.rechenkraft.net_yoyo/sr2sieve_1.9.3.1_aarch64 (-i in -f factors.txt --pmin 177800000000000 --pmax 177900000000000 -v)
06:12:24 (11231): sr2sieve.exe exited; CPU time 139773.000252
06:12:24 (11231): called boinc_finish(0)

</stderr_txt>
]]>

Validate state Initial
Claimed credit 4576.218772093873
Granted credit 640.462576062241
application version 145.03

[technik007.cz]

Failed on the same machine:

https://www.rechenkraft.net/yoyo/result ... =105833390

Result ID 105833390
Name sr2_347400000000000-347500000000000-R795-1721038031-3464_2
Workunit 74889147
Created 17 Jul 2024 23:09:10 UTC
Sent 18 Jul 2024 0:15:12 UTC
Received 18 Jul 2024 0:20:08 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 193 (0xc1)
Computer ID 514002
Report deadline 23 Jul 2024 0:15:12 UTC
CPU time 0
stderr out

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
00:15:30 (2709): wrapper (7.7.26016): starting
00:15:30 (2709): wrapper (7.7.26016): starting
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
SIGABRT: abort called
Stack trace (3 frames):
[0x49741c]
[0xffffbdec0790]
[0x502598]

Exiting...

</stderr_txt>
]]>

Validate state Initial
Claimed credit 0
Granted credit 0
application version 145.03



https://www.rechenkraft.net/yoyo/result ... =105833369

Result ID 105833369
Name sr2_348200000000000-348300000000000-R795-1721038032-3472_2
Workunit 74889155
Created 17 Jul 2024 23:00:20 UTC
Sent 18 Jul 2024 0:15:12 UTC
Received 18 Jul 2024 0:20:08 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 193 (0xc1)
Computer ID 514002
Report deadline 23 Jul 2024 0:15:12 UTC
CPU time 0
stderr out

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
00:15:39 (2720): wrapper (7.7.26016): starting
00:15:39 (2720): wrapper (7.7.26016): starting
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
SIGABRT: abort called
Stack trace (3 frames):
[0x49741c]
[0xffffadbb5790]
[0x502598]

Exiting...

</stderr_txt>
]]>

Validate state Initial
Claimed credit 0
Granted credit 0
application version 145.03

[technik007.cz]

This problem exists long time:
viewtopic.php?f=56&t=17100

Ok, but do you know what is problem? Boinc servers use some techniques to cut off failing clients returning bad results. But what is differnce between faulty app and faulty computer in this case for them? None.
And as result of that some computers will stop receiving jobs from this project or not very ofter even there is nothing wrong with them. And start processing other ones. Not good for yoyo... project.

[Michael H.W. Weber]

That's why it is important, to report issues - otherwise they can't be fixed at all.

Michael.