Can anyone tell me why my finished wu's are generating this error when it tries to upload finished work?

---

Can anyone tell me why my finished wu's are generating this error when it tries to upload finished work?

Because the servers of the project are down for the third time in the last month.

Just take a look at the home page of the project...

Ralf

Been uploading work for almost an hour now, have even gotten new work units for a few of my systems. My thanks to those who gave up a part of their weekend to make this possible.

Over here, I've found that unit reporting has started (even finished for me), however unit upload is still met immediately by "File Upload handler is missing". hmmph. Hopefully that's just a sign of overload, and will wear off as things progress. Hopefully. But to this point, I haven't even had one upload sneak thru, of about 50 that are retrying.

Dave

Over here, I've found that unit reporting has started (even finished for me), however unit upload is still met immediately by "File Upload handler is missing". hmmph. Hopefully that's just a sign of overload, and will wear off as things progress. Hopefully. But to this point, I haven't even had one upload sneak thru, of about 50 that are retrying.

Dave

I got now 11 WU showing up under "Credit pending", but that's roughly a quarter of finished jobs.

And a couple of new jobs actually got downloaded and are running as sharing of my "backup project" allows...

Ralf

Well, still 100% failure on upload attempts. If I recall, boinc does not attempt any work request while uploads are pending, thus most of my machines are now stuck with no r@h work until this thing gets fixed......

ah well

Dave

I've only got 6 wu on our network attempting to upload, and these all all indicating Project File Handler is missing.
However, this morning I got 2 wu downloaded from R@h, awaitng to see what happens when they complete.
If I get Project File Handler is missing with these, then I'm suspending R@h until the matter is sorted out.

Charlie

Ok the first of the new wu's which arrived this morning has just finished.

On attempt to upload and gave the same message Project File Upload Handler Is missing.

So as I stated in my previous thread,I've suspended R@h until things are sorted.

Work now being diverted to other projects.

Charlie

Well the following messages are a new twist in this problem.


Sun Jan 9 08:41:17 2011 rosetta@home update requested by user
Sun Jan 9 08:41:17 2011 rosetta@home Sending scheduler request: Requested by user.
Sun Jan 9 08:41:17 2011 rosetta@home Reporting 2 completed tasks, requesting new tasks
Sun Jan 9 08:41:18 2011 rosetta@home Scheduler request completed: got 0 new tasks
Sun Jan 9 08:41:18 2011 rosetta@home Message from server: platform 'x86_64-apple-darwin' not found


And like the rest of you my upload queue is full of completed work.

Regards

---

We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.

Well the following messages are a new twist in this problem.


Sun Jan 9 08:41:17 2011 rosetta@home update requested by user
Sun Jan 9 08:41:17 2011 rosetta@home Sending scheduler request: Requested by user.
Sun Jan 9 08:41:17 2011 rosetta@home Reporting 2 completed tasks, requesting new tasks
Sun Jan 9 08:41:18 2011 rosetta@home Scheduler request completed: got 0 new tasks
Sun Jan 9 08:41:18 2011 rosetta@home Message from server: platform 'x86_64-apple-darwin' not found


And like the rest of you my upload queue is full of completed work.

Regards

---

We Must look for intelligent life on other planets as,
it is becoming increasingly apparent we will not find any on our own.

