GNU/Linux S5R3 App 4.14 available for Beta test

Metod, S56RKO
Metod, S56RKO
Joined: 11 Feb 05
Posts: 135
Credit: 790,845,977
RAC: 15,076

I've just found a (minor?)

I've just found a (minor?) glitch with 4.14: it does not record CPU time consumed on one of my hosts. Some further details about host:

  • * Linux RedHat 7.3 (yep, I know it's ancient)
    * GLIBc version: 2.2.5 (ditto)
    * BOINC CC: 5.10.21 official
    * CPU: dual Pentium III (Coppermine) @ 1GHz
    * RAM: 2GB
    * Disk 9.5GB free on BOINC installation partition

It used to show CPU consumed just fine while it was running 4.09. It shows CPU time with S@H.

[edit2]
Not that it's sensible to bother with this problem too much if it only shows on my box: I can't even run official S@H apps on this box ...
[/edit2]

[edit]
Just noticed it has plenty of Couldn't sync errors. Filesystem in question is XFS.
These happen also on my other hosts that have XFS file systems.
[/edit]

Metod ...

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4,027
Credit: 215,242,228
RAC: 60,441

Good to know. Can you ty

Good to know.

Can you ty to switch off syncing on your XFS machines by putting EAH_NO_SYNC in your BOINC directory? In principle a "can't sync" message shouldn't be tragic, but it may unneccessarily fill up the stderr log.

BM

BM

Chris Kojiro
Chris Kojiro
Joined: 2 Mar 06
Posts: 4
Credit: 131,915,133
RAC: 0

Howdy, I've had a

Howdy,
I've had a similar problem as reported by Metod, where I've had results returned and validated, but reporting small (but non-zero) CPU time consumed.

E.g. 7.42 seconds
3.62 seconds
1.77 seconds
2.94 seconds
4.34 seconds
3.67 seconds
2.99 seconds

These are from 4 different computers. The first example was on a P4 2.8GHz, and the rest were on P4 3.6GHz boxes; and, the last 4 were all on the same computer.

They all have the same OS RHEL 3, 2.4.21 kernel.
Boinc version 5.8.16
glibc 2.3.2-95.50

I have succesfully run 4.14 on a RHEL4 machine (69,335 seconds). So, I'm thinking this has something to do with the kernel or glibc version. Hope this info helps find an explanation for this behavior.

Chris

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4,027
Credit: 215,242,228
RAC: 60,441

RE: [edit]Just noticed it

Message 74697 in response to message 74693

Quote:
[edit]Just noticed it has plenty of Couldn't sync errors. Filesystem in question is XFS.
These happen also on my other hosts that have XFS file systems.
[/edit]


Quote:
Can you ty to switch off syncing on your XFS machines by putting EAH_NO_SYNC in your BOINC directory? In principle a "can't sync" message shouldn't be tragic, but it may unneccessarily fill up the stderr log.


Actyally you should do that. I just found that in the code of the 4.14 App the checkpoint is actually not written at all in case of a sync error (has been fixed in the current code).

BM

BM

Conan
Conan
Joined: 19 Jun 05
Posts: 162
Credit: 5,937,946
RAC: 6

RE: Error being reported in

Message 74698 in response to message 74689

Quote:

Error being reported in this thread.

Result
Host

[pre]
Outcome Client error
Client state Compute error
Exit status 11 (0xb)[/pre]

Got one of these ones as well (Signal 11 error).
On this WU
One of the very few errors I have had on this project.
Running Beta 4.14, Linux on AMD Opteron.

Metod, S56RKO
Metod, S56RKO
Joined: 11 Feb 05
Posts: 135
Credit: 790,845,977
RAC: 15,076

RE: RE: Can you ty to

Message 74699 in response to message 74697

Quote:
Quote:
Can you ty to switch off syncing on your XFS machines by putting EAH_NO_SYNC in your BOINC directory? In principle a "can't sync" message shouldn't be tragic, but it may unneccessarily fill up the stderr log.

Actyally you should do that. I just found that in the code of the 4.14 App the checkpoint is actually not written at all in case of a sync error (has been fixed in the current code).

Where exactly should this file be and is there anything else to do? I can't seem to get it right. I've tried to put it in both BOINC installation folder as well as EAH project folder but it still shows can't sync errors. Should I restart BOINC or something?

Metod ...

Annika
Annika
Joined: 8 Aug 06
Posts: 720
Credit: 494,410
RAC: 0

Okay guys... seems like the

Okay guys... seems like the client errors were basically my own fault, or maybe that of my laptop manufacturer. Just getting back to let you know...
Apparently the WUs got killed by a problem which also caused frequent system freezes on this box (or maybe the freezes itself when the file system got damaged, dunno if this can happen on Linux boxes). I hunted the problem down over the weekend and it turned out to be old and very buggy firmware on my DVD burner. No idea why it was included in the first place, the laptop is almost new, but never mind. Luckily I was able to download a newer firmware version and update. Since then, the laptop has been rock solid- and miraculously the client errors have also stopped. I'm quite certain there is a connection between those things and I'll be fine now.
Sorry for indicating it might be a problem with BOINC.

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4,027
Credit: 215,242,228
RAC: 60,441

RE: Where exactly should

Message 74701 in response to message 74699

Quote:
Where exactly should this file be and is there anything else to do? I can't seem to get it right. I've tried to put it in both BOINC installation folder as well as EAH project folder but it still shows can't sync errors. Should I restart BOINC or something?


Probably easiest is to try the new 4.16 App. It will stop syncing automatically after 5 failures.

BM

BM

Conan
Conan
Joined: 19 Jun 05
Posts: 162
Credit: 5,937,946
RAC: 6

As I am still running App

As I am still running App version 4.14 on this computer, it was interesting to see that when I lost my ADSL connection last night I then lost 5 WU's in a row with Signal 11 errors.
This only happened on one host as no others lost WU's.

I think it is time to change up to a latter application.

Work units are
91403900
91435772
91600974
91601257
91607767

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.