However, why is that a problem on Windows but seems not to be a problem for any Linux systems? (Well, mine at least that is, some with a mix of most recent to quite old versions of libcurl?)

Happy crunchin',
Martin

I think it's a question of signal to noise ratio, and our sample.

From the other thread, we know it happens on Windows.

We got some hazier reports dealing with the Mac.

... and I think only one mention of Linux.

So, based on the amount of input we received, I'm not sure we have enough information to say (statistically) that it is one OS, but not others.

Also, I could probably rag on how libcurl caches IP addresses. The entry has a reference count, a TTL, the name and the IP.

If the TTL runs out, and the reference count goes to zero, the cache entry is released, but under a "heavy load" (according to the notes) the reference count may not go to zero.

In other words, there are a lot of variables. I'm not sure we know all of them.

---

I think this ones a fake panic....
12/3/2009 1:19:18 PM SETI@home Message from server: (Project has no jobs available)
12/3/2009 1:20:34 PM SETI@home Sending scheduler request: To fetch work.
12/3/2009 1:20:34 PM SETI@home Requesting new tasks for GPU
12/3/2009 1:20:44 PM SETI@home Scheduler request completed: got 5 new tasks
12/3/2009 1:20:47 PM SETI@home Started download of 27mr07aa.22670.6616.3.10.158

---

Official Abuser of Boinc Buttons...
And no good credit hound!

It happened on my iMac and the Quad and in reverse on the Dell.

The iMac and Quad could not download anything until I edited the hosts file but the Dell had no problem at all.

---

Servers down.....

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Servers down.....

Yes, but it's taken care of:

04/12/2009 19:50:16|SETI@home|Message from server: Project is temporarily shut down for maintenance

No it's not still down here.

---

I think he means it's being taken care of.

---

PROUD MEMBER OF Team Starfire World BOINC

O.K. SORRY

Dave

---

Uh-oh!! The server status page is stuck at 09:40:11 :-(

F.

---

Yes, sure - it's weekend..


I hope we will not run out of new work.. or get other server outages/probs..

---

And the Seti@home server graphs have flatlined since then. Lets all worry Lmao

---

And the Seti@home server graphs have flatlined since then. Lets all worry Lmao

?
Work is still being downloaded, results are still being returned.
The only problem is with the status updates.

---

Grant
Darwin NT

And the Seti@home server graphs have flatlined since then. Lets all worry Lmao

?
Work is still being downloaded, results are still being returned.
The only problem is with the status updates.

Yes, everything is working as it should in the background. But it is weekend so I think we deserve a minor panic :-)

F.

---

Getting up this early on a Sunday Morning to kick the machines. Awesome and thanks.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

And the Seti@home server graphs have flatlined since then. Lets all worry Lmao

?
Work is still being downloaded, results are still being returned.
The only problem is with the status updates.

Yes, everything is working as it should in the background. But it is weekend so I think we deserve a minor panic :-)

F.

Looks like they agreed...

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Someone know how long the unplanned maintenance will last?

I have now 1,030 results ready for report on my GPU cruncher..
If + ~ 24 hours, it'll be not possible to report this big report file.
Although current also only with good luck (if possible).

So I need to detach/attach the project. And the project will lose ~ 104,000 credits/science.


Yes, everybody have his own 'probs'..

---

You could also suspend crunching, to stop accumulating new tasks to upload. Why crunching them now if you have to throw them away later?

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Someone know how long the unplanned maintenance will last?

I have now 1,030 results ready for report on my GPU cruncher..
If + ~ 24 hours, it'll be not possible to report this big report file.
Although current also only with good luck (if possible).

So I need to detach/attach the project. And the project will lose ~ 104,000 credits/science.


Yes, everybody have his own 'probs'..

I have 200 units to report on one machine. How many is too many?

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Shut down the computer until the servers come back again. Easy solution and you will not lose any credits that you're waiting to upload.

??

The results are ULed.

I can't report!

I have only a 3 day WU cache.. so after some short time he will idle..

I'm not afraid because of my credits.. it's the 'deleted' credits(performance)/science.

---

I have 200 units to report on one machine. How many is too many?

It depend how fast your UL is.

I could suspend my UL/DL now.
But then the report file will be send in the same time the UL of the results will happen.

So I guess it's better to send only the report file.

I have only DSL light (384/64), more isn't possible here where I live.

I had probs to report ~ 1,600 results. The report lasts ~ 20 minutes or something.
After many, many, many and much more scheduler server error messages.

---