Manually uploading client_state.xml to s@h |
![]() |
| log in |
Message boards : Number crunching : Manually uploading client_state.xml to s@h
1 · 2 · 3 · Next
| Author | Message |
|---|---|
|
When the s@h client has troubles getting through to s@h when trying to upload the file to report completed workunits, is there an manual option that you could do to make it work? | |
| ID: 1033608 · | |
When the s@h client has troubles getting through to s@h when trying to upload the file to report completed workunits, is there an manual option that you could do to make it work? Good question to ask...... I was thinking exactly the same thing yesterday when I was getting nothing but HTTP internal server errors every time my rigs tried to report their stored up completed work. Thankfully, things settled down a bit and they finally all made it through. Don't know the size of the file, but I think the largest had about 3000 WUs to report. Yours must have a lot more than that. I too, was wondering if there was a way to get Boinc to report only X number of completed WUs at a time, or be able to split the file up into smaller subfiles to transfer successfully. I think the Boinc devs should consider adding an option..... <report_max_results>XXXXX</report_max_results> ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1033609 · | |
Yea i wrote that long ago that it should be split and that it would be incorporated in the Boinc structure itself not only to s@h. Small batches would be better for the overall amount of TCP packets needed for resend etc. For now that machine has about 4800 Wu's to report and it's increasing fast :-/ Hope there is a way otherwise i need to babysit and watch the graphs so the network isn't congested to it's max and wait it out and hope :) Kind regards Vyper ____________ _________________________________________________________________________ Addicted to SETI crunching! Founder of GPU Users Group | |
| ID: 1033614 · | |
|
It isn't client_state.xml that you're trying to upload. It's sched_request_*.xml, so you have to check the size of this file. | |
| ID: 1033694 · | |
|
Vyper.... | |
| ID: 1034005 · | |
|
Gonna try now! As i write this. | |
| ID: 1034069 · | |
Gonna try now! As i wite this. Yikes......how much are you trying to report now?? ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1034072 · | |
|
Boinc has behaved badly so the machine was set in an unresponsive state tonight so it hasn't been up until my colleague rebooted it at the office this afternoon (4 hours ago).. | |
| ID: 1034090 · | |
|
Ok | |
| ID: 1034113 · | |
Ok The kitties say meowa meowa kazzzam. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1034119 · | |
|
Somebody must be getting through, my total and RAC are climbing slowly and my pendings are dropping. Good luck Vyper. | |
| ID: 1034123 · | |
|
Ok the first try didn't work. | |
| ID: 1034127 · | |
|
/me crosses everything crossable. :D | |
| ID: 1034128 · | |
Ok the first try didn't work. Kibble go high, kibble go low. From the cruncher to the server, here we go.............. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1034135 · | |
/me crosses everything crossable. :D Thanks Jord..... As computers and GPUs get faster and can process more and more work, this may become even more of an issue. At least at Seti. I don't run other projects, so I am not sure how the size of their WUs compare. But Boinc may need to adjust so that situations like Vyper's can be handled more gracefully by the core client. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1034139 · | |
|
Vyper, David asks if you can email him your sched_request*.xml file. (I'll ask you to zip or otherwise compress it first. :-)) | |
| ID: 1034143 · | |
|
Update. David Anderson wrote: I see what the problem is (it's in the server; it crashes when lots of results are reported). I'll try to get it fixed today. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 1034146 · | |
|
Great, that should be a load off the minds of our super-crunchers out there. | |
| ID: 1034150 · | |
Great, that should be a load off the minds of our super-crunchers out there. Well, it sure doesn't bother us "peons" anyhow :-) ____________ /The grumpy old Swede. "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1034152 · | |
Update. Thanks! In past I lost a few times a lot of results/Cr., because I needed to detach/attach that my GPU machine got again well contact to the server.. Currently 'top_host'_#4 owner.. ;-) ____________ >Das Deutsche Cafe. The German Cafe.< | |
| ID: 1034154 · | |
Message boards : Number crunching : Manually uploading client_state.xml to s@h
| Copyright © 2013 University of California |