For the last two days, the BOINC client on my Linux box has been unable to retrieve work units.

2005-07-03 07:42:15 [---] Starting BOINC client version 4.43 for i686-pc-linux-gnu
2005-07-03 07:42:15 [---] Data directory: /usr/local/sbin/BOINC
2005-07-03 07:42:15 [---] No general preferences found - using BOINC defaults
2005-07-03 07:42:15 [---] Remote control not allowed; using loopback address
2005-07-03 07:42:17 [---] Running CPU benchmarks
2005-07-03 07:43:14 [---] Benchmark results:
2005-07-03 07:43:14 [---] Number of CPUs: 1
2005-07-03 07:43:14 [---] 184 double precision MIPS (Whetstone) per CPU
2005-07-03 07:43:14 [---] 650 integer MIPS (Dhrystone) per CPU
2005-07-03 07:43:14 [---] Finished CPU benchmarks
2005-07-03 07:43:14 [---] Resuming computation and network activity
2005-07-03 07:43:14 [---] Insufficient work; requesting more
2005-07-03 08:43:15 [---] Insufficient work; requesting more
2005-07-03 09:43:15 [---] Insufficient work; requesting more


I restart the process from time to time just to see if it'll work, but same story. My two Windows machines have been happily crunching the same time the Linux computer has been attempting to request work.

Anyone have any ideas? Does the Linux BOINC client retrieve work from a different server? I had assumed that since the Windows computers were working correctly that the problem lies in the Linux BOINC client.

---

I found the problem:

Looks like the "run_client" script is borked.

If you run ./boinc -attach_project ..... it works (grabs data)
If you run ./run_client -attach_project ..... it fails


It seems the "run_client" script is only useful for running *AFTER* you have run "boinc" the first time to attach to a project.

---

This might not be the cause but i had the same problem on all my machines it was because there literally wasnt any work being sent out for two days and when it came back up the wu's were being created to slow to be served, at one point it didnt move from 13 ready to send for a day.

---

I'm having a similar problem except there are two more lines of output that indicate my client will attempt to get data in 23 hours.

Can I get data sooner by changing a configuration parameter?
Are there SETI units available now?

---