From what I've noticed, 6.12.x will not request new work when you have some (or just one?) downloads in Retry state (and NOT just uploads).

And previous versions of BOINC did the same, for as far back as I can remember.

Indeed. I have a similar issue, though it's not an issue for me because I seem to get a boat load of work when I need it. BOINC generally will not let you get new work unless you are crunching or reporting the very last task, at least for SETI@home and BETA. I don't know why, but even if you have your cache for 7+ days, BOINC will only download work when it absolutely needs it (aka downloading work when you are reporting/crunching/etc your very last task). It is annoying, but if you have a faster PC like me, (quad core processor), then you can easily get enough tasks for 7 days or more. I had, on my last download of tasks, I think close to 190 tasks. I will not get more work until they are all finished or very close to it.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

Hmm, I got 13 tasks 1 1/2 hours ago.

---

[/i][/b]

Antagonising the people who are trying to help you by being rude is not in general considered an approach that leads to people going out of their way to help you.

We can only help you further with your problem, if we have access to the data we have suggested you need to provide. (i.e. stdoutdae.txt output with work_fetch_debug set in cc_config). It would also help to know which of your 13 machines is/are experiencing this problem.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

First of all - I hope I'm not the one being rude here. That is not my intention.

Second, since my last post, it seems like the r2-d2 machine contact status has been updated. But due to the status yesterday, I have now disabled new tasks until I know that all current tasks has been reported successfully.

Third, the initial title of this thread "Can't report or get new tasks" is currently a bit misleading. The situation the last few months has been that it seems like this machine will not report tasks as completed, causing them to time out even if they has been completed and even uploaded.

The r2-d2 machine is the only one that has had this kind of problem. All my other machines has worked without any kind of problem (except problems caused when the project has been down for some time).

If the problem occurs again, perhaps it's better to start a new thread?

---

First of all - I hope I'm not the one being rude here. That is not my intention.

I think Miep is specifically responding to gcpeters

in response to Message 1114755.

The r2-d2 machine is the only one that has had this kind of problem. All my other machines has worked without any kind of problem (except problems caused when the project has been down for some time).

If the problem does recur, please give us the S&H ID number of the offending machine, or a link to it's details page. "The r2-d2 machine" doesn't tell us which one of your 8 active machines is the culprit.

Edit: There is a place on each computer's Details page labeled "Domain Name" where you can give that computer a name, such as "r2-d2". My two boxes are marked "dons-g4" and "dons laptop".

---

Donald
Infernal Optimist / Submariner, retired

Edit: There is a place on each computer's Details page labeled "Domain Name" where you can give that computer a name, such as "r2-d2". My two boxes are marked "dons-g4" and "dons laptop".

But only the logged-in owner of the machines can see those names - and you can't "give" them a name here, the website merely reports the (necessarily unique) name the computers already have on your network.

In any event, other people can't see the names - they're useless for describing a problem to other people on this board. Use the HostID number instead.

Edit: There is a place on each computer's Details page labeled "Domain Name" where you can give that computer a name, such as "r2-d2". My two boxes are marked "dons-g4" and "dons laptop".

But only the logged-in owner of the machines can see those names - and you can't "give" them a name here, the website merely reports the (necessarily unique) name the computers already have on your network.

In any event, other people can't see the names - they're useless for describing a problem to other people on this board. Use the HostID number instead.

Thank you, Richard, I did not realize that.
Learn somethin' new every day around here.

---

Donald
Infernal Optimist / Submariner, retired

