Hi folks,

Finally my native linux machine (64bit 18.04 LTS) got a WU hadcm3s_c0r1_204412_120_602_011361658_1
and......killed it in 16 seconds with the following

<core_client_version>7.9.3</core_client_version>
<![CDATA[
<message>
process exited with code 22 (0x16, -234)</message>
<stderr_txt>
forrtl: severe (17): syntax error in NAMELIST input, unit 5, file /var/lib/boinc-client/projects/climateprediction.net/hadcm3s_c0r1_204412_120_602_011361658/jobs/climate.cpdc, line 396, position 20
Image PC Routine Line Source
hadcm3s_um_8.34_i 0848A415 Unknown Unknown Unknown
hadcm3s_um_8.34_i 084AF3E6 Unknown Unknown Unknown
hadcm3s_um_8.34_i 082C77B5 Unknown Unknown Unknown
hadcm3s_um_8.34_i 081C028B Unknown Unknown Unknown
hadcm3s_um_8.34_i 081C1E0A Unknown Unknown Unknown
hadcm3s_um_8.34_i 083F95C9 Unknown Unknown Unknown
hadcm3s_um_8.34_i 083F867F Unknown Unknown Unknown
hadcm3s_um_8.34_i 0840346D Unknown Unknown Unknown
Controller:: CPDN process is not running, exiting, bRetVal = 1, checkPID=0, selfPID=16535, iMonCtr=1
Model crash detected, will try to restart...

I checked the libraries and seem fine
sudo ldd hadcm3s_um_8.34_i686-pc-linux-gnu
linux-gate.so.1 (0xf7f5d000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7f32000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7e30000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7e11000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7c35000)
/lib/ld-linux.so.2 (0xf7f5f0

any ideas

Interesting. Someone previously had run a task in that specific work unit til at least one trickle, but yours died immediately.

The syntax error suggests that there was something wrong with the climate.cpdc file on your disk. This could be a corrupted file that was downloaded from the server, or a corruption of that file that occurred on your disk or in transmission.

The batch was issued in late 2017 and they have about 60% success rate from it so the loss of that task is no big deal.

And just for completeness, for the hadcm3 tasks, it's also good to do a

sudo ldd hadcm3s_se_8.34_i686-pc-linux-gnu.so

as the library requirements are slightly different than the um.

sudo ldd hadcm3s_se_8.34_i686-pc-linux-gnu.so

as the library requirements are slightly different than the um.

for this I got
ldd: ./hadcm3s_se_8.34_i686-pc-linux-gnu: No such file or directory

though ls -la show
-rwx------ 1 boinc boinc 2583233 Mar 23 2017 hadcm3s_se_8.34_i686-pc-linux-gnu.so
-rwxr-xr-x 1 boinc boinc 906190 Dec 30 20:03 hadcm3s_se_8.34_i686-pc-linux-gnu.zip
and permissions are different than um's -rwxr-xr-x

the only other hadcm3s gives the following
sudo ldd hadcm3s_8.34_i686-pc-linux-gnu

linux-gate.so.1 (0xf7ee8000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7ea3000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7e9e000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf7d18000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7c16000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7bf8000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7a1c000)
/lib/ld-linux.so.2 (0xf7eea000)

I have the same permissions on that file, but if I do a

sudo ldd hadcm3s_se_8.34_i686-pc-linux-gnu.so

it produces the following, which includes the libz 386 version. If that version of libz is not there, problems can occur.

linux-gate.so.1 (0xf7edd000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf7e12000)
libnsl.so.1 => /lib/i386-linux-gnu/libnsl.so.1 (0xf7df7000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf7c71000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7b6f000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7b51000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7975000)
/lib/ld-linux.so.2 (0xf7edf000)

Not that I think this is the problem you had, but I've seen it in others who thought they had all the necessary 32bit libraries because they had the other hadcm3s 32bit requirements.

I have the same permissions on that file, but if I do a

sudo ldd hadcm3s_se_8.34_i686-pc-linux-gnu.so

I got the same it is all there. Hopefully new linux WUs will come so we can test some crash. Thanks

I just got 2 hadcm3s batch 643 and killed them both in 16 sec with the same report as in my first post.

I just got 2 hadcm3s batch 643 and killed them both in 16 sec with the same report as in my first post.

Batch 643 is so old it is closed anyway or on the list to be closed.