Hello,

I’ve recently installed BOINC 5.4.9 on my Windows, Linux (FC4), and Mac(OSX PPC) PC’s. I’ve noticed that in all three versions, I’m having more work units sit longer at 100%. The communication interval for my projects is the default (0.1 days), and this has not changed since I updated a few days ago.

On version 5.2, I would run the option “Retry Communications”. This would send all complete work units for all projects. When I would watch in the “Messages” tab, I could see it going through each project. However, now on 5.4, “Retry Communications” doesn’t seem to actually do anything. Nothing appears in the “Messages” tab, and the complete work units are not sent. I have to go to the first tab and click “Update” for each project to send the work units for that project. If I just leave them, the work units will eventually go, but I can accumulate 2-4 units for different projects before they go.

I do not have a proxy server. I have a hardware firewall, but this does not seem to interfere with normal operation. No other updates were done around the same time. The problem occurs on all three platforms, and seems to affect all seven projects.

Is this a known bug? (I haven’t seen anything on the BOINC site.) Are other people seeing this, or do my work units just like me and don’t want to leave?

Thank you.

That is what BOINC is programmed to do, just leave them there are they will go when BOINC is ready to get rid of them, it will part upload them and then later on finish off uploading them to the project.



Its something like the 1st upload creates a database tablefor the WU's and then the 2nd upload puts them into the database table

I installed 5.4.9 and I don't have anymore Seti WU's anymore. What happened?

Is there something I need to reset?

Thanks.

gary

Please describe in more words what happens. What are the messages in the BOINC Manager you get when requesting new work from SETI? But as described by you i think this is an app-info.xml problem. Go to the setiathome project directory and delete the app.info.xml.