Since about 5 o'clock this morning on one of my rigs I'm getting this message: "Communication resumed for 24:00 hours", then counting down. When pressing 'Update' I get "Fetching scheduler list"...and that's it. Master file won't download and nothing else is happening. Got many WUs ready for upload but due to that prob they're stuck.
What I've done already:
- trying another client (6.3.14, 6.3.10, 6.2.15) using the old data and account: no success
- trying stable client 6.2.15 on a fresh installation and new account: no success either...it even won't download the initialization files, just that "24:00 hours" message is apperarin...
- putting the whole BOINC-folder to another rig and trying to get the WUs through from here: same prob again...

Any idea what I could do to get that rig/account usable again ?

Since about 5 o'clock this morning on one of my rigs I'm getting this message: "Communication resumed for 24:00 hours", then counting down. When pressing 'Update' I get "Fetching scheduler list"...and that's it. Master file won't download and nothing else is happening. Got many WUs ready for upload but due to that prob they're stuck.
What I've done already:
- trying another client (6.3.14, 6.3.10, 6.2.15) using the old data and account: no success
- trying stable client 6.2.15 on a fresh installation and new account: no success either...it even won't download the initialization files, just that "24:00 hours" message is apperarin...
- putting the whole BOINC-folder to another rig and trying to get the WUs through from here: same prob again...

Any idea what I could do to get that rig/account usable again ?

I have the same problem on my computers since about 2 weeks.
Hitting the update button doesn`t really help, but then, all of the sudden,
when you don`t expect it, MilkyWay "finds" one of the comps again.....

Would be of great help, if anybody knew what`s going on !!

Kurt

---

I have run into this problem at other projects.....I just shut down boinc, waited a minute, and restarted it.....That usually fixes most Boinc problems....

The extreme measure would be to detach from the project and add it again....

I have run into this problem at other projects.....I just shut down boinc, waited a minute, and restarted it.....That usually fixes most Boinc problems....

The extreme measure would be to detach from the project and add it again....

Thank you for your answer !
I`ve tried both methods described above several times, but it doesn`t help.
On the other hand, one of my comps usually gets attached to MilkyWay and I
have work. I was just wondering if Boinc, my computers, or MilkyWay is
responsible.

All the best,

Kurt

---

Maybe an "ipconfig flushdns" command will help (under "Start" -> "Ausführen")?



EDIT: Sorry for my "Denglish" as we call English mixed with German, hehe...)

---

Lovely greetings, Cori

Hi Cori !

Good idea, I´ll give it a try tomorrow evening.
Right now even coffee won`t help me from falling asleep !

All the best,

Kurt

---