Since 20 February my results that have been uploaded are still pending for credit. That is not a problem as it could take a few daqys. However since last night finished WU's are still uploading.
This is a part of messages:
22/02/2010 12:41:30 rosetta@home Requesting new tasks
22/02/2010 12:41:46 rosetta@home Scheduler request failed: Couldn't resolve host name
22/02/2010 12:42:46 rosetta@home Sending scheduler request: To fetch work.
22/02/2010 12:42:46 rosetta@home Requesting new tasks
22/02/2010 12:43:02 rosetta@home Scheduler request failed: Couldn't resolve host name

Can someone of the dev please look at this?
Thanks.

---

Greetings,
TJ.

Since 20 February my results that have been uploaded are still pending for credit. That is not a problem as it could take a few daqys. However since last night finished WU's are still uploading.
This is a part of messages:
22/02/2010 12:41:30 rosetta@home Requesting new tasks
22/02/2010 12:41:46 rosetta@home Scheduler request failed: Couldn't resolve host name
22/02/2010 12:42:46 rosetta@home Sending scheduler request: To fetch work.
22/02/2010 12:42:46 rosetta@home Requesting new tasks
22/02/2010 12:43:02 rosetta@home Scheduler request failed: Couldn't resolve host name

Can someone of the dev please look at this?
Thanks.

I also have added a message under Server Problems about the Pending Issue.
I now have over 2 pages of Pending work units.

The message about "Couldn't Resolve Host Name" usually means that your local Internet connection has been interrupted towards the Boinc Server and your local Boinc Client (on your computer) can't talk to the Rosetta Server.

I am not getting that message myself so I can talk to the servers (from Australia), but I have gotten it in the past for short periods even though I can still use my own internet quite OK.

I would say it is an issue with the Rosetta Boinc server losing it's internet connection or a problem with their internet Provider, but also check that your own internet is still working OK.

---

Thanks for your input Conan,

I have checked my internet connection beforehand and Einstein and Milkyway where and are still "talking" with my computers.

Perhaps Rosetta solves it in the course of the day.

---

Greetings,
TJ.

I noticed a huge drop off in my average credits over the week-end and now see I have 16,000 pending credits. It appears that everthing sicne around Friday evening has been put into pending.

Since 20 February my results that have been uploaded are still pending for credit. That is not a problem as it could take a few daqys. However since last night finished WU's are still uploading.
This is a part of messages:
22/02/2010 12:41:30 rosetta@home Requesting new tasks
22/02/2010 12:41:46 rosetta@home Scheduler request failed: Couldn't resolve host name
22/02/2010 12:42:46 rosetta@home Sending scheduler request: To fetch work.
22/02/2010 12:42:46 rosetta@home Requesting new tasks
22/02/2010 12:43:02 rosetta@home Scheduler request failed: Couldn't resolve host name

Can someone of the dev please look at this?
Thanks.

Most of my tasks over the last 3 days, stuck in a state of "pending" too.
Apparently this is due to the validator failure (rah_validator_mini = Not running)
I only get credits for "rossmann3x3..." tasks. Seems because it runs on different application (Rosetta Beta 5.98), with own validator (rah_validator_beta = Running)
So what you have to wait until devs fix rah_validator_mini...

I have 3 screens' worth of pending, total value approx. 3300 credits.

---

The validator is back running now and I've noticed a few WUs have already been awarded.

A big day for credits today to make up for the weekend. Panic over.

Edit: Well that's fastest 2000 credits I've ever had!

Just 3 left to validate, but 2 validate errors in the process. I'll cope.

---

Just 3 left to validate, but 2 validate errors in the process. I'll cope.

I only had 3 Rosetta WUs stuck waiting for the mini validator to come back up, but 2 of them (291252049 & 291252024) also failed to validate. After reading the previous post, I suspect the validator wasn't feeling well when it processed them. Based on this host's (1184796) past performance, I think a server-side, rather than a client-side issue is more likely.

I'm not whining about a few hundred credits here...you can keep 'em, I have more. I really believe project administration should take a look at this validator's performance since it came back up. But as the philosopher says, "that's just my opinion, I could be wrong."

---

Best wishes:)

I have validate error too: https://boinc.bakerlab.org/rosetta/workunit.php?wuid=291359005
And these WU is the same type as listed in the jjwhalen's post: placestub_1sq2_*

I'm not whining about a few hundred credits here...you can keep 'em, I have more. I really believe project administration should take a look at this validator's performance since it came back up. But as the philosopher says, "that's just my opinion, I could be wrong."

If I'm not mistaken another job runs each day (or two) that picks up all the validate errors and awards them the same value as the claimed credit. Isn't that right, someone?

If so, I'd be more concerned that the project gets the benefit of the processing. Does the job's results get accepted properly for the science part?

Sent in 44 wu's after validator went down.
17 Validate errors
4 still pending

Come on guys, your just spinnin my power meter here.
Im sure Alabama power loves you for it but I'm just not feelin the "love"

I got 4 validate errors out of 12 tasks, not good odds

some of them have been since the validator restarted. :(

---

I'm still getting the validate errors on wu's sent yesterday.
have flushed everything and starting fresh - even my drink
dunno if its gonna fix things, but I can say the drink tastes better!
wish me luck ;)

Just 3 left to validate, but 2 validate errors in the process. I'll cope.

I only had 3 Rosetta WUs stuck waiting for the mini validator to come back up, but 2 of them (291252049 & 291252024) also failed to validate. After reading the previous post, I suspect the validator wasn't feeling well when it processed them...

I'm not whining about a few hundred credits here... you can keep 'em, I have more. I really believe project administration should take a look at this validator's performance since it came back up. But as the philosopher says, "that's just my opinion, I could be wrong."

As mentioned earlier, both those jobs have been awarded full claimed credit in spite of the validate error. One was sent to a wingman and validated properly. Another went out again and produced another validate error. Short story, everyone here gets the credits so nothing to worry about there.

The server is coming up green on everything, but there are still a few validate errors and delays in awarding them, so it does appear there's a remaining issue somewhere.

Could someone at TPTB take a look at it and report back please?

---

The server is coming up green on everything, but there are still a few validate errors and delays in awarding them, so it does appear there's a remaining issue somewhere.

Could someone at TPTB take a look at it and report back please?

I noticed the server went down for a while last night and came back up soon enough. Now validation is going through much better. I assume this is all fixed now, but a confirmation would still be appreciated.

---

The message about "Couldn't Resolve Host Name" usually means that your local Internet connection has been interrupted towards the Boinc Server and your local Boinc Client (on your computer) can't talk to the Rosetta Server.

Likely to depend on what ISP you're using. For mine, it usually means that the DNS server you're using for turning host names into IP addresses isn't working, even if the rest of the internet is still working and you can still reach any other hosts for which your computer has saved the IP address from the last time it contacted that host.

I'm not whining about a few hundred credits here...you can keep 'em, I have more. I really believe project administration should take a look at this validator's performance since it came back up. But as the philosopher says, "that's just my opinion, I could be wrong."

If I'm not mistaken another job runs each day (or two) that picks up all the validate errors and awards them the same value as the claimed credit. Isn't that right, someone?

If so, I'd be more concerned that the project gets the benefit of the processing. Does the job's results get accepted properly for the science part?

I'd expect to be more like manual intervention to inspect any workunits for which too many people got validate errors, and then either adjust the validator and run it on on those workunits again, or manually determine the valid parts of the workunit outputs and award credits for just those parts.

What you suggest might be true for the workunits closer to beta testing of new program sections, though, since for those workunits, testing the software is more important than getting scientific results.