Windows SMP Client, general troubleshooting

[gedon]

I created a link to fahlog.txt on my desktop. should give you the same info as the commandline

[gedon]

Project: 2652 (Run 0, Clone 236, Gen 23)

has anybody else problems with this unit too?

got it three times, and three EUEs at 3%

[Strongwolf]

Errr, I never chk that kind of info. My bad.

[Samuknow]

[00:31:31] - Ask before connecting: No
[00:31:31] - User name: samuknow (Team 45)
[00:31:31] - User ID: 3A454971471DC463
[00:31:31] - Machine ID: 1
[00:31:31]
[00:31:31] Work directory not found. Creating...
[00:31:31] Loaded queue successfully.
[00:31:31] - Preparing to get new work unit...
[00:31:31] + Attempting to get work packet
[00:31:31] - Connecting to assignment server
[00:31:31] - Successful: assigned to (0.0.0.0).
[00:31:31] + News From Folding@Home: Welcome to Folding@Home
[00:31:31] Work Unit has an invalid address.
[00:31:31] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[00:31:49] + Attempting to get work packet
[00:31:49] - Connecting to assignment server
[00:31:49] - Successful: assigned to (0.0.0.0).
[00:31:49] + News From Folding@Home: Welcome to Folding@Home
[00:31:49] Work Unit has an invalid address.
[00:31:49] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[00:32:01] + Attempting to get work packet
[00:32:01] - Connecting to assignment server
[00:32:02] - Successful: assigned to (0.0.0.0).
[00:32:02] + News From Folding@Home: Welcome to Folding@Home
[00:32:02] Work Unit has an invalid address.
[00:32:02] - Error: Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[00:32:25] + Attempting to get work packet
[00:32:25] - Connecting to assignment server
[00:32:26] - Successful: assigned to (0.0.0.0).
[00:32:26] + News From Folding@Home: Welcome to Folding@Home
[00:32:26] Work Unit has an invalid address.
[00:32:26] - Error: Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[00:33:14] + Attempting to get work packet
[00:33:14] - Connecting to assignment server
[00:33:14] - Successful: assigned to (0.0.0.0).
[00:33:14] + News From Folding@Home: Welcome to Folding@Home
[00:33:14] Work Unit has an invalid address.
[00:33:14] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[00:34:47] + Attempting to get work packet
[00:34:47] - Connecting to assignment server
[00:34:47] - Successful: assigned to (0.0.0.0).
[00:34:47] + News From Folding@Home: Welcome to Folding@Home
[00:34:47] Work Unit has an invalid address.
[00:34:47] - Error: Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[00:37:36] + Attempting to get work packet
[00:37:36] - Connecting to assignment server
[00:37:37] - Successful: assigned to (0.0.0.0).
[00:37:37] + News From Folding@Home: Welcome to Folding@Home
[00:37:37] Work Unit has an invalid address.
[00:37:37] - Error: Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[00:43:10] + Attempting to get work packet
[00:43:10] - Connecting to assignment server
[00:43:10] - Successful: assigned to (0.0.0.0).
[00:43:10] + News From Folding@Home: Welcome to Folding@Home
[00:43:10] Work Unit has an invalid address.
[00:43:10] - Error: Attempt #8 to get work failed, and no other work to do.
Waiting before retry.

This is all I get at home.

Work rig is plugging away.

[Samuknow]

Never mind. I got it to work finally. Copied the work folder from my other client and then restarted it. It immediately DL new work and took off.

[Strongwolf]

I get that crap too. Haven't been able to finish any WU's lately. Between my dad and I manage to ruin some work. I insist to OC while at SMP and sometimes I just have dump everything and start over again. Can't help it. The Opty, the cards, the memory are behaving so well that is hard to resist the temptation to OC. My dad keep turning off almost everything he see on. Partialy disasemble my sound system and turn off Wolf1 everytime he see it on (W1 is in another room). He has AD you know so there's not much I can do but turn it on again. Wolf2 is still off line.

[keithwalton]

Originally Posted by gedon

Project: 2652 (Run 0, Clone 236, Gen 23)

has anybody else problems with this unit too?

got it three times, and three EUEs at 3%

I've had several problems with 2652's in the past (http://www.aoaforums.com/forum/samuk...tml#post457429)

your lucky they are EUE'ing at 3% and not 86% as thats half an hour of cpu time wasted rather than 14 hours!

[ThunderRd]

@Sam:
0.0.0.0 errors are simply an indication of busy assignment servers. It's an intentional message to let you know that you can't connect at the moment. The recommended procedure is to WAIT. I see this with some regularity and sometimes it takes hours. There were, incidentally, a number of complaints on the community forum yesterday about busy servers. It seems to run in spurts.

EDIT: Interestingly enough, I had 4 clients waiting on 0.0.0.0.today at the same time. As I was standing there, one of them jumped to attention and connected. Without any further action from me, the others, one by one, connected after that and downed. They had been waiting 3 hours+.

@Keith:
Some generations of 2652 are known problems; some people get them to run, some don't. I have had success on *most* of mine. Plenty of info on the forum, check it out. On several occasions I have had some of these EUE and after rolling back to an earlier backup have gotten them to finish without a problem.

Are you running any backup strategy? It really helps.

@Everyone:
I follow the community forum quite closely. I read the same complaints that most of us have on a regular basis. I normally know if a server is down, or there is a bad WU out there. I also am aware (although not always able to correct) of the intermittent problems with the client. The bottom line is:

It's a beta client.

Remember that your production of 900+ points per day is a compensatory figure to account for lost time with the client. The Pande guys ain't dumb. They know it doesn't work as they would like it to, so they give you extra points for being a beta tester. That's why version 6 releases have been made on every client recently EXCEPT the Windows SMP. It's still in beta 5.91. They want it to behave as well as the other (Windows and Linux) clients.

If you have patience and time, you can far outproduce running two standard clients.

If you don't, well, it's not for you. I'll give you an example. Yesterday I opened one of my shops in the morning to find the following (19 machines):
a)9 hung clients
b)2 EUE's
c)3 I/O errors
d)1 0x7E error
e)4 machines running properly

