Are their maybe some data tapes left to crunch?.
All my crunchers are running low...

Best regards,

# Bob Ahlers #

Now i see more channels available but my crunchers arent able to get new WU's.

7/18/2009 5:07:01 PM SETI@home Scheduler request failed: Failure when receiving data from the peer

It is online though, whats going on?

Can someone explain what this Failure when receiving data from the peer means please? I am a newbie when it comes to programming etc

---

I guess - if the scheduler contact wasn't complete/successful.

Nothing to worry about.

---

Now i see more channels available but my crunchers arent able to get new WU's.

7/18/2009 5:07:01 PM SETI@home Scheduler request failed: Failure when receiving data from the peer

It is online though, whats going on?

You contact the Scheduler (report results/request work) and send the file "sched_request_setiathome.berkeley.edu.xml" the Scheduler acknowledges and looks to see if you need work and then will reply with the file "sched_reply_setiathome.berkeley.edu.xml"

Generally the error means is that you did Not receive a "Good" copy of the file. It will recover on the next Scheduler request (scheduled automatically).

---

Please consider a Donation to the Seti Project.

It looks like the scheduler is down orso.
Even when i manual request an update it says:

7/18/2009 6:56:55 PM SETI@home update requested by user
7/18/2009 6:56:58 PM SETI@home Sending scheduler request: Requested by user.
7/18/2009 6:56:58 PM SETI@home Requesting new tasks
7/18/2009 6:57:04 PM Project communication failed: attempting access to reference site
7/18/2009 6:57:05 PM Internet access OK - project servers may be temporarily down.
7/18/2009 6:57:08 PM SETI@home Scheduler request failed: Failure when receiving data from the peer

Is it me, or is the scheduler down?

Now you can see at the 'status page' that most of the servers are back online again.

Earlier today (Dutch time) almost everything was red (=trouble). Almost everything was down! Now it's green (=ok) or orange (=disabled). Disabled means that someone turned that particular machine off, which means someone found the time this weekend to get (most of it) up and running again!


PS: Bob, welkom bij ons team!

---

The SETI@Home Gauntlet 2012 april 16 - 30| info / chat | STATS

It looks like the scheduler is down orso.
Even when i manual request an update it says:

7/18/2009 6:56:55 PM SETI@home update requested by user
7/18/2009 6:56:58 PM SETI@home Sending scheduler request: Requested by user.
7/18/2009 6:56:58 PM SETI@home Requesting new tasks
7/18/2009 6:57:04 PM Project communication failed: attempting access to reference site
7/18/2009 6:57:05 PM Internet access OK - project servers may be temporarily down.
7/18/2009 6:57:08 PM SETI@home Scheduler request failed: Failure when receiving data from the peer

Is it me, or is the scheduler down?

Hi Bob,

I turned my machine back on about an hour ago, but can't seem to 'connect' to seti at all. Tried a restart of boinc, a flushdns and even a reboot of the machine. No luck so far. I always get a 'couldn't connect' or an 'http-error' message. And a manually forced update results in the 'failure when receiving data from peer'. Something must be wrong with the servers, I guess. I haven't had these types of messages even when network traffic was extremely high. Oh well, it's now early morning in Berkeley, so maybe will have a look at it in a couple of hours.

Regards,
John.


7/18/2009 6:56:08 PM SETI@home Started upload of 05dc08ae.23944.16023.11.8.244_0_0
7/18/2009 6:56:30 PM Project communication failed: attempting access to reference site
7/18/2009 6:56:30 PM SETI@home Temporarily failed upload of 05dc08ae.23944.16023.11.8.244_0_0: connect() failed
7/18/2009 6:56:30 PM SETI@home Backing off 2 hr 35 min 40 sec on upload of 05dc08ae.23944.16023.11.8.244_0_0
7/18/2009 6:56:31 PM Internet access OK - project servers may be temporarily down.

