old thread "No Activity" seems the closest to my problem, but does not seem to be securing a response.

For several weeks now while apparently set up to spend 50% of time on Einstein and 50% of time on SETI, in practice all the time is spent on the former, and every time a piece of work is complete another piece from Einstein is provided and starts working. Have tried to UPDATE SETI but seems to have no effect apart from advice that request successfully received (unless which is quite probable I am misunderstanding the messages). Particularly irritating is receipt of recent email circular from SETI asking me to RECONNECT to SETI.

Only relevant background (I think) is that I had at least one occasion when unable to complete a particular SETI piece of work (within timescale) so sent an abort message (wrong procedure??).

Not too IT clever and would appreciate any advice.

Colin Jackson
____________

---

It looks like you were doing SETI several months ago, and then it stopped? Maybe early summer?

Look in your BOINC\\Projects\\SETI.... folder, do you have a file called app_info.xml? If so, STOP BOINC, delete this file, and restart BOINC.

If not, please stop BOINC, restart BOINC, then post the messages that come up for the first couple of minutes.

---

My movie https://vimeo.com/manage/videos/502242

It looks like you were doing SETI several months ago, and then it stopped? Maybe early summer?

Look in your BOINC\\Projects\\SETI.... folder, do you have a file called app_info.xml? If so, STOP BOINC, delete this file, and restart BOINC.

If not, please stop BOINC, restart BOINC, then post the messages that come up for the first couple of minutes.

Hi there, I have the same problem as above but not have the file named but seti will not upload or download. other project do? Any help

---

Hi there, I have the same problem as above but not have the file named but seti will not upload or download. other project do? Any help

Under Boinc the data is not sent back INSTANTLY the moment you complete the crunching. It is sent back in a bunch based on when you need more work. Your computer sent back work on the 25th. Click on your name and then view your computers and then click on the number to the far right. In your case, just now, it was 24, the number of units the database says it is tracking on your computers. Old units are purged to keep the database from getting too full. They are still kept but in a totally different database.

---

Hi there, I have the same problem as above but not have the file named but seti will not upload or download. other project do? Any help

You have gotten work over the last 24 hours.

If you are doing more than one project, you may have a debt problem, where it thinks you have done too much SETI, and the other project(s) need to get their time, before it allows SETI to do work, again.

---

My movie https://vimeo.com/manage/videos/502242

I've had the same problem. I'm running Seti and BBC Climate Change on two computers, both at 50%, so each project gets its fair share and until 3 or 4 days ago that was fine. BOINC would run one project for an hour, then switch to the other. That's still the case on one machine. On the other I haven't had any SETI tasks run for 3 or 4 days and even clicking Update doesn't fetch any work.
Jack

---

I've had the same problem. I'm running Seti and BBC Climate Change on two computers, both at 50%, so each project gets its fair share and until 3 or 4 days ago that was fine. BOINC would run one project for an hour, then switch to the other. That's still the case on one machine. On the other I haven't had any SETI tasks run for 3 or 4 days and even clicking Update doesn't fetch any work. Jack

This is called "Long Term Debt", it is spelled out i nthe Wiki. The Wiki is available on the home page of Boinc. But basically LTD, as it is acronymed, is the crunching of one project for much longer than another because somewhere along the line it thinks it got shorted. It will even out by itself and Seti will crunch for a bit with CPD laying back. Over the course of a year you will see the 50/50 you want. Over the course of a few days or even weeks, the numbers will be more like 60/40 or so.
Another problem with CPD is that some units are now taking upto a full year to crunch, of course the credits granted are huge when you finish it.

---

im having a problem connecting, it was fine yesterday on my first download but i cannot always be connected to the internet, and it downloaded then my father turned the router off and i left my boinc to crunch the data while i went to bed.

i uploaded the file today, and whenever i try to download, it starts then says "retry in x:xx minutes" why the heck?

Looks like you can add me to the list! Attached below is the message I've been getting all evening!

11/13/2006 10:41:02 PM|SETI@home|Started download of file 14jn03ab.20420.21138.336072.3.72
11/13/2006 10:41:04 PM|SETI@home|Incomplete read of less than 5KB for 14jn03ab.20420.21138.336072.3.72 - truncating
11/13/2006 10:41:04 PM|SETI@home|Temporarily failed download of 14jn03ab.20420.21138.336072.3.72: Error 403
11/13/2006 10:41:04 PM|SETI@home|Backing off 1 minutes and 8 seconds on download of file 14jn03ab.20420.21138.336072.3.72

---

@Salmon 1 and Gvaz:

The BOINC-SETI servers have been acting funny all evening, it isn't just your computers. Give it until tomorrow and it should be straightened out.

---

Yeah,

me here as well with a very similar named workunit.

SETI rarely have these problems, so my personal computer here is only running SETI for now, hope you straighten it out quickly guys, and thanks!

gady b
Jupiter Crash SETI team

---

me too am experiencing the same problems, no work being downloaded. hopefully i've set my preferences to allow mw some extra units in my machines. apparently all servers but one are running. anyone has any information for us?
keep crunching guys

---

Yup, same problem for me. No work being sent. I get this message:
Tue 14 Nov 2006 15:59:32 CET|SETI@home|Temporarily failed download of 13jn03aa.22301.5936.184644.3.67: Error 403
So if it's a server problem then I'll just let it go till the servers are back up.
J

Yup, same problem for me. No work being sent. I get this message:
Tue 14 Nov 2006 15:59:32 CET|SETI@home|Temporarily failed download of 13jn03aa.22301.5936.184644.3.67: Error 403
So if it's a server problem then I'll just let it go till the servers are back up. J

Yes, error code #403 means it is a server side error. When Berkeley fixes their end, it will work again.

---

12/5/2006 12:19:24 PM|SETI@home|Message from server: (reached daily quota of 2 results)
Why are there now quotas on work? Please Help...

---

12/5/2006 12:19:24 PM|SETI@home|Message from server: (reached daily quota of 2 results)
Why are there now quotas on work? Please Help...

Quick answer as I'm heading out the door. Daily quota is set to 100 and is reduced by 1 every time a result errors out to prevent a rogue computer draining the work queue. It double back up to a max of 100 with the return of a good results.

Your AMD 64 is trashing WU, with error 'Couldn't start or resume: -108'. It looks like that system is having problems.

I hope someone else can help you figure out why.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

12/5/2006 12:19:24 PM|SETI@home|Message from server: (reached daily quota of 2 results)
Why are there now quotas on work? Please Help...

Error code -108 means:
"ERR_FOPEN -108 system fopen The file is "open" and in use by another process, or write access to the file cannot be obtained."
And the quotas have been in place a long time. It is as stated..100 workunits per cpu, up to a max of 4 cpus per machine.
It will decrease by 1 for every bad unit you have, so 1 host doesn't hog all availble units if it is not crunching them properly. It then increases by 2 for every unit that host returns correctly. So it is slow to go down, but fast to recover.

---

12/5/2006 12:19:24 PM|SETI@home|Message from server: (reached daily quota of 2 results)
Why are there now quotas on work? Please Help...

Ricky1,

this error may appear if a previous instance of the Seti app couldn't shut down properly (e.g. stuck while writing to a file) and therefore keeps a file locked (file locking is handled by the OS; if the OS doesn't get a "signal" to unlock a file, it stays locked, even if the process that locked the file has been terminated).

This can simply cleared by a restart of the affected PC. Also make sure you have full access to the BOINC directory and it's subfolders. If this error still shows up after a reboot, please come back.

Regards
Andy