LHC@home

I have installed a new validator and a new assimilator. Let us see if this solves the problem.

---

Chrulle
Research Assistant & Ex-LHC@home developer
Niels Bohr Institute

I have two hosts with disabled network-access and pending credits.
host: 47319 credits: 21967.37 pending: 3 results
host: 57272 credits:7879.67 pending: 2 results
both hosts show correct information (unsure about "Average turnaround time")
I will keep an eye on them this afternoon and see if any pending credits are rewarded.

So far so good. I have several corrupted host records on my account, but the hosts they relate to have created new records for themselves and (crossed fingers) the corruption doesn't appear to have affected these new records.

---

I have installed a new validator and a new assimilator. Let us see if this solves the problem.

It won't solve it, I'm afraid.
My last contact (upload) is approx. 1000 UTC, my last validated result is approx. at 1100. I belive only database of hosts is getting corrupted continuously.

---

Well, since the new processes where installed after 1100 UTC it could still work.

---

Chrulle
Research Assistant & Ex-LHC@home developer
Niels Bohr Institute

You were right. I reset the project and it started to download new WU immediately. Also values in my host record are OK now.

---

You were right. I reset the project and it started to download new WU immediately. Also values in my host record are OK now.

Question @ JardaM
Did the reset also solve the daily quota 'failure'? (from previous misswriting of the quantity to 0 WU/day)
From another post I saw you had the same problem as I. Your qoute:

It wozuldn't bother me much but the problem is that rewrites also No. of WUs allowed per day. This practically cuts me off from your source. I cannot get any fresh WU any longer.

greetz littleBouncer
BTW: I reported one success WU, but the daily quota didn't change (host 41625)...

---

Your fix corrected the host information on a host that had corrupted over night prior to your fix. However, the host location did not update from the corrupted value of 0 (the other information was ok) reset the host location to the location I desired for that host and will now watch and see if it holds.

---

Result of 1 WU uploaded, host still OK.

Result of that WU reported 10 minutes after the upload and credit granted immediately, host still OK. Location still OK too.

Not sure yet - host venues now seem OK, as do the operating system entries, but this host (23752) still has a 12wu/day limit, and won't retrieve new work because of this, even though it's only had 9 results delivered to it in the last 24 hours.

---

Gaspode the UnDressed
http://www.littlevale.co.uk

Very powerfull host 62217?

LHC@home - 2005-10-26 15:21:54 - Message from server: No work sent (reached daily quota of 200 results)

Wow, I never thought, that this host can do so many WUs a day ;-)
.. or is there something wrong with the scheduler?

Greeting!

---

26-Oct-05 16:34:24|LHC@home|Message from server: No work sent
26-Oct-05 16:34:24|LHC@home|Message from server: (reached daily quota of 100 results)

Get this MSG from the server although my host has no WU's left to crunch.
What's up ?

---

all my active hosts have updated succesfully, host-information remained intact after credit was granted.

Only problem left is the
10/26/2005 4:48:54 PM|LHC@home|Message from server: No work sent
10/26/2005 4:48:54 PM|LHC@home|Message from server: (reached daily quota of 200 results)
message, so far I have only seen it on host 47319, which is a dual-cpu system
my dual Xeon (4 logical cpu's) downloaded new results without a problem.

Just manually updated the wu's from overnight crunching and host info is now remaining intact here after a credit update.

---

Get BOINC WIKIed

The only 'thing' I noted after a manually update (only sending 2 WU's back).
Why there is the bolded line (see bellow)?

26.10.2005 18:49:53|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
26.10.2005 18:49:53|LHC@home|Reason: Requested by user
26.10.2005 18:49:53|LHC@home|Requesting 0 seconds of work, returning 2 results
26.10.2005 18:50:02|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
26.10.2005 18:50:03|LHC@home|Deferring communication with project for 5 seconds

IMO:That is something unnessecary, or I'm wrong?

greetz littleBouncer
otherwise no problems with that host 45610

---

26.10.2005 18:50:03|LHC@home|Deferring communication with project for 5 seconds

IMO:That is something unnessecary, or I'm wrong?

To guard against clients flooding scheduling-server with requests, there's for a long time been a project-specific limit between how often scheduling-server accepts connections.

A resent change is that the scheduling-server now always sends this limit in all replys, this stops clients from immediately asking again, but getting hit by a "too resent"-message.


Of course, with projects like LHC@home that uses 5?-second-limit it's mostly superfluous to be told to wait 7 seconds... but since it's an informal message meaning doesn't show up as red, it shouldn't be a problem. ;)


BTW, the deferral is always a little bit longer than the limit, to guard against computers with too-fast clock being stuck in an infinite loop of asking, "too resent" wait 1 minute, contacts after 59.99 seconds and "too resent".

26.10.2005 18:50:03|LHC@home|Deferring communication with project for 5 seconds

IMO:That is something unnessecary, or I'm wrong?

To guard against clients flooding scheduling-server with requests, there's for a long time been a project-specific limit between how often scheduling-server accepts connections.

A resent change is that the scheduling-server now always sends this limit in all replys, this stops clients from immediately asking again, but getting hit by a "too resent"-message.


Of course, with projects like LHC@home that uses 5?-second-limit it's mostly superfluous to be told to wait 7 seconds... but since it's an informal message meaning doesn't show up as red, it shouldn't be a problem. ;)


BTW, the deferral is always a little bit longer than the limit, to guard against computers with too-fast clock being stuck in an infinite loop of asking, "too resent" wait 1 minute, contacts after 59.99 seconds and "too resent".

@ Ingleside
THX for your informativ reply!
you wrote:"but since it's an informal message meaning doesn't show up as red, it shouldn't be a problem."
But this message:
26.10.2005 18:50:03|LHC@home|Deferring communication with project for 5 seconds
is in red!!! and appaers after each request.
(edit):After the 5 second of deferring the client doesn't request at new! (what is right, but the line is unnessecary), that's why I was asking, because normally it requests after the announced deferring time...

greetz littleBouncer

But this message:
26.10.2005 18:50:03|LHC@home|Deferring communication with project for 5 seconds
is in red!!! and appaers after each request.

It's only showing red if you're running an old client, not if you're running v5.2.x ;)

Sorry never mind -- misread the timestamp on some log messages. Updating venue manually fixed the client's messages eventually.

But this message:
26.10.2005 18:50:03|LHC@home|Deferring communication with project for 5 seconds
is in red!!! and appaers after each request.

It's only showing red if you're running an old client, not if you're running v5.2.x ;)

@ Ingleside
Sorry , it is a 4.72, I will upgrade when all works fine with the server after it's upgrade, that's why I'm not yet on 5.2.x.;)

greetz littleBouncer