14.6.2011 г. 18:54:43 ч. | SETI@home | [work_fetch] request: CPU (0.00 sec, 0.00 inst) NVIDIA GPU (0.00 sec, 0.00 inst)
14.6.2011 г. 18:54:43 ч. | SETI@home | Sending scheduler request: Requested by user.
14.6.2011 г. 18:54:43 ч. | SETI@home | Reporting 68 completed tasks, not requesting new tasks
14.6.2011 г. 18:54:54 ч. | SETI@home | Scheduler request completed
14.6.2011 г. 18:54:54 ч. | | [work_fetch] Request work fetch: RPC complete
14.6.2011 г. 18:54:59 ч. | | [work_fetch]: work fetch start
14.6.2011 г. 18:54:59 ч. | | [work_fetch] ------- start work fetch state -------
14.6.2011 г. 18:54:59 ч. | | [work_fetch] target work buffer: 0.86 + 864000.00 sec
14.6.2011 г. 18:54:59 ч. | | [work_fetch] CPU: shortfall 3175725.35 nidle 0.00 saturated 66802.32 busy 0.00 RS fetchable 0.00 runnable 100.00
14.6.2011 г. 18:54:59 ч. | SETI@home | [work_fetch] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
14.6.2011 г. 18:54:59 ч. | | [work_fetch] NVIDIA GPU: shortfall 1697013.08 nidle 0.00 saturated 14405.90 busy 0.00 RS fetchable 0.00 runnable 100.00
14.6.2011 г. 18:54:59 ч. | SETI@home | [work_fetch] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
14.6.2011 г. 18:54:59 ч. | SETI@home | [work_fetch] overall LTD -39755.19
14.6.2011 г. 18:54:59 ч. | | [work_fetch] ------- end work fetch state -------
14.6.2011 г. 18:54:59 ч. | | [work_fetch] No project chosen for work fetch
14.6.2011 г. 18:55:16 ч. | SETI@home | Started download of 15ap11ab.27804.6611.12.10.183
14.6.2011 г. 18:55:19 ч. | | [work_fetch] Request work fetch: project updated by user
14.6.2011 г. 18:55:29 ч. | | [work_fetch] Request work fetch: RPC complete
14.6.2011 г. 18:55:34 ч. | | [work_fetch]: work fetch start
14.6.2011 г. 18:55:34 ч. | | [work_fetch] ------- start work fetch state -------
14.6.2011 г. 18:55:34 ч. | | [work_fetch] target work buffer: 0.86 + 864000.00 sec
14.6.2011 г. 18:55:34 ч. | | [work_fetch] CPU: shortfall 3175876.01 nidle 0.00 saturated 66704.30 busy 0.00 RS fetchable 0.00 runnable 100.00
14.6.2011 г. 18:55:34 ч. | SETI@home | [work_fetch] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
14.6.2011 г. 18:55:34 ч. | | [work_fetch] NVIDIA GPU: shortfall 1696115.48 nidle 0.00 saturated 15356.82 busy 0.00 RS fetchable 0.00 runnable 200.00
14.6.2011 г. 18:55:34 ч. | SETI@home | [work_fetch] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
14.6.2011 г. 18:55:34 ч. | SETI@home | [work_fetch] overall LTD -39726.47
14.6.2011 г. 18:55:34 ч. | | [work_fetch] ------- end work fetch state -------