I'm sitting here with well over a hundred results files that won't upload. :( I've had a few that have uploaded, but many more that won't.

[rant]
You know, I left the Seti project and attached to this one because of server based problems. Now it's looking to me like the same shoestring mentality is ruling this project too, as concerns the servers and database. I don't know much about setting up the hardware to run a project such as this, but I would think that primary consideration would be given to make a robust data handling system with redundancies and it looks to me like academia in general doesn't seem to think (to me at least) that making sure your infrastructure is robust enough to take into account the possibility of equipment failure bringing an entire project to a screeching halt. Spend more money on your project infrastructure before you go on dreaming new methods to crunch numbers or whatever, you all. I have seen this with this project, Seti and also the Folding@Home project run by Stanford, although theirs seems to be more a problem with dreaming up new clients and never getting the bugs worked out of their older DC clients.

I hope that you all can get this back up and running soon. Otherwise, I guess I will move on to someone else's project, since it ticks me off to have something I am donating my time to by running their project (and paying the electricity for to run their project on my computers) not take some precautions to keep their project going by providing redundancy in their project's infrastructure to handle hardware failure.
[/rant]

I've detatched the project from our network until the administrators can be bothered to update us regarding the issues posted here.

I'm not wasting my network time or my power consumption, on work units that may or may not eventually upload.

I've sacrificed 6 wu's, and diverted my capacity to the other projects I'm running.

Charlie

Strange attitudes to have when "donating" your time (by donating time I mean letting your computer stay on). A catastrophic failure is no fun. It takes a lot of work, time, and stress. I believe there are only one or two guys that maintain the servers. I think their time is better served by writing a line or two, as they did, as to the status rather than write an essay on causes and effects and have everyone second guess their methods, actions, and infrastructure on the forums - which is exactly what would happen.

If you can't upload, just keep crunching until you can, what's wrong with that?

---

I humbly ask members not to detach from R@H - but to set BOINC to not get new tasks from R@H until the present file-upload problem got resolved.

In the meantime, maybe members can consider helping out other projects.

I have got machines crunching CPU WUs for R@H & SETI and GPU WUs for SETI, Collatz, DNetC and Milky. When 1 project got problems, the spare resources automatically go to WUs of another project. I can further control resource share ratio in my project account page.

The recent problems faced by the project are regrettable. Despite all good intention/maintenance by sys-admins, sometime hardware failure happens. Redundancies are good - however when you don't have it, you can't spare *that* $20.

We are donating our resources/support to R@H as we believe in the project's cause – agree?

--
terence

edit: R@H is still the least problematic project IMHO.

Now it's looking to me like the same shoestring mentality is ruling this project too, as concerns the servers and database.

If it bothers you that much, you could always try this.

---

It's frustrating when the project is down but having full redundancy probably isn't the best use of the Bakerlab's funds, especially given that (my understanding is that) a fibre SAN costs many thousands of pounds, and given that there's a new one currently on order.

It would be nice if the project had 100% uptime, but I've been running it for a few years and there's only been downtime of over a day a few times, and maybe only three times that I've run out of work in that period - stick a backup project in at 0% and it'll only run on the occasions when Rosie is down.

On a similar topic, I think it would be useful if the forum were hosted elsewhere from the other equipment, but I don't have any idea if that's practical.

I'm sitting here with well over a hundred results files that won't upload. :( I've had a few that have uploaded, but many more that won't.

[rant]
You know, I left the Seti project and attached to this one because of server based problems. Now it's looking to me like the same shoestring mentality is ruling this project too, as concerns the servers and database. I don't know much about setting up the hardware to run a project such as this, but I would think that primary consideration would be given to make a robust data handling system with redundancies and it looks to me like academia in general doesn't seem to think (to me at least) that making sure your infrastructure is robust enough to take into account the possibility of equipment failure bringing an entire project to a screeching halt. Spend more money on your project infrastructure before you go on dreaming new methods to crunch numbers or whatever, you all. I have seen this with this project, Seti and also the Folding@Home project run by Stanford, although theirs seems to be more a problem with dreaming up new clients and never getting the bugs worked out of their older DC clients.

I hope that you all can get this back up and running soon. Otherwise, I guess I will move on to someone else's project, since it ticks me off to have something I am donating my time to by running their project (and paying the electricity for to run their project on my computers) not take some precautions to keep their project going by providing redundancy in their project's infrastructure to handle hardware failure.
[/rant]

---

DCDC said ...

I think it would be useful if the forum were hosted elsewhere from the other equipment, but I don't have any idea if that's practical.

Amen brother. And if hosting the forum somewhere else is not feasible, then at least utilize the Rosetta Facebook page to communicate status with the community when your server is down.

[rant]
You know, I left the Seti project and attached to this one because of server based problems. Now it's looking to me like the same shoestring mentality is ruling this project too, as concerns the servers and database. I don't know much about setting up the hardware to run a project such as this, but I would think that primary consideration would be given to make a robust data handling system with redundancies and it looks to me like academia in general doesn't seem to think (to me at least) that making sure your infrastructure is robust enough to take into account the possibility of equipment failure bringing an entire project to a screeching halt. Spend more money on your project infrastructure before you go on dreaming new methods to crunch numbers or whatever, you all. I have seen this with this project, Seti and also the Folding@Home project run by Stanford, although theirs seems to be more a problem with dreaming up new clients and never getting the bugs worked out of their older DC clients.

I hope that you all can get this back up and running soon. Otherwise, I guess I will move on to someone else's project, since it ticks me off to have something I am donating my time to by running their project (and paying the electricity for to run their project on my computers) not take some precautions to keep their project going by providing redundancy in their project's infrastructure to handle hardware failure.
[/rant]

muddocktor calls this a rant. but it looks a lot more like an objective and cogent analysis of the problems that ensue when arrogance finds its way into project management.

Strange attitudes to have when "donating" your time (by donating time I mean letting your computer stay on). A catastrophic failure is no fun. It takes a lot of work, time, and stress. I believe there are only one or two guys that maintain the servers. I think their time is better served by writing a line or two, as they did, as to the status rather than write an essay on causes and effects and have everyone second guess their methods, actions, and infrastructure on the forums - which is exactly what would happen.

If you can't upload, just keep crunching until you can, what's wrong with that?

Riiight. Just keep wasting energy for an indeterminate period waiting for some sort of communication from somebody.

The traffic light at the intersection has suffered a catastrophic failure. It is stuck on "red." We should just sit at the intersection with our vehicle engines running until somebody decides to make repairs (or we run out of fuel).

...I think it would be useful if the forum were hosted elsewhere from the other equipment, but I don't have any idea if that's practical.

Sure it would be practical. Why wouldn't it. Web sites are remotely hosted all the time.

Anybody can suffer a catastrophic failure of equipment. What is difficult to understand is the paucity and vagueness of communication from the Project's managers.

deesy

Sure it would be practical. Why wouldn't it. Web sites are remotely hosted all the time.

Maybe because it's part of the BOINC server suite and puts things like the user's RAC on their posts? I don't know how closely the two are tied together...

---

Sure it would be practical. Why wouldn't it. Web sites are remotely hosted all the time.

Maybe because it's part of the BOINC server suite and puts things like the user's RAC on their posts? I don't know how closely the two are tied together...

The forum is the forum. Stats are some else entirely. It is common practice in IT-world to have your feedback about an application on a physically different machine (so not another virtual machine hosted on the same physical server..), at least in the companies I worked for (IBM, AT&T)

---