Page 1 of 1
Client banned after as a result of 7.3.6 troubleshooting.
Posted: Sat Mar 02, 2013 1:32 pm
by warp-9.9
Using warp9pnt9, it connects to the assignment servers and sends me to an IP for a nonexistent server 171.64.122.137. If I use another name, I get a work unit. Unban this so I can process data. I reverted to 7.2.9 which worked flawlessly for me. My work units got corrupted in the process and have all been deleted.
Re: Client banned after as a result of 7.3.6 troubleshooting
Posted: Sat Mar 02, 2013 4:34 pm
by Joe_H
Post your log showing the system and configuration information and the messages showing the client attempts to connect to servers and the results. Too little information to troubleshoot the problem. As for banning, I have not heard of that happening.
Re: Client banned after as a result of 7.3.6 troubleshooting
Posted: Sat Mar 02, 2013 5:33 pm
by bruce
The servers do sometimes protect themselves from bad hardware that might draining them of WUs. Just how many WUs were discarded in our debugging effort when you use warp9pnt9? There's nothing wrong with reverting to V7.2.9 if it's working for you.
You might also consider switching from the WebControl application (which opens in your browser and which is designed for the utmost in simplicity) to the FAHControl user interface that's designed for experts -- provided that's your choice. It would be more like the interface you were using in V7.2.9.
Please post some of the logs showing the troubles you had. Every time you restart V7, it creates a backup of the previous log in a subdirectory of the FAH data directory listed by date and time.
Re: Client banned after as a result of 7.3.6 troubleshooting
Posted: Sun Mar 03, 2013 9:13 am
by warp-9.9
Now it's downloading. Absolutely no changes on my end. The servers must have thought I was throttling too much. About 10 installs/uninstalls. About 8 discarded WUs. The first three were almost done too.
Before is when it kept getting assigned to nonexistent server as previously mentioned. There was nothing wrong with my config, as I said, and no other information to be gained, as I said. Now I get a proper server IP and will just go back to silently crunching numbers. And avoid updates at all costs.
Code: Select all
09:05:19:Trying to access database...
09:05:19:Successfully acquired database lock
09:05:19:Enabled folding slot 00: READY smp:8
09:05:19:Enabled folding slot 01: READY gpu:0:"GF100 [GeForce GTX 480]"
09:05:19:Enabled folding slot 02: READY gpu:1:"GF100 [GeForce GTX 480]"
09:05:19:WU00:FS00:Connecting to assign3.stanford.edu:8080
09:05:19:WU01:FS01:Connecting to assign-GPU.stanford.edu:80
09:05:19:WU02:FS02:Connecting to assign-GPU.stanford.edu:80
09:05:19:WU00:FS00:News: Welcome to Folding@Home
09:05:19:WU00:FS00:Assigned to work server 171.67.108.35
09:05:19:WU00:FS00:Requesting new work unit for slot 00: READY smp:8 from 171.67.108.35
The only thing now is that all the "About Project" pages give a 500 Internal Server Error, which I thought meant the client had become outdated, or a change made on server.
http://fah-web.stanford.edu/cgi-bin/fah ... ned?p=8082 works fine in a browser, but withion the FAHControl, gets
Code: Select all
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
root@localhost and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.0.52 (CentOS) Server at fah-web.stanford.edu Port 80</address>
</body></html>
As I said, works fine in my browser. Same error in FAHControl for all projects.
I do not know if these messages are cached, but I assume they are. So I may have to wait until some WUs finish and new ones are ready to download, and run a tcpdump (WireShark) to show all client communication.
Re: Client banned after as a result of 7.3.6 troubleshooting
Posted: Sun Mar 03, 2013 1:00 pm
by PantherX
warp-9.9 wrote:...The only thing now is that all the "About Project" pages give a 500 Internal Server Error, which I thought meant the client had become outdated, or a change made on server...
If the Server is 129.74.85.15, then it is a known issue and you can read about it here -> viewtopic.php?f=18&t=23599