climateprediction.net (CPDN) home page
Thread 'Tasks complete OK, but Stderr is strange.'

Thread 'Tasks complete OK, but Stderr is strange.'

Message boards : Number crunching : Tasks complete OK, but Stderr is strange.
Message board moderation

To post messages, you must log in.

AuthorMessage
Jean-David Beyer

Send message
Joined: 5 Aug 04
Posts: 1120
Credit: 17,202,915
RAC: 2,154
Message 66382 - Posted: 13 Nov 2022, 13:34:33 UTC

My machine just completed three tasks, but the stderr does not seem right.. Is this how it is supposed to be? Here is one of them:

Task 22237605
Name 	hadsm4_a1b9_201311_4_938_012156263_0
Workunit 	12156263
Created 	11 Nov 2022, 11:37:42 UTC
Sent 	11 Nov 2022, 12:24:02 UTC
Report deadline 	24 Oct 2023, 17:44:02 UTC
Received 	13 Nov 2022, 11:23:21 UTC
Server state 	Over
Outcome 	Success
Client state 	Done
Exit status 	0 (0x00000000)
Computer ID 	1511241

Stderr 	

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<stderr_txt>
Suspended CPDN Monitor - Suspend request from BOINC...
Signal 15 received: Software termination signal from kill 
Signal 15 received: Abnormal termination triggered by abort call <---<<<
Signal 15 received, exiting...
12:39:19 (1159872): called boinc_finish(193)
Suspended CPDN Monitor - Suspend request from BOINC...
06:22:41 (40471): called boinc_finish(0)

</stderr_txt>
]]>



Old ones from last July end this way:
(hadsm4_a23u_201310_6_935_012149492_4)

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<stderr_txt>
Suspended CPDN Monitor - Suspend request from BOINC...
Suspended CPDN Monitor - Suspend request from BOINC...
11:09:13 (154220): called boinc_finish(0)


</stderr_txt>
]]>

Is this OK or is something wrong?
ID: 66382 · Report as offensive     Reply Quote
ProfileDave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 4540
Credit: 19,039,635
RAC: 18,944
Message 66383 - Posted: 13 Nov 2022, 15:04:05 UTC - in response to Message 66382.  

I don't think it is a biggie. Though just checked two of my completed tasks from the latest batch and they both have the same in stderr as your old ones. I will cogitate and see if my brain comes up with anything. - Pretty sure I have seen what you have in your three before somewhere.
ID: 66383 · Report as offensive     Reply Quote
Jean-David Beyer

Send message
Joined: 5 Aug 04
Posts: 1120
Credit: 17,202,915
RAC: 2,154
Message 66384 - Posted: 13 Nov 2022, 18:37:42 UTC - in response to Message 66383.  

I have two more of that batch currently running. They should finish in about 6.5 hours for the first of these and a little over a day for the second. I will see how they finish.
ID: 66384 · Report as offensive     Reply Quote
Richard Haselgrove

Send message
Joined: 1 Jan 07
Posts: 1061
Credit: 36,716,561
RAC: 8,355
Message 66385 - Posted: 13 Nov 2022, 19:05:55 UTC

I've just finished task 22236971 - absolutely minimal stderr.

<core_client_version>7.18.1</core_client_version>
<![CDATA[
<stderr_txt>
17:46:49 (536107): called boinc_finish(0)

</stderr_txt>
]]>
ID: 66385 · Report as offensive     Reply Quote
Jean-David Beyer

Send message
Joined: 5 Aug 04
Posts: 1120
Credit: 17,202,915
RAC: 2,154
Message 66386 - Posted: 13 Nov 2022, 20:59:15 UTC - in response to Message 66384.  

For the record, I am running
Red Hat Enterprise Linux release 8.6 (Ootpa)
with this kernel
4.18.0-372.26.1.el8_6.x86_64
Ths kernel runs SELinux (security enhanced linux), but I have always been running that.
However I notice my main boinc client stuff just got updated.

[/usr/bin]$ ls -l boinc*
-rwxr-xr-x. 2 root root 1112184 Jul 29 09:36 boinc
-rwxr-xr-x. 2 root root 1112184 Jul 29 09:36 boinc_client
-rwxr-xr-x. 1 root root  358784 Jul 29 09:36 boinccmd
-rwxr-xr-x. 1 root root 4081696 Jul 29 09:36 boincmgr
-rwxr-xr-x. 1 root root  350704 Jul 29 09:36 boincscr


The last one I got that completed correctly was done
30 Jul 2022, 15:12:15 UTC, so I guess it is not my client software making the problem..
ID: 66386 · Report as offensive     Reply Quote
Jean-David Beyer

Send message
Joined: 5 Aug 04
Posts: 1120
Credit: 17,202,915
RAC: 2,154
Message 66388 - Posted: 14 Nov 2022, 1:04:54 UTC - in response to Message 66384.  

This one just finished, and completed OK.
So I guess I will never know why those other three, while they worked OK, terminated so peculiarly.

Task 22236843
Name 	hadsm4_a0q3_201311_4_938_012155501_0
Workunit 	12155501
Created 	11 Nov 2022, 11:15:45 UTC
Sent 	11 Nov 2022, 12:24:02 UTC
Report deadline 	24 Oct 2023, 17:44:02 UTC
Received 	14 Nov 2022, 0:56:58 UTC
Server state 	Over
Outcome 	Success
Client state 	Done
Exit status 	0 (0x00000000)
Computer ID 	1511241
Run time 	1 days 22 hours 37 min 37 sec
CPU time 	1 days 22 hours 14 min 3 sec
Validate state 	Valid
Credit 	3,230.53
Device peak FLOPS 	6.13 GFLOPS
Application version 	UK Met Office HadSM4 at N144 resolution v8.02
i686-pc-linux-gnu
Peak working set size 	658.42 MB
Peak swap size 	787.61 MB
Peak disk usage 	143.01 MB
Stderr 	

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<stderr_txt>
Suspended CPDN Monitor - Suspend request from BOINC...
19:53:39 (64085): called boinc_finish(0)

</stderr_txt>
]]>

ID: 66388 · Report as offensive     Reply Quote

Message boards : Number crunching : Tasks complete OK, but Stderr is strange.

©2024 cpdn.org