[EnVoy]

Ok, so I run the GUI version of F@H, fill in my name and team 16. The display just sits there, and says:

Loading...
benchmarking...
Progress: 0%

I don't think it actually loaded anything to work on, and suspect it is a firewall prob. I have a Linksys firewall/router set up.

Can anyone help me with the proper settings to get this working? Thanks..

[reader50]

The GUI client is known to be slow sometimes. You can launch ProcessViewer to see if it's doing anything:
/Applications/Utilities/Process Viewer.app

Sort by CPU usage, Folding should come to the top.

You can also check the work unit logfile located at:
/Users/(you)/Library/Folding@home/work/logfile_01.txt

This logfile notes when the client completes each frame. If there are no logfiles in /work, then the client really is hanging before it can start up.

While there, check for the crunch core located at:
/Users/(you)/Library/Folding@home/core_65.exe

If this core is not present on a Mac, the client was unable to fetch it from Stanford and the client really is hung.

With your dual CPU setup, you can double your production by installing two instances of the CLI client instead of the GUI. Or if you like the GUI graphics, you could install one CLI client in addition to the GUI client. If you do add CLI clients, be sure to launch them with the "-local" tag so they work from separate work folders, and to give them different machine ID numbers so they work on separate work units.

[Shaktai]

Originally posted by EnVoy:
Ok, so I run the GUI version of F@H, fill in my name and team 16. The display just sits there, and says:

Loading...
benchmarking...
Progress: 0%

I don't think it actually loaded anything to work on, and suspect it is a firewall prob. I have a Linksys firewall/router set up.

Can anyone help me with the proper settings to get this working? Thanks..

Does it display a protein name or number in the GUI?

Folding@Home proteins vary dramatically in size. If you got a large protein the first time it could take a while before you see any progress. Depending on your machine and the particular protein, it could take from several hours to several days for it to process. Of course the larger the protein, the more points you gain per unit.

Also, with the GUI, run it with the window hidden, not minimized. (Command H) This reduces the graphics overhead and improves speed to be almost on par with the CLI.

[EnVoy]

F@H is using 0% in top.

It does not display a protein name or number.

[reader50]

Correction: Folding shows activity in top as "FahCore_65". The "Folding@home" process is a user interface to the crunch core.

[EnVoy]

There is no core_65.exe at;

/Users/(me)/Library/Folding@home/

and no "FahCore_65" in top.

[reader50]

I'd suggest killing the GUI app for now and installing a copy of the CLI client. Launch it without the "-local" tag so it will use the same folder as the GUI client. The Terminal messages should give some idea of where the error is happening.

[EnVoy]

Ok, So here is what I get from the CLI version:

[14:31:57] - Ask before connecting: No
[14:31:57] - User name: cg118 (Team 16)
[14:31:57] - User ID = XXXXXXXXXXXXXXX
[14:31:57] - Machine ID: 1
[14:31:57]
[14:31:57] Loaded queue successfully.
[14:31:57] + Benchmarking ...
[14:32:06]
[14:32:06] + Processing work unit
[14:32:06] Core required: FahCore_65.exe
[14:32:06] Core not found.
[14:32:06] - Core is not present or corrupted.
[14:32:06] - Attempting to download new core...
[14:32:06] + Downloading new core: FahCore_65.exe
[14:32:15] - Error: HTTP GET returned error code 0
[14:32:15] + Error: Could not download core
[14:32:15] + Core download error (#2), waiting before retry...

[14:32:30] + Downloading new core: FahCore_65.exe
[14:32:30] - Error: HTTP GET returned error code 0
[14:32:30] + Error: Could not download core
[14:32:30] + Core download error (#3), waiting before retry...

I think it is the firewall blocking the WU from being downloaded?

[Welnic]

It could just be the F@H server being flaky. I have seen about 7 download attempts in one of my logs on a machine that ordinarily didn't have any problems.

But I have heard of people not being able to run F@H through a corporate firewall. But I think that the problem occurred during the upload part.

One thing that you could try would be to download something from the command line using "get", which is what the F@H client is trying to use.

[reader50]

The client reached the assignment server and got a work unit. It attempted to grab the proper crunch core, but was failing for some reason.

Grab the core manually. Unstuff and place in the Folding folder. You may need to "chmod +x" on it to make it executable:

http://www.stanford.edu/~pande/OSX/P...Core_65.exe.bz

If that doesn't do it, the project crunch core folder also contains another file which you could drop into the Folding folder:

http://www.stanford.edu/~pande/OSX/PowerPC/Core_65.fah

[EnVoy]

I'm not at the machine now, but I seem to remember the file "Core_65.fah" already being in the F@H folder. Don't know if that make sa difference or not. I'll try to download the WU file manually later when I am at the machine....

[EnVoy]

In another post I found that Adelphia blocks port 80. I have Adelphia cable modem, could this be the problem?

[EnVoy]

OK, downloaded the .exe file, and the .fah file. Still no go, I get the same errors on the CLI version, and the GUI version just sits there saying "benchmarking...: with no protien name or news. Any suggestions?

And what about the Adelphia and port 80 thing...

[reader50]

Port 80 is used for web serving, and the ISP block would be against incoming port 80 requests. In other words, your ISP will not allow you to set up a web server and serve pages to other people. However, the Folding server should not be sending any port 80 requests to you because such requests would go to Apache rather than Folding, so that block should not matter in this case.

Your client install is behaving oddly. I'd suggest wiping the client and the Folding@home folder. Start over with a fresh client install, most likely the CLI so you can see the error messages. If the CLI can set up a new Folding@home folder properly, you will be able to quit the CLI and let the GUI client take over.

[EnVoy]

One thing that you could try would be to download something from the command line using "get", which is what the F@H client is trying to use.

I tried "man get" and the CLI returns: no manual entry for get

Does this mean the get command is not installed, or not working?

[bousozoku]

Ports 80 and 8080 (secure web) are both used by folding@home. Make certain that the latter is also open.

There is no get directly from the command line. It is a subcommand within ftp--file transfer protocol.

Did you move the Core_65.exe into the folding@home folder after you downloaded the core? If it's not finding it then, it's odd indeed.

[EnVoy]

OK, I'll check those ports.

Yes, Core_65.exe is in the folding@home folder.

[EnVoy]

How can I make certian that port 8080 is open? My firewall/router (Linksys) doesn't specificaly list that port. I tried doing a port scan from the machine, but that didn't seem to work.

[mikkyo]

Have you tried deleting the whole Folding@home directory in your ~/Library?
If the permissions get screwed up and the client can't write to that directory it will behave exactly as you have described.

[EnVoy]

Nevermind, got it working!

It was a specific setting in the firewall....

F@H is in effect....

[Shaktai]

Congratualions! Nothing like being persistent. Glad to have you on board.

[bousozoku]

Congratulations on your victory over the firewall!

Software setup should be easier.