AthlonXP
NForce2 chipset
HDD is far from full - 50GB free
Currently running Gentoo, but had this happen with earlier clients on Mandrake and Mandriva
I use BAM! to manage projects. I have 2 systems (the other one runs WinXP and does not have this problem).

I run boinc in X, I do not run in cli-only.

I find BOINC sitting inactive often. It will be full of completed units from various projects and the messages show no new entries for hours. I ask it to retry communications and nothing happens. I try to update a project and nothing happens. I try to sync with BAM and nothing happens.

I have to close the client and restart it to get it working. It closes without delay, it is not behaving like a hung app in this respect.

When the client comes up, it appears to run through the requests I made of it before closing it.

What is happening? Is this a Linux client peculiarity?
I searched and no Linux issues match this, not could I find it related to the client in general.
If I had not seen this occur in two completely separate Distros I would have thought it a config issue on my part. It has happened with every version of BOINC, not just 5.10.21

---

The only reason some people get lost in thought is because it's unfamiliar territory.
--Paul Fix

FWIW I've seen this happen in Fedora, Ubuntu, XP and Vista. So it's likely something in the client and not OS specific.

I was never able to reproduce it on demand, so it was hard to submit any sort of bug report.

---

Kathryn :o)

AthlonXP
Currently running Gentoo, but had this happen with earlier clients on Mandrake and Mandriva
I use BAM! to manage projects. I have 2 systems (the other one runs WinXP and does not have this problem).

I run boinc in X, I do not run in cli-only.

I find BOINC sitting inactive often. It will be full of completed units from various projects and the messages show no new entries for hours. I ask it to retry communications and nothing happens. I try to update a project and nothing happens. I try to sync with BAM and nothing happens.

I have to close the client and restart it to get it working. It closes without delay, it is not behaving like a hung app in this respect.

When the client comes up, it appears to run through the requests I made of it before closing it.

What is happening? Is this a Linux client peculiarity?
I searched and no Linux issues match this, not could I find it related to the client in general.
If I had not seen this occur in two completely separate Distros I would have thought it a config issue on my part. It has happened with every version of BOINC, not just 5.10.21

G'day ./aal

I run gentoo on most of my boxes and haven't experienced this problem. I self compile the boinc client (I don't use the gentoo ebuild or the Berkeley compiled executable).

It sounds like a config issue to me. I would install and setup BOINCView on your XP box as this could help you diagnose the problem. If it's a config issue (which I suspect - such as suspended because of time of day, user active, etc) the wu's on your linux box will show up grey and the reason will also show. If it's a hung science app the wu will show up yellow.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

I run gentoo on most of my boxes and haven't experienced this problem. I self compile the boinc client (I don't use the gentoo ebuild or the Berkeley compiled executable).


It sounds like a config issue to me. I would install and setup BOINCView on your XP box as this could help you diagnose the problem. If it's a config issue (which I suspect - such as suspended because of time of day, user active, etc) the wu's on your linux box will show up grey and the reason will also show. If it's a hung science app the wu will show up yellow.[/quote]

I did self compile on gentoo

And this does not happen on the XP system


I do not have it suspend ever, time of day or otherwise. This system sits idle most of the time, and it is set to used less cpu, but not suspend when I use the system.

The task lists does not show suspened, they have "waiting to run", "ready to start", "ready to report", or "running", but not "suspended"
The wu's are grey all the time, unless they are not selected, then they are white background, but there is no difference when BOINC has stopped. I can select as usual, but none of the command buttons do anything.

thank you for the replies, I hope this info helps track this down

---

The only reason some people get lost in thought is because it's unfamiliar territory.
--Paul Fix

The task lists does not show suspened, they have "waiting to run", "ready to start", "ready to report", or "running", but not "suspended"
The wu's are grey all the time, unless they are not selected, then they are white background, but there is no difference when BOINC has stopped. I can select as usual, but none of the command buttons do anything.

Is the above when you are using the BOINC Manager gui or when using BOINCView?

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

The task lists does not show suspened, they have "waiting to run", "ready to start", "ready to report", or "running", but not "suspended"
The wu's are grey all the time, unless they are not selected, then they are white background, but there is no difference when BOINC has stopped. I can select as usual, but none of the command buttons do anything.

Is the above when you are using the BOINC Manager gui or when using BOINCView?

BOINC Manager (e.g. run_manager)

---

The only reason some people get lost in thought is because it's unfamiliar territory.
--Paul Fix