Reached daily quota of 2 results

Questions and Answers : Unix/Linux : Reached daily quota of 2 results

Author	Message
Velez's Send message Joined: 30 Nov 02 Posts: 24 Credit: 1,545,060 RAC: 2,465	Message 233431 - Posted: 19 Jan 2006, 8:58:40 UTC
	Hello all, All of a sudden on my linux machine, my entire cache disappeared and I got a message from the server saying: Message from server: no work sent Message from server: (reached daily quota of 2 results) No work from project Deferring communication with project for 23 hours, 43 minutes, and 2 seconds I wake up this morning and I have two workunits running on my two CPUs and nothing in cache. It seems the server thinks I am only allowed to do two workunits a day. I did notice the boinc client had terminated all of a sudden. When I restarted, this started to occur. Should I reinstall the boinc client? And why did this happen all of a sudden? JV ____________
	ID: 233431 ·

Velez's Send message Joined: 30 Nov 02 Posts: 24 Credit: 1,545,060 RAC: 2,465	Message 233441 - Posted: 19 Jan 2006, 10:28:27 UTC Last modified: 19 Jan 2006, 10:34:17 UTC
	OK. Problem solved. For people who end up in this thread looking for explanations: I had an unexpected termination of the boinc client which subsequently caused unfinished workunits to be reported. This caused the server in Berkeley to reduce my quota to 2 a day. From that point on, every time I finished a work unit and reported good results with no communication/upload errors, the Berkeley SETI server doubled my quota. Fairly soon, I should be back to a normal quota again. I only ended up losing a few hours of work, due to an abnormal occurrence. Patience was the key. [edit] The strange thing is that the client seems to have terminated when the power supply shifted to my UPS since we had a power outage. The linux machine did not lose power since it wasn't shut down. I noticed it once before that the shift to UPS killed my boinc client. Is that just coincidence? [end edit] JV ____________
	ID: 233441 ·

Doris and Jens Volunteer developer Volunteer tester Send message Joined: 21 Nov 99 Posts: 362 Credit: 976,542 RAC: 339	Message 233446 - Posted: 19 Jan 2006, 10:53:20 UTC - in response to Message 233441. Last modified: 19 Jan 2006, 13:07:18 UTC
	[edit] The strange thing is that the client seems to have terminated when the power supply shifted to my UPS since we had a power outage. The linux machine did not lose power since it wasn't shut down. I noticed it once before that the shift to UPS killed my boinc client. Is that just coincidence? [end edit] It should not happen that the client crashed when the host switch to UPS, but it is not a very public issue, so there may be a unknown problem. Would be nice if you find out more about the problem and can give some more information (OS, UPS software, client release, error messages ...) The BOINC client normally should stop the computing done by the SETI@home client when the host goes on battery. This is a function for Laptops, where computing a WU will drop down the runtime a lot. There is a option in the preferences to set it on or off, default is on. But it should not crash in this case. Is it possible that your UPS configuration try to shut down all applications and kill the BOINC and SETI@home clients, breaking the computation? ____________ Greetings from Bremen/Germany Jens Seidler (TheBigJens)
	ID: 233446 ·

Velez's Send message Joined: 30 Nov 02 Posts: 24 Credit: 1,545,060 RAC: 2,465	Message 233455 - Posted: 19 Jan 2006, 11:48:17 UTC - in response to Message 233446.
	The BOINC client normally should stop the computing done by the SETI@home client when the host goes on battery. This is a function for Laptops, where computing a WU will drop down the runtime a lot. There is a option in the preferences to set it on or off, default is on. But it should not crash in this case. Is it possible that your UPS configuration try to shut down all applications and kill the BOINC and SETI@home clients, braking the computation? Thanks Jens for the quick response. I don't have my host set up to shutdown applications when it switches to UPS. Actually, my UPS is not that sophisticated (I'm assuming I need an input signal other than the power supply to make the host understand I've switched to UPS). I'm using RHEL 4 on a Dell i370 EM64T. The rub is going to be that I'm using an optimized version of the boinc client (Harold Naparst's client) so I doubt Berkeley can do anything about it. Since my UPS is not that sophisticated and am actually not running UPS software on my host, I guess it's just pure coincidence. I'll have to see whether this happens a third time but it seems puzzling to me that it could. JV ____________
	ID: 233455 ·

Doris and Jens Volunteer developer Volunteer tester Send message Joined: 21 Nov 99 Posts: 362 Credit: 976,542 RAC: 339	Message 233470 - Posted: 19 Jan 2006, 13:12:43 UTC - in response to Message 233455.
	Okay, thanks for the reply. If you have a new idea what happend, please let me know. If the UPS has some switch time from line to battery, this may be followed by several problems, but it is always very difficulty to find out what happend. If you see it again, you may try to view the logs, if the linux power management system reports the problems, or other error messages pop up. Hopfully you wil not see it again. :) ____________ Greetings from Bremen/Germany Jens Seidler (TheBigJens)
	ID: 233470 ·

Questions and Answers : Unix/Linux : Reached daily quota of 2 results