Problem reporting tasks
Problem reporting tasks |
|
| log in |
Message boards : Number crunching : Problem reporting tasks
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
| Author | Message |
|---|---|
That problem has been explained a few times before, but I cannot find the right thread right now. It has something to do with the scheduler or the feeder only having 100 units every 6 seconds, and if those are used/taken/send to someone else, you'll get the msg no work available althought there might be thousands of units shown on the server status page or the cricket graph not being maxed out. In other words, keep trying , it'll work eventually :) I agree, its happening post outage as well... ____________ | |
ID: 1021474 ·  | |
Did you set it to no new tasks? Try hitting the update button a couple of times if needed to see if that will send them in. I've tried with and without no new tasks set. Hitting the update button just forces the comms deferred to get longer and longer. Then it eventually returns to 1 min and then repeats ____________ | |
| ID: 1021485 · | |
|
Not complaining since today is my 9th anniversary here but..................... | |
| ID: 1021508 · | |
|
This thread is drifting off topic. It was started to report that there is a problem with some computers not being able to report tasks. These computers are getting the "SETI@home Scheduler request failed: HTTP internal server error" This problem started on the 27th of July (before the last three day outage). I now have one week's worth of work on one computer that I can't report and cannot get new work. My other computer is working just fine. Can anyone come up with any more ideas as to what the problem might be? | |
| ID: 1021560 · | |
|
none of my comps can report, uploads are fine, just get | |
| ID: 1021570 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906  | |
none of my comps can report, uploads are fine, just get There are communication problems but only one of your pc's did not report since July 25th. The other onces all reported today. | |
| ID: 1021572 · | |
sorry about that didn't notice the others did manage to get through but the one that hasn't reported sense the 25th is dry, I would care as much if it still had at least one to chew on. ____________  | |
| ID: 1021574 · | |
This thread is drifting off topic. It was started to report that there is a problem with some computers not being able to report tasks. These computers are getting the "SETI@home Scheduler request failed: HTTP internal server error" This problem started on the 27th of July (before the last three day outage). I now have one week's worth of work on one computer that I can't report and cannot get new work. My other computer is working just fine. Can anyone come up with any more ideas as to what the problem might be? its occuring on my laptop and one of my boxes, but the other two are fine ... Houston, I think we have a problem ... ____________ | |
| ID: 1021576 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906 | |
This thread is drifting off topic. It was started to report that there is a problem with some computers not being able to report tasks. These computers are getting the "SETI@home Scheduler request failed: HTTP internal server error" This problem started on the 27th of July (before the last three day outage). I now have one week's worth of work on one computer that I can't report and cannot get new work. My other computer is working just fine. Can anyone come up with any more ideas as to what the problem might be? I agree! At this moment, most (if not all) pc's have a hard time reporting tasks but eventually they get through. A number of pc's cannot report at all and have not been able to do so since July 26, a full day before the outage. We can only hope that the troublesome scheduler communications and the HTTP internal server errors are related and will be fixed tomorrow. If the number of affected pc's is too low, we could end up with having to reset the project. One of my teammates did this, loosing 4200 finished tasks in the process, but the problem was solved ;-) | |
| ID: 1021577 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906 | |
Your laptop fits the profile, the other ones reported today. | |
| ID: 1021579 · | |
At this moment, most (if not all) pc's have a hard time reporting tasks but eventually they get through. A number of pc's cannot report at all and have not been able to do so since July 26, a full day before the outage. I may have to consider reseting or detach/attach, but i'll wait until the report deadlines have passed... there's alway hope :-P dlanor ____________ | |
| ID: 1021580 · | |
|
I found that in my case the HTTP Server internal error was related to my app_info.xml file. This contained references to older application versions which are no longer used. (the content of app_info.xml is reported on any update) | |
| ID: 1021602 · | |
|
Well since a few minutes, I'm able to UP-DOWN-Load and report! | |
| ID: 1021605 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906 | |
I modified the app_info.xml files on both my problem pc's by removing the references to: - Astropulse - Astropulse_v5 - setiathome_enhanced version 5.28 I left Astropulse version 5.05, Enhanced version 6.03, and Enhanced 6.08. Both pc's reported fine after the change. Thanks BW! | |
| ID: 1021610 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906 | |
|
For some reason my Linux pc's and an XP pc running Boinc 6.6.20 do not have this problem. The only difference is that the affected pc's had a reference to astropulse (which is version 5.0) and the others did not. | |
| ID: 1021612 · | |
|
Previous message was from my LapTop (WLAN) and this comes from one of my Q6600 with GTS2500 (CUDA) and can't still report. | |
| ID: 1021618 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906 | |
Previous message was from my LapTop (WLAN) and this comes from one of my Q6600 with GTS2500 (CUDA) and can't still report. Did you check the app_info.xml for references to old Astropulse and Enhanced versions as described in the previous messages? | |
| ID: 1021620 · | |
Those are the only references I've left, too. Removed the 'older numbers' some time ago, while editting the app_info.xml files for AP. The 'problem host',(this one) hasn't been checked, yet for previous MB and/or AP entries, which I'll do a.s.a.p. (It's also the only with VISTA 32BIT) Other have XP x86, my X64 is still down. So it can be the 'entry numbers', for AP ,(also MB) causing this? Will check this again and report back, but I'm fairly shure, to have removed all old entries in the app_info.xml files. ____________  Knight Who Says Ni N!, OUT numbered................. | |
| ID: 1021624 · | |
|
S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 175 Credit: 119,690,617 RAC: 105,906 | |
Removing old references worked for BuddyWolly and for me. The only "odd" reference my problem pc's had in common was Astropulse version 5.00 so that one could be the culprit. There is still a Linux application for Enhanced 5.28 so that one could be fine. | |
| ID: 1021625 · | |
|
Will have a look again, for AstroPulse 5.0, which is obsolete, nowadays. | |
| ID: 1021627 · | |
Message boards : Number crunching : Problem reporting tasks
| Copyright © 2013 University of California |
