Hi all, one of my hosts seems to be getting a lot of errors in the last few hours since the servers came back online Host ID: 879910 I have another three WU's that are yet to report and I noticed the run time is identical when they exit at 01:51:44 I am running AK's optimised app and they are non Cuda WU's, anyone having similar problems?
One of them link below

EXIT STATUS -177 (0xffffffffffffff4f)

http://setiathome.berkeley.edu/result.php?resultid=1698440392

---

Hi all, one of my hosts seems to be getting a lot of errors in the last few hours since the servers came back online Host ID: 879910 I have another three WU's that are yet to report and I noticed the run time is identical when they exit at 01:51:44 I am running AK's optimised app and they are non Cuda WU's, anyone having similar problems?
One of them link below

EXIT STATUS -177 (0xffffffffffffff4f)

http://setiathome.berkeley.edu/result.php?resultid=1698440392

There are a few threads with explanations as to the cause of these errors but as a quick fix you can download the new Reschedule tool by Fred which has an option to fix the problem. (The -177 happens when a task exits because it has reached a maximum timeout value)

New Reschedule tool

John.

---

GPU Users Group

-177 error is exceeded time allotted. In other words the tasks are taking longer than it was thought they would. The easiest way to cure this is to get EFmer's new reschedule tool. There are other ways and I'm sure others will chime in but the tool seems to be the best to me.


Edit: Thanks John, I didn't have the link.

---

PROUD MEMBER OF Team Starfire World BOINC

Error -177 stands for "Maximum elapsed time exceeded", so it's not surprising that they all had the same run time.

You could try a forum search (top left corner) for "-177" (without quotation marks).

Gruß,
Gundolf
[edit]Wow, three at a time![/edit]

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Thanks guys, I will try the reschedule app, I have been using the old one to get rid of vlars but it sounds like there is a new kid on the block.

---

Hi again, just a question re rescheduler, I thought it was for when the Cuda app gets the vlar's so they are sent to the cpu, my errors are on the cpu work units not the cuda, they keep on climbing in time to completion and wind up with the error, am I missing something?

---

Nope, not missing anything. They are probably old work sent back out again. The rescheduler will change the flops bound or whatever it's called so that it will judge the time correctly on both CPU and GPU work. Lots of improvements in this new rescheduler.

---

PROUD MEMBER OF Team Starfire World BOINC