LHC@home

Is anyone else having the problem where they seem to be downloading lots of work (I probably have more than 1,000) that are "lost") while spawing off new computers?

I detached from the project, but since I did not notice it for a week, well, it sure isn't pretty ...

I am going to leave that computer off for a bit and whack out the empty computers (if I can)

---

I haven't had that problem Paul, unless I spawned them myself ... hehe ... ;)

> Is anyone else having the problem where they seem to be downloading lots of
> work (I probably have more than 1,000) that are "lost") while spawing off new
> computers?
>
> I detached from the project, but since I did not notice it for a week, well,
> it sure isn't pretty ...
>
> I am going to leave that computer off for a bit and whack out the empty
> computers (if I can)
>
I haven't seen this problem. Perhaps you should check out Paul Bucks' Website. He has answers for just about everything. LOL

tony

> I haven't seen this problem. Perhaps you should check out Paul Bucks'
> Website. He has answers for just about everything. LOL

First place I looked and he did not know how to fix it either ...

---

> > I haven't seen this problem. Perhaps you should check out Paul Bucks'
> > Website. He has answers for just about everything. LOL
>
> First place I looked and he did not know how to fix it either ...
>


Funny lololol

---

BOINC Wiki

> Funny lololol

Sorry, it is the only sense of humor I have ...

---

Don't be sorry. I loved the humor.

Jim

> > Funny lololol
>
> Sorry, it is the only sense of humor I have ...
>

---

Paul,

Do you have BOINC installed as a service? I seem to remember a while back that a similar problem was cropping up on other projects where the service was having problems with machines that had frequently used logins without administrator rights. Those machines would download thousands of workunits, also. Just a thought...

Scott

Good funny thread here.

Scott most likely has the real answer. It is probably a permissions error. If BOINC can not open the client_state.xml file for writing it will create a new one each time you try to start the client.

If it is just this project doing that reset the project. It may be a problem with (caused by) the signatures.

---

BOINC WIKI

BOINCing since 2002/12/8

Yes Paul, I had this happen with every project on the new Manager versions that hadn't gotten their app files signed. Luckily I'm on a dial-up connection so that it didn't blow thru too many units. Once the project's app files got their digital signatures everything calmed back down.

Hmm,

I don't install as service. I sit by the computers most of the day every day, and all they do (most of them) is BOINC ... so, with the GUI off, no screen saver I don't see how the service can be better. Ah, well ..

Ok, well, I took that computer off line for the time being ... I think it currently has 1400+ Wu queued up.

NOt listening to my own advice I need to drain my queues some ... I thought 2 days was conservative enough ...

The only files locked were locked by BOINC, so when I disconnected from the project and stopped BOINC I whacked them out. Once I get down to 0.1 days :)

well, MAYBE I will try that one again ...

Heck, if it was easy, ANYONE could play ...

---