I know, i also saw that.
But even when the servers are ok (like now) i still get the messages that the scheduler is not responding.

I wonder if that fix that Eric put in did not come back up with the restart of the servers?

---

Upload queue = empty
cache setting = 10 days
current (estimated) amount of work = 7.5 days

I'm not getting any more work, just keeps saying:

Mon 20 Jul 2009 04:53:13 PM KST|SETI@home|Sending scheduler request: To report completed tasks. Requesting 0 seconds of work, reporting 1 completed tasks
Mon 20 Jul 2009 04:53:18 PM KST|SETI@home|Scheduler request completed: got 0 new tasks


Now... shouldn't it try to get more work? Yes, I have enough to work through for a while, but nothing for my CPUs (all I have is for GPU), so why am I not getting more work?

Upload queue = empty
cache setting = 10 days
current (estimated) amount of work = 7.5 days

I'm not getting any more work, just keeps saying:

Mon 20 Jul 2009 04:53:13 PM KST|SETI@home|Sending scheduler request: To report completed tasks. Requesting 0 seconds of work, reporting 1 completed tasks
Mon 20 Jul 2009 04:53:18 PM KST|SETI@home|Scheduler request completed: got 0 new tasks

Now... shouldn't it try to get more work? Yes, I have enough to work through for a while, but nothing for my CPUs (all I have is for GPU), so why am I not getting more work?

1) You've probably got some 7-day deadline stuff in the mix. It won't fetch more while you've got potential deadline-busters on board.

2) That old BOINC v6.4.5 you're having to use. It will only fetch work for the highest version number in your system (608), because it doesn't understand about <plan_class>. You have two choices: find out (or work with the developers and Linux volunteers to find out) why you can't get both CUDA cards working under BOINC v6.6.xx: or (2) study the logic of the re-branding scripts, and write one that works on Linux but doesn't rely on <plan_class> (just changing 608 to 603 is enough under v6.4.5, and it can run them after re-branding, it just won't ever fetch them).

Upload queue = empty
cache setting = 10 days
current (estimated) amount of work = 7.5 days

I'm not getting any more work, just keeps saying:

Mon 20 Jul 2009 04:53:13 PM KST|SETI@home|Sending scheduler request: To report completed tasks. Requesting 0 seconds of work, reporting 1 completed tasks
Mon 20 Jul 2009 04:53:18 PM KST|SETI@home|Scheduler request completed: got 0 new tasks

Now... shouldn't it try to get more work? Yes, I have enough to work through for a while, but nothing for my CPUs (all I have is for GPU), so why am I not getting more work?

1) You've probably got some 7-day deadline stuff in the mix. It won't fetch more while you've got potential deadline-busters on board.

2) That old BOINC v6.4.5 you're having to use. It will only fetch work for the highest version number in your system (608), because it doesn't understand about <plan_class>. You have two choices: find out (or work with the developers and Linux volunteers to find out) why you can't get both CUDA cards working under BOINC v6.6.xx: or (2) study the logic of the re-branding scripts, and write one that works on Linux but doesn't rely on <plan_class> (just changing 608 to 603 is enough under v6.4.5, and it can run them after re-branding, it just won't ever fetch them).

Not fully understanding the re-branding part, but the reason it doesn't work under 6.6.x is that those versions see two CUDA devices, but assigns them both to the same device.

SuSE Linux 10.3, BOINC 6.6.31. I have 3 MB WUs trying to upload, one running and 2 waiting to start. SETI continues giving me work, only uploads are slow.
Tullio

---

Solution (for 6.4.5 users) is here:

http://setiathome.berkeley.edu/forum_thread.php?id=54707&nowrap=true#919675

It works great, now I have my CPUs and GPUs crunching away. If I have some time this weekend I'll write a script for any other Linux users out there having the same issues I am to speed it up. If I have A LOT more time than I expect I'll see if I can find the problem in 6.6.36 and fix it too(programmer by trade, but my paying job takes most of my free time, heh).