|
Problems return WUs? Is anyone else having problems return WUs on their Linux SMP cores? This is the second time in the space of a week that I've had problems returning a WU. The first time I just deleted the work directory and started again. But it's happened again, and this is getting damned annoying: For some reason, when I shut my machine down and then restart it, I get an error indicating that the thing isn't able to resume the WU, and then when it tries to contact the work server, it can't. |
First thing I normally do if something like that happens is try to connect to the work server in my browser. If I get an "OK" then I know that problem is on my end. If I don't, then I check here: Folding@Home server status I checked the forum; the only complaints recently about server downage were on GPU servers. If the problem continues, try deleting the following from the fah directory: -work -all logfiles -unitinfo.txt -fahcore_n Then restart the Deino service if you are running that client. Otherwise make sure that the mpiexec process is killed, and any running core processes. Le the client down a new WU, and it will also download the current core file, and see if that helps. |
Ok, I'm having the same problem AGAIN! Here's some log output: Quote:
|
Gizmo, let's start that client with the -verbosity 9 flag so we can see more info (mainly we want to see which server you're trying to connect to unsuccessfully). Everything is normal in that log otherwise. If we know where it's calling home, we can check the server status page. |
Quote:
Ok, so when I ping that server with my browser, it comes back as 'Ok'. That begs the question: "What the hell is going on?" I'm obviously able to connect to the internet and download stuff, or I wouldn't be able to get the WUs to start with. If I su to fah (my folding user) and wget the status page, that works as well, so the issue isn't user permissions. |
I have seen the same thing occasionally, last time it turned out to be a problem with the ISP and a transparent proxy blocking the transfers somehow. IDK if that is the problem here or not. Can you resolve that address to an IP xxx.xxx.xxx.xxx? Then we can check the server page. Sometimes, even though you get OK status, the server is loaded heavily or it is in "reject" status and waiting is the only answer. Or the server may be in "accept" status for some reason, and it isn't assigning ATM. Again, waiting it out is the answer. Here's a possible solution that's recent: Folding Forum • View topic - can not connect to assign server for work I do know that when I see things like this, although they piss me off, they go away eventually in every case. All by themselves. |
I can ping them both by name: Quote:
I dunno if I've got some kind of a library problem or what, but it sure is frustrating. This has been goin on now for something like 1 1/2 weeks. That's a lot of power wasted. |
Here's an idea- Go to the folding directory, create a directory called "later" or some such, and move the work directory and the queue.dat file into it. You could delete them if you want, the finished WU already uploaded, so there's nothing of value there. Then, restart the client with the -config flag. You will get the configuration routine, make no changes. Does it download now? EDIT: I just checked those IPS, and servers are running normally according to the log pages. So problem isn't Stanford. Don't get fooled by being able to ping them, though. Normally they are pingable if they are in accept status, but they won't assign until staff works out the problem. Accept means "accepting connections", but the accepted connections just sit there. |
No, it doesn't, and the failure is pretty much instantaneous. I must have a borked library or something somewhere. Hmm......I just realized that I'm running the 6.24 beta version. I don't rightly remember when I downloaded it though. It seems like it was back in August some time, but maybe I ought to back down to the 6.02 client? |
If I were you, I'd let the client run overnight tonight and see if it has a WU in the morning. The 6.24 client IS the 6.02 client with a few upgrades regarding how it handles EUEs and some other changes, but basically the networking part is the same. I don't think using 6.02 would be any different. It's starting to sound like some transparent proxy issue to me. I'd wait it out and see. I'm going into a meeting now, and you're 12 hours different, so by the time I'm out you're sleeping. I'll check back with you tonight when you're back at work. |
No worse than dealing with my new owners in India. LOL. Thanks for your help, TR. |
I just had a thought... If you run the config routine again, instruct the client to use a web proxy (you'll have to find one on google or something, like hidemyass.com or another one - there are many). Then see if the client downloads. If it does, you have an ISP problem. That is how I discovered the cause of my own problem a while ago. When I reported it to the ISP they told me there was a new transparent proxy in place, and the IP filters were still being worked on. Sewveral days later, the problem was gone, and it didn't return. In my case, IIRC, I could download but not upload. WUs died on the vine, so to speak. |
There's no way that can be the problem for two reasons: 1) This is my traveling laptop: I take it between home and the office every day and I have the problem both places. 2) I have 5 other machines here folding away (1 Ubuntu, 1 fedora, 2 Gentoo, and 1 Windows) and they all are getting WUs just fine. It really looks like a local (laptop) issue of some kind, but I haven't the foggiest clue what it might be. |
I didn't know you had other machines connecting successfully. Maybe a reinstall of the client is in order. You might also try reinstalling the ia32-libs package. |
Have you had any success as yet? |
No ia32-libs package for Fedora 11. No compat-libstdc++ either. Apparently, it shouldn't be working at all. |
Some distros have the 32-bit support, but I know for sure that debian and derivatives do not. If the client runs, Fedora must have it. I forget what exactly needs it - it's either the client itself or the core. (not both) |
Quote:
|
Ok, after banging around in the folding forums for a few days, we finally figured out the issue: In /etc/nsswitch.conf, I changed the following: Quote:
Quote:
PPM, you're going to have to peddle faster to catch me! I got 5th gear back! |
Can you add a link to your thread over there...I can't find it. EDIT NM, I have it: http://foldingforum.org/viewtopic.ph...t=CosmHTTPOpen [note to self: Gizmo called jackofall a "GOD". will direct obscure linux queries to him from now on] @Gizmo, he's asking a followup question, don't know if you saw... |
| All times are GMT +1. The time now is 10:28 PM. |
Copyright ©2001 - 2010, AOA Forums