Now, this wasn't a good way to start my day but I took a deep breath and got down to it. I reckon that it was the result of some network hiccup during the night. In the end (about 1.5 hours later) I had all clients running, and lost NO work units. I had to restore the 2 EUE's from an 8 hour old backup, as well as the 0x7E error.

So I took a hit and produced only 9000 instead of 30k for the day. But I'm still way ahead of what I WOULD produce if I wasn't running SMP. I just take the bad with the (far more attractive) good.

[Samuknow]

Again, my rig at work is flawless. @ 99 on it's 3rd set already.

I am still having issues at home.

I have uninstalled several times. I did forget I was overclocking also. I set to default. I will see if that helps.

[ThunderRd]

Originally Posted by 7im [community forum moderator, responding to an impatient user who bitched to him about his statement that "it's a beta, it has unresolved problems"]

Not an excuse, it's a stated fact for all Beta Clients: As in the use of any beta software, please make sure to back up your hard drive, and do not run this client if you or your hardware cannot tolerate even the slightest instability or problems.

Teddy, if you can't handle an occasional server outage for the BETA SMP clients, feel free to run the more stable CPU clients.

Thank you for reporting the server problem. Someone IS looking in to the problem.

Originally Posted by kasson [of Pande Group]

Server 171.64.65.65 is running, but as you can see from the server status page it is experiencing extremely high network traffic. This may be responsible for the delays in obtaining new work.

This is in response to complaints about the 0.0.0.0 problem; it's acknowledged and people are on the case. You cannot change the server that your particular WU calls for; if you try to you'll lose it. At least wait until your finished WU has upped, then you can delete your work folder and your queue file. Then re-start the client and it will look for an assignment server. If you still get zeroes, WAIT. It WILL connect eventually.

I will say again, you need to have patience. Your patience will pay off, but you have to have it to begin with, or you're not going to make it work.

[Samuknow]

No biggie. I can wait. I just thought it was odd the the one at work fired right up and the one at home has been throwing a hissy fit from the get go.

[Samuknow]

It appears that the SMP client at home decided to start working today.....

It is chugging away. Should start seeing an increase in a few days....YAY..

[ThunderRd]

Glad to hear it's working now. Keep it going.

[Daniel ~]

The sweetness comes with the fruit, which flowers last.":O}

[Strongwolf]

Do a fresh install of WXP (don't ask me why,please)wipe out all my data including F@H. Download with Opera, Firefox and IE and couldn't install it cause the file was corrupted. Everytime I try to download SMP again it won't cause is already there. Try to find the dam file everywhere and can't find it to erase it and try again. Run out of places to look for it. Any ideas. Use win search and explorer and erase everything I found. Still can't download. ??

[ThunderRd]

I'm not sure that I understand. Are you saying that you formatted and made a fresh install of OS, then you downloaded the file from the F@H site 3 times, with 3 different browsers, and it was corrupted every time?

If that seems to be the case my money says that the file is ok. It sounds to me like it is more likely that you have a problem with the Windows Installer or the service. I mean, what are the chances that 3 different downloads would be corrupted? I'd be very surprised if the file on the site is corrupt. If it were, there would be complaints on the forum site.

Check to make sure that the Windows Installer service is running. On the machine I'm on right now, it is set to manual, but perhaps you have to set it to automatic. Then check the RPC Service. There is a dependency and RPC must be set to Automatic and be running for the WI to run. Also check the DCOM Server Process Launcher Service. I think it's related to the Installer in some way I can't remember.

As far as not being able to find the file, well, IDK. Are you searching under the right name? The correct filename is: "Folding@Home Windows SMP Client.EXE". Can you download it to another machine and use a thumb drive to move it to the target?

Get all those services up and then run the file again.

[Strongwolf]

What's "IDK"?

Yes, three diferent downloads with same results.
"The data section of this self-extracting file has been damage.( CRC errror;
Should be F02E7018, is A8965BC".
Indows Instaler is running in auto now; RPC is in auto now and started; DCOM Server Process Launcher Service is started and in auto; still no go.
Have 3 flash drives and an external portable HDD: none works! I do search with the correct name and other variations. Nada.

Gona borrow a flash drive from a friend and take the file from W1. Still...Where in Heaven is that dam file???? (retoric question).

Curious, my dad keep unpluging W1 from the socket and every time I re-start the system and the app. it runs smootly, like is nothing had happen. W3 SMP give trouble for almost anything. Just a note.

[Strongwolf]

Got the flash drive and the file from W1. Still a no go. I think there is something that is not supouse to be there. Chk it out:


Never mind, I got it working!!

[ThunderRd]

What was wrong?

[Strongwolf]

I really don't know. Imagine that the data (maybe I'm very wrong here) that was in the SMP folder that I copy has storage some of the data of the WU it was working on. So I delete the "work" folder and the "FahCore_a1.exe" folder. Start again and didn't work, so I post and let it running. After a couple of "unable to unzip and something starting with FATAL" it start by hinself. TBH I didn't know what I was doing, but is working now and is at 36% done.