and no work unit :(

---

[size=9]14.6.2011 г. 18:54:59 ч. | | [work_fetch] ------- start work fetch state -------
14.6.2011 г. 18:54:59 ч. | | [work_fetch] target work buffer: 0.86 + 864000.00 sec
14.6.2011 г. 18:54:59 ч. | | [work_fetch] CPU: shortfall 3175725.35 nidle 0.00 saturated 66802.32 busy 0.00 RS fetchable 0.00 runnable 100.00
14.6.2011 г. 18:54:59 ч. | SETI@home | [work_fetch] CPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
14.6.2011 г. 18:54:59 ч. | | [work_fetch] NVIDIA GPU: shortfall 1697013.08 nidle 0.00 saturated 14405.90 busy 0.00 RS fetchable 0.00 runnable 100.00
14.6.2011 г. 18:54:59 ч. | SETI@home | [work_fetch] NVIDIA GPU: fetch share 0.00 LTD 0.00 backoff dt 0.00 int 0.00 (comm deferred)
14.6.2011 г. 18:54:59 ч. | SETI@home | [work_fetch] overall LTD -39755.19
14.6.2011 г. 18:54:59 ч. | | [work_fetch] ------- end work fetch state -------
[/size=9]

Seti is running on a 5 minute timeout - if you hit the update button before the 5 minutes are over, the server just tells you 'go away you just asked'. Leave at least 5 minutes between hitting the update button - boinc is going to ask after 5 minutes anyway and will gradually increase the time between attempts when it doesn't get through.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

Edit: There is a place on each computer's Details page labeled "Domain Name" where you can give that computer a name, such as "r2-d2". My two boxes are marked "dons-g4" and "dons laptop".

But only the logged-in owner of the machines can see those names - and you can't "give" them a name here, the website merely reports the (necessarily unique) name the computers already have on your network.

In any event, other people can't see the names - they're useless for describing a problem to other people on this board. Use the HostID number instead.

Thank you, Richard, I did not realize that.
Learn somethin' new every day around here.

Ahh.. silly me. I thought everybody could see the names. Is this http://setiathome.berkeley.edu/show_host_detail.php?hostid=5256434 better?

Still getting a few 500 Internal server error messages in return from the server @berceley.edu.

---

Ahh.. silly me. I thought everybody could see the names. Is this http://setiathome.berkeley.edu/show_host_detail.php?hostid=5256434 better?

Still getting a few 500 Internal server error messages in return from the server @berceley.edu.

Servers are not having a good evening. Cricket Graphs are mostly in the noise since about 17:00 local.

Matt can do some remote monitoring and control, but the fix may have to wait for morning.

---

Donald
Infernal Optimist / Submariner, retired

Still the same problem - the computer (id 5256434) will not report any tasks. According to http://setiathome.berkeley.edu/hosts_user.php?userid=7992989 this machine last reported June 14th while the other machines have reported completed works since then.

The other machine (id 5306094) is very similar and seem to work OK. Since I'm not able to find any solution to this, I'm about to give up this machine.... :(

---

I did have an issue with some of my pc's a couple of months ago where the app_info.xml caused the internal server error 500.
The reason was that those pc's were asking for obsolete work versions such as Enhanced 5.28 and Astropulse 5.0.

---

Seti@Netherlands website

Still the same problem - the computer (id 5256434) will not report any tasks. According to http://setiathome.berkeley.edu/hosts_user.php?userid=7992989 this machine last reported June 14th while the other machines have reported completed works since then.

The other machine (id 5306094) is very similar and seem to work OK. Since I'm not able to find any solution to this, I'm about to give up this machine.... :(

Somebody in another thread found that using a proxy was a workaround for a similar situation. You might try something like Privoxy (with the filtering disabled).

                                                                 Joe

Still the same problem - the computer (id 5256434) will not report any tasks. According to http://setiathome.berkeley.edu/hosts_user.php?userid=7992989 this machine last reported June 14th while the other machines have reported completed works since then.

The other machine (id 5306094) is very similar and seem to work OK. Since I'm not able to find any solution to this, I'm about to give up this machine.... :(

Somebody in another thread found that using a proxy was a workaround for a similar situation. You might try something like Privoxy (with the filtering disabled).

                                                                 Joe

That was i ;-)
greetz

---

I did have an issue with some of my pc's a couple of months ago where the app_info.xml caused the internal server error 500.
The reason was that those pc's were asking for obsolete work versions such as Enhanced 5.28 and Astropulse 5.0.

There is no app_info.xml file in the BOINC directory at this machine (or the other machines).

---

Still the same problem - the computer (id 5256434) will not report any tasks. According to http://setiathome.berkeley.edu/hosts_user.php?userid=7992989 this machine last reported June 14th while the other machines have reported completed works since then.

The other machine (id 5306094) is very similar and seem to work OK. Since I'm not able to find any solution to this, I'm about to give up this machine.... :(

Somebody in another thread found that using a proxy was a workaround for a similar situation. You might try something like Privoxy (with the filtering disabled).

                                                                 Joe

I cannot understand why this should cure it. The other machines, which use the same ADSL line and hide behind the same IP-address seem to have no problem with reporting completed WUs.

---

I know this machine runs Linux, have you tried a reboot? Works many times for Windows machines.

A project reset is also an option but you would lose the work already on board and completed. Berkeley should resend the work after the reset but you would have to crunch it again. Last but best option in my view. After 6 days of non communication you have to do something!

---

Boinc....Boinc....Boinc....Boinc....

try rebooting your router. I have the same issue with my I7. For some reason every once in a while it wont connect to anything on the internet. My Mac and P4 do. If i cant connect after I reboot the I7. I power it down and then turn off the power to the router and wait a minute or two. When I power back up every thing works.

I know its wierd but it works.

---

[/quote]

Old James

Did you try to move the LAN cable to another LAN port on the DSL router and restart the router?
Or use the cable from the working machine to connect the non-working to the router?

I had problems in the past with:
1) (~ 3 years ago) Semi-working LAN card in the computer after lightning fall nearby
2) (~ 1 year ago) Semi-working LAN cable (bad contacting at the plug)

In both cases I had Internet connection but slow and with errors causing many auto-retries and timeouts/drops in the connection.

If something don't work at all it's easy to diagnose and find the problem.
If it's working but very bad you can wonder for long time where in the chain is the problem.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)