I think it's bad that the project has been down for almost a week, I have 22 completed units to upload but what is most annoying is that there hasn't been any update of the technical news page since Friday (15/7). I realize the servers have to be updated and that unexpected things happen but why not let us know what's going on? It makes waiting for things to start working so much easier.

---

We know it has a problem, we are working on it, it will be fixed sOON............;0)

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

What amuses me is the initial glib responses to peoples concerns. "This always happens etc...", "Oh not another poster complaining, don't you know this always happens etc...", "Yet another poster complaining, haven't you read all the other posts on this etc...".

Now it turns out that there was a real problem after all. Perhaps it would have been resolved sooner if it had been taken more seriously sooner?

---

We know it has a problem, we are working on it, it will be fixed sOON............;0)

Now you're part of the core team Head Troll? LOL

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=2263&amp;prj=1&amp;trans=off"><img src="http://seti.mundayweb.com/stats.php?userID=937&amp;trans=off">

Now it turns out that there was a real problem after all. Perhaps it would have been resolved sooner if it had been taken more seriously sooner?

I doubt it, as it's not the forum users that are the ones with the power to fix anything.

What amuses me is the initial glib responses to peoples concerns. "This always happens etc...", "Oh not another poster complaining, don't you know this always happens etc...", "Yet another poster complaining, haven't you read all the other posts on this etc...".

Now it turns out that there was a real problem after all. Perhaps it would have been resolved sooner if it had been taken more seriously sooner?

Since the problem happens for about 3* the length of any outage, paying attention to it too early is counter productive. When the problem went to about 5 or 6 * the length of the outage was when the developers started to notice that it was a real problem and not business as usual after an outage. The crunch dealing with the backlog of uploads was completely expected, and experience has indicated that it takes X amount of time for Y amount of time with the servers off. When X was exceeded, it was time to look to see if there was something else going, looking earlier would normally have been a complete waste of time that the developers could have been using to enhance the rest of the system.

If you cry wolf too many times, you will be ignored. This is precisely what happened - the users were crying wolf that the uploads were not going through even though this happens every time and patience has sorted it out in the past with no intervention.

---

BOINC WIKI

We know it has a problem, we are working on it, it will be fixed sOON............;0)

Now you're part of the core team Head Troll? LOL

Apple core maybe ;0)

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Now it turns out that there was a real problem after all. Perhaps it would have been resolved sooner if it had been taken more seriously sooner?

I had comunicated very early after the outage with Jeff Cobb about the upload problems and there was not to see anything different to previous overload situations. So the response in the boards - that it was only a normal overload - was correct at this moment and had no relation to the question if the problem was taken seriously in the lab or not. Still all problems will be taken seriously.

The upload problem was monitored over the time, and as it didn't sorted out itself and there was not found a quick solution, as a work around, hardware was added.

I am sure all would like to solve problems before they occur, or see quick fixes, but this is not always possible. Sorry for that.

---

Greetings from Bremen/Germany
Jens Seidler (TheBigJens)

Now it turns out that there was a real problem after all. Perhaps it would have been resolved sooner if it had been taken more seriously sooner?

I had comunicated very early after the outage with Jeff Cobb about the upload problems and there was not to see anything different to previous overload situations. So the response in the boards - that it was only a normal overload - was correct at this moment and had no relation to the question if the problem was taken seriously in the lab or not. Still all problems will be taken seriously.

The upload problem was monitored over the time, and as it didn't sorted out itself and there was not found a quick solution, as a work around, hardware was added.

I am sure all would like to solve problems before they occur, or see quick fixes, but this is not always possible. Sorry for that.

I beg to differ. I reported over a week ago that the scheduler server was getting "Internal Server Errors". That is not an overload situation. As far as I know, they have not yet been addressed.

---

I beg to differ. I reported over a week ago that the scheduler server was getting "Internal Server Errors". That is not an overload situation. As far as I know, they have not yet been addressed.

Yes, I know. But the 500 error is a typical part of a overload situation, together with other. A type of general fault. And the scheduler is a different issue as the data server. I can't say that there are not the same roots in both cases, but have no hint at the moment.

---

Greetings from Bremen/Germany
Jens Seidler (TheBigJens)