Message boards :
Number crunching :
Panic Mode On (105) Server Problems?
Message board moderation
Previous · 1 . . . 22 · 23 · 24 · 25 · 26 · 27 · 28 . . . 34 · Next
Author | Message |
---|---|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Try my steps that I used in the message earlier in the thread and use the Log Options. First you need to be using the Advanced View in BOINC Manager, not the Simple View. Change it in the View Tab. Then using the Options tab >> Event Log options, tick the network_status_debug, http_debug and work_fetch_debug options in the BOINC Diagnostics Flags menu and hit OK. Event Log options Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
ReiAyanami Send message Joined: 6 Dec 05 Posts: 116 Credit: 222,900,202 RAC: 174 |
Thank you, Keith. Now I'm receiving a long event log, but it still says the same thing. 4/12/2017 3:39:26 PM | | [network_status] status: online 4/12/2017 3:39:27 PM | SETI@home | [http] [ID#17] Info: Could not resolve host: setiboincdata.ssl.berkeley.edu 4/12/2017 3:39:27 PM | SETI@home | [http] [ID#17] Info: Closing connection 15 4/12/2017 3:39:27 PM | SETI@home | [http] [ID#18] Info: Could not resolve host: setiboincdata.ssl.berkeley.edu 4/12/2017 3:39:27 PM | SETI@home | [http] [ID#18] Info: Closing connection 16 4/12/2017 3:39:27 PM | | [network_status] got HTTP error - checking ref site 4/12/2017 3:39:27 PM | SETI@home | [http] HTTP error: Couldn't resolve host name 4/12/2017 3:39:27 PM | | [network_status] got HTTP error - checking ref site 4/12/2017 3:39:27 PM | SETI@home | [http] HTTP error: Couldn't resolve host name 4/12/2017 3:39:27 PM | | [network_status] status: reference site lookup pending How can I use this information? If I keep running this, does it automatically debug and correct the situation? I'm quite ignorant about network and programs. |
ZenMercenary Send message Joined: 16 Mar 17 Posts: 15 Credit: 3,924,868 RAC: 0 |
Just checking: is anyone else having an issue where they have a massive amount of tasks sitting in "Validation Pending" status? I have 590 as of right now and that number seems to go up every time I've looked since this morning (was about 300 this morning). The only reason I noticed is because my credits are not rising nearly as much as they normally do on a Wednesday after the Tuesday downtime. |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
You might be getting a server time out while it is processing 400 uploaded tasks. Try adding this to cc_cinfig under options (I would suggest 100). <max_tasks_reported>N</max_tasks_reported> - Report at most N tasks per scheduler RPC. Try N=1000 if your computer has lots of tasks to report and is having trouble completing a scheduler RPC. |
JaundicedEye Send message Joined: 14 Mar 12 Posts: 5375 Credit: 30,870,693 RAC: 1 |
Just checking: is anyone else having an issue where they have a massive amount of tasks sitting in "Validation Pending" status? I have 590 as of right now and that number seems to go up every time I've looked since this morning (was about 300 this morning). Please read the last 5 posts and try using that procedure. [edit] nevermind......... "Sour Grapes make a bitter Whine." <(0)> |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
I looked at your pendings, and they are not out of line at all. They normally run about the same value as valid tasks +/- 20%. It is all up to your wingman reporting the tasks ..... |
rob smith Send message Joined: 7 Mar 03 Posts: 22231 Credit: 416,307,556 RAC: 380 |
Pending tasks has nothing to do with the problems that are being discussed in the previous five posts, and there is nothing we can do about them apart from wait. Back to the problems - the first thing I can see is that you don't appear to have access to a suitable DNS entry for SETI's servers: 4/12/2017 3:39:27 PM | SETI@home | [http] [ID#17] Info: Could not resolve host: setiboincdata.ssl.berkeley.edu I would expect the time-out to occur during a later stage of the communication, not during establishing the link. One question at a time: How do you connect to the internet? (It may be that during the period of time when there were issues with SETI's DNS entries that you ISP's DNS server lost track of things) Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
ReiAyanami Send message Joined: 6 Dec 05 Posts: 116 Credit: 222,900,202 RAC: 174 |
You might be getting a server time out while it is processing 400 uploaded tasks. Thank you, Brent. I checked cc-config and N was 0. I changed it to 100, and I still have all 400 tasks. (I tried 1000 and not resolved) Should I make N bigger or smaller? 4/12/2017 4:17:36 PM | | [work_fetch] Request work fetch: Backoff ended for SETI@home 4/12/2017 4:17:36 PM | | [work_fetch] ------- start work fetch state ------- 4/12/2017 4:17:36 PM | | [work_fetch] target work buffer: 864000.00 + 864000.00 sec 4/12/2017 4:17:36 PM | | [work_fetch] --- project states --- 4/12/2017 4:17:36 PM | SETI@home | [work_fetch] REC 981418.379 prio -1.000 can't request work: too many uploads in progress 4/12/2017 4:17:36 PM | | [work_fetch] --- state for CPU --- 4/12/2017 4:17:36 PM | | [work_fetch] shortfall 20736000.00 nidle 12.00 saturated 0.00 busy 0.00 4/12/2017 4:17:36 PM | SETI@home | [work_fetch] share 0.000 4/12/2017 4:17:36 PM | | [work_fetch] --- state for NVIDIA GPU --- 4/12/2017 4:17:36 PM | | [work_fetch] shortfall 5184000.00 nidle 3.00 saturated 0.00 busy 0.00 4/12/2017 4:17:36 PM | SETI@home | [work_fetch] share 0.000 4/12/2017 4:17:36 PM | | [work_fetch] ------- end work fetch state ------- 4/12/2017 4:17:36 PM | SETI@home | [work_fetch] request: CPU (0.00 sec, 0.00 inst) NVIDIA GPU (0.00 sec, 0.00 inst) 4/12/2017 4:17:36 PM | SETI@home | [http] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 4/12/2017 4:17:36 PM | SETI@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set 4/12/2017 4:17:37 PM | | [network_status] status: online 4/12/2017 4:17:37 PM | SETI@home | [http] [ID#1] Info: Could not resolve host: setiboinc.ssl.berkeley.edu 4/12/2017 4:17:37 PM | SETI@home | [http] [ID#1] Info: Closing connection 13 4/12/2017 4:17:37 PM | | [network_status] got HTTP error - checking ref site 4/12/2017 4:17:37 PM | SETI@home | [http] HTTP error: Couldn't resolve host name 4/12/2017 4:17:37 PM | | [work_fetch] Request work fetch: RPC complete 4/12/2017 4:17:38 PM | | [network_status] status: reference site lookup pending |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
Does that computer even have internet access? 4/12/2017 4:17:37 PM | SETI@home | [http] [ID#1] Info: Could not resolve host: setiboinc.ssl.berkeley.edu 4/12/2017 4:17:37 PM | SETI@home | [http] [ID#1] Info: Closing connection 13 4/12/2017 4:17:37 PM | | [network_status] got HTTP error - checking ref site 4/12/2017 4:17:37 PM | SETI@home | [http] HTTP error: Couldn't resolve host name 4/12/2017 4:17:37 PM | | [work_fetch] Request work fetch: RPC complete 4/12/2017 4:17:38 PM | | [network_status] status: reference site lookup pending What is the result from the reference site? You should get "Internet access OK - Project servers may be down" You might try from a DOS window (Widows Start / Run / cmd) ping google.com ping setiboinc.ssl.berkeley.edu |
Wiggo Send message Joined: 24 Jan 00 Posts: 34946 Credit: 261,360,520 RAC: 489 |
Maybe running, ipconfig /flushdns, will clear your problem. Cheers. |
ReiAyanami Send message Joined: 6 Dec 05 Posts: 116 Credit: 222,900,202 RAC: 174 |
Does that computer even have internet access? Yes, it says: 4/12/2017 4:17:39 PM | | [http] [ID#0] Received header from server: 4/12/2017 4:17:39 PM | | [http] [ID#0] Info: Connection #10 to host www.google.com left intact 4/12/2017 4:17:39 PM | | Internet access OK - project servers may be temporarily down. |
ReiAyanami Send message Joined: 6 Dec 05 Posts: 116 Credit: 222,900,202 RAC: 174 |
Maybe running, ipconfig /flushdns, will clear your problem. Thank you, Wiggo. Flushdns was successful but still not solved the problem. |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
What about nslookup setiboinc.ssl.berkeley.edu .. and goggle.com Resolves to an IP? |
Ghia Send message Joined: 7 Feb 17 Posts: 238 Credit: 28,911,438 RAC: 50 |
Maybe running, ipconfig /flushdns, will clear your problem. That solved things here. Exit Boinc, reboot computer without starting Boinc, then flush the DNS cache. Reboot, restart Boinc. Humans may rule the world...but bacteria run it... |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Good advice to flush the DNS entries after first rebooting the computer and before starting BOINC. I also wonder whether you had added any entries in your HOSTS file for the outdated server IP addresses in the past. That would certainly cause your connection issue. The flushdns and then a registerdns should resolve the correct IP addresses though. If and when you get things sorted out, you can then go back in to the Event Log options and select Default >> OK to get back to the standard log entries. That will get it back to normal activity and the file won't be so busy. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
ReiAyanami Send message Joined: 6 Dec 05 Posts: 116 Credit: 222,900,202 RAC: 174 |
What about Google is fine, but *** can't find setiboinc.ssl.berkeley.edu: Server failed |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
You could try to change your IPS DNS to use Google DNS 8.8.8.8 and 8.8.4.4 |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
What about Looks like your ISP doesn't have a record for it anymore. Name: setiboinc.ssl.berkeley.edu Address: 208.68.240.126 SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
ReiAyanami Send message Joined: 6 Dec 05 Posts: 116 Credit: 222,900,202 RAC: 174 |
What about When I looked up 208.68.240.126 synergy.ssl.berkeley.edu was returned |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
What about That does look like the host name of the server. scheduling server synergy scheduler process synergy feeder synergy However since the project doesn't use server host names to communicate with you might want to temporarily add entries to your local host file. 208.68.240.110 setiathome.berkeley.edu 208.68.240.126 setiboinc.ssl.berkeley.edu 208.68.240.118 setiboincdata.ssl.berkeley.edu 208.68.240.119 boinc2.ssl.berkeley.edu 208.68.240.127 boinc2.ssl.berkeley.edu I use google, 8.8.8.8, for my primary DNS in my router and my ISP DNS as secondary. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.