Hi,

since the server-problem last week i can't fetch any workunits. An update to 6.2.15 don't fix this problem. I always receive the same message:

Mi 20 Aug 2008 18:49:43 CEST|SETI@home|Sending scheduler request: Requested by user. Requesting 604800 seconds of work, reporting 0 completed tasks
Mi 20 Aug 2008 18:49:48 CEST|SETI@home|Scheduler request succeeded: got 0 new tasks
Mi 20 Aug 2008 18:49:48 CEST|SETI@home|Message from server: No work sent

My settings are to connect every 3 days with additional 4 days of work. Changing this also don't help. Any ideas?

---

Hi,

since the server-problem last week i can't fetch any workunits. An update to 6.2.15 don't fix this problem. I always receive the same message:

Mi 20 Aug 2008 18:49:43 CEST|SETI@home|Sending scheduler request: Requested by user. Requesting 604800 seconds of work, reporting 0 completed tasks
Mi 20 Aug 2008 18:49:48 CEST|SETI@home|Scheduler request succeeded: got 0 new tasks
Mi 20 Aug 2008 18:49:48 CEST|SETI@home|Message from server: No work sent

My settings are to connect every 3 days with additional 4 days of work. Changing this also don't help. Any ideas?

The got 0 new tasks with no other information means that the server is temporarily out.

---

BOINC WIKI

The got 0 new tasks with no other information means that the server is temporarily out.

I know. I changed some settings at the preferences-web-page. Now i got following messages:

Mi 27 Aug 2008 22:35:54 CEST|SETI@home|Sending scheduler request: To fetch work. Requesting 172800 seconds of work, reporting 0 completed tasks
Mi 27 Aug 2008 22:35:59 CEST|SETI@home|Scheduler request succeeded: got 0 new tasks
Mi 27 Aug 2008 22:35:59 CEST|SETI@home|Message from server: No work sent
Mi 27 Aug 2008 22:35:59 CEST|SETI@home|Message from server: No work is available for SETI@home Enhanced
Mi 27 Aug 2008 22:35:59 CEST|SETI@home|Message from server: No work is available for Astropulse

At this messagetime the statuspage says 200.000+ WUs are available. Connectsettings: every 1 day with 1 additional day of work.

PC: IntelP4 2.53GHz 1GB RAM Fedora9

so what?

---

It looks like the server status page hasn't been updating in almost an hour. The messages below in your manager are confirming this.

It looks like the server status page hasn't been updating in almost an hour. The messages below in your manager are confirming this.

The problem is still active. A complete reinstall of BOINC (6.2.15) with all files doesn't solve the problem.

There's only one way to get at least one WU. Detach from project followed by an attach to the project. But while this WU is calculating the 'No work available...' messages coming again.

The whole trouble first appears after the big outage at the middle of august.

BTW: I got another computer running BOINC (5.10.45 dualcore xeon) where everything works fine.

---

Have you different cache settings on the other system ? - BOINC only downloads enought WUs to fit your WU cache. - I have checked you both systems and one system has only one WU in progress.

Have you different cache settings on the other system ?

Yes, but the same settings at home changed nothing.

BOINC only downloads enought WUs to fit your WU cache.

I know. But even when i set the WU cache to maximum i only get one WU. When it finish calculating the server sends no further work and brings the 'no work available' message even if the statuspage shows more than 200k WUs available.

I have checked you both systems and one system has only one WU in progress.

That's my PC with the trouble. Hey, deny the server WUs for systems which are to slow? (like my P4 2.53 GHz) ;-))

---

That's my PC with the trouble. Hey, deny the server WUs for systems which are too slow? (like my P4 2.53 GHz) ;-))

Definitely not! I have a 600MHz pc succesfully running SETI 5.27 under NT4.

Perhaps your time stats give a hint to your problem. Open client_state.xml with a text editor and search for <time_stats>. Then copy the lines between <time_stats> and </time_stats> here. Don't change anything in the file!

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

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

Perhaps your time stats give a hint to your problem. Open client_state.xml with a text editor and search for <time_stats>. Then copy the lines between <time_stats> and </time_stats> here. Don't change anything in the file!

Gruß,
Gundolf

Ok, here it is:

<time_stats>
<on_frac>0.577680</on_frac>
<connected_frac>-1.000000</connected_frac>
<active_frac>0.999920</active_frac>
<cpu_efficiency>0.984722</cpu_efficiency>
<last_update>1221430601.792535</last_update>
</time_stats>

I hope it helps.

MfG Matthias

---

...
I hope it helps.

MfG Matthias

Sorry, nothing unusual about those numbers. I had suspected a very low on_frac, perhaps from setting the system clock to the future.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

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