• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

FAH error in log file

B

BinarySynapse

[H]F Junkie
2FA
Joined
Feb 6, 2006
Messages
13,965
I keep getting this error in my FAHlog.txt file

Code: 
[00:22:40] + Attempting to send results
[00:23:10] Couldn't send HTTP request to server (wininet)
[00:23:10] + Could not connect to Work Server (results)
[00:23:10]     (171.65.103.162:8080)
[00:23:10] - Error: Could not transmit unit 01 (completed October 2) to work server.


[00:23:10] + Attempting to send results
[00:23:27] Couldn't send HTTP request to server (wininet)
[00:23:27] + Could not connect to Work Server (results)
[00:23:27]     (171.65.103.100:8080)
[00:23:27]   Could not transmit unit 01 to Collection server; keeping in queue.
[00:40:11] Writing local files
[00:40:12] Completed 220000 out of 250000 steps  (88)
[01:18:18] Writing local files
[01:18:18] Completed 222500 out of 250000 steps  (89)

What could be causing it?
 
marty9876 said:
http://fah-web.stanford.edu/serverstat.html

(171.65.103.100:8080) is in not accept mode

(171.65.103.162:8080) is up

How many WU's you got stuck in the queue? Are you monitoring with EM3? Looks liek might be >1 which is wierd.
Click to expand...

No I'm not using anything to monitor. I just open up the log file every now and then to see what's been going on. This error has been in there at least 20 times over the past three or four days.

Plus my stats on Hardfolding.com haven't gone up any since the initial statistics popped up.



 
stop console (service)

start>run "c:\where ever client\console5.05.exe" -send all

Run the client with -send all flag and see what happens
 
got this
Code: 
C:\Program Files\Fold@Home>FAH502-Console.exe -send all

Note: Please read the license agreement (FAH502-Console.exe -license). Further
use of this software requires that you have read and accepted this agreement.

No directory settings found in registry. Using current directory...


--- Opening Log file [October 5 01:42:51]


# Windows Console Edition #####################################################
###############################################################################

                       Folding@Home Client Version 5.02

                          [url]http://folding.stanford.edu[/url]

###############################################################################
###############################################################################

Launch directory: C:\Program Files\Fold@Home
Executable: FAH502-Console.exe
Arguments: -send all

[01:42:51] - Ask before connecting: No
[01:42:51] - Use IE connection settings: Yes
[01:42:51] - User name: ryan_975 (Team 33)
[01:42:51] - User ID: 7745EA260FC7420
[01:42:52] - Machine ID: 1
[01:42:52]
[01:42:52] Loaded queue successfully.
[01:42:52] Attempting to return result(s) to server...


[01:42:52] + Attempting to send results
[01:43:23] Couldn't send HTTP request to server (wininet)
[01:43:23] + Could not connect to Work Server (results)
[01:43:23]     (171.65.103.162:8080)
[01:43:23] - Error: Could not transmit unit 01 (completed October 2) to work ser
ver.


[01:43:23] + Attempting to send results
[01:43:59] Couldn't send HTTP request to server (wininet)
[01:43:59] + Could not connect to Work Server (results)
[01:43:59]     (171.65.103.100:8080)
[01:43:59]   Could not transmit unit 01 to Collection server; keeping in queue.
[01:43:59] - Failed to send all units to server

Folding@Home Client Shutdown.

C:\Program Files\Fold@Home>
 
huh.

.100 server is down so that's just that. It shoud redirect to the collection server at some point in time.

.162 is up, so why it's not goign there is interesting. Is this @ home or in a corperate enviroment? Anything blocking outbound traffic?

You can ping folding.stanford.edu right?

Actually, that might be the same WU trying to go to orginal server and collection server. Internet working?
 
marty9876 said:
huh.

.100 server is down so that's just that. It shoud redirect to the collection server at some point in time.

.162 is up, so why it's not goign there is interesting. Is this @ home or in a corperate enviroment? Anything blocking outbound traffic?

You can ping folding.stanford.edu right?

Actually, that might be the same WU trying to go to orginal server and collection server. Internet working?
Click to expand...

I"m at home, and yes internet is working, I'm posting from the computer that is giving the problems. My UD client is uploading just fine. I even specifically made an exception for FAH in Windows Firewall. And it seemed to upload my first WU just fine last weekend.

Just tried pinging and got this
Code: 
C:\PROGRA~1\FOLD@H~1>ping -a folding.stanford.edu

Pinging proxy3.stanford.edu [171.67.16.154] with 32 bytes of data:

Reply from 171.67.16.154: bytes=32 time=67ms TTL=43
Reply from 171.67.16.154: bytes=32 time=67ms TTL=43
Reply from 171.67.16.154: bytes=32 time=69ms TTL=43
Reply from 171.67.16.154: bytes=32 time=73ms TTL=43

Ping statistics for 171.67.16.154:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 67ms, Maximum = 73ms, Average = 69ms

C:\PROGRA~1\FOLD@H~1>


 
Did you edit the firewall after first upload?

Windows default firewall will not block out bound traffic, you really should not have had to change anything there. I wonder if your change broke things maybe?
 
marty9876 said:
Did you edit the firewall after first upload?

Windows default firewall will not block out bound traffic, you really should not have had to change anything there. I wonder if your change broke things maybe?
Click to expand...

No, I made the change after I noticed the error. It didn't make a difference.
 
this is my client.cfg file just in case it makes a difference

Code: 
C:\PROGRA~1\FOLD@H~1>type client.cfg
[settings]
username=ryan_975
team=33
asknet=no
bigpackets=yes
machineid=1

[http]
active=no
host=localhost
port=8080
usereg=yes

[core]
priority=0
cpuusage=100
disableassembly=no


C:\PROGRA~1\FOLD@H~1>
 
can you ping the addy above?

either Stanford server down, or your not getting there. Second is odd since you obviously grabbed another WU. folding.stanford.edu
 
ping result from both address in the log file

Code: 
C:\PROGRA~1\FOLD@H~1>ping 171.65.103.162

Pinging 171.65.103.162 with 32 bytes of data:

Reply from 171.65.103.162: bytes=32 time=62ms TTL=43
Reply from 171.65.103.162: bytes=32 time=73ms TTL=43
Reply from 171.65.103.162: bytes=32 time=75ms TTL=43
Reply from 171.65.103.162: bytes=32 time=66ms TTL=43

Ping statistics for 171.65.103.162:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 75ms, Average = 69ms

C:\PROGRA~1\FOLD@H~1>ping 171.65.103.100

Pinging 171.65.103.100 with 32 bytes of data:

Reply from 171.65.103.100: bytes=32 time=71ms TTL=43
Reply from 171.65.103.100: bytes=32 time=110ms TTL=43
Reply from 171.65.103.100: bytes=32 time=63ms TTL=43
Reply from 171.65.103.100: bytes=32 time=69ms TTL=43

Ping statistics for 171.65.103.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 63ms, Maximum = 110ms, Average = 78ms

C:\PROGRA~1\FOLD@H~1>
 
I might also add that I'm running Vista. But I was also running Vista when the first WU was turned in, so I don't think it makes a difference.
 
try kicking the computer?

you could try telnet out on port 8080 and see what happens. Not too good at this...

start>run>cmd

tenlet

o 171.65.103.162 8080

o=oreo (open)

let me know if you get "press any key" or could not connect error
 
ryan_975 said:
I might also add that I'm running Vista. But I was also running Vista when the first WU was turned in, so I don't think it makes a difference.
Click to expand...

well, theres your problem right there... :)
 
one server is down, but it should roll to the other. these happen form time to time but generally fix themselves.

if something in Vista firewall is blocking port 8080 outbound you can't send results back (but can get new ones)
 
Ok, just got telnet installed on here.

this is what I'm seeing

Code: 
Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> o 171.65.103.100:8080
Connecting To 171.65.103.100:8080...Could not open connection to the host, on po
rt 23: Connect failed
Microsoft Telnet> o 171.65.103.162:8080
Connecting To 171.65.103.162:8080...Could not open connection to the host, on po
rt 23: Connect failed
Microsoft Telnet> quit

C:\Program Files\Fold@Home>

This is with firewall off.
 
It seems I had some unfounded success. I have no idea what I did, or if anything I did mattered. But the work unit was submitted. and queue slot 01 is now empty.

Code: 
--- Opening Log file [October 5 04:23:12]


# Windows Console Edition #####################################################
###############################################################################

                       Folding@Home Client Version 5.02

                          [url]http://folding.stanford.edu[/url]

###############################################################################
###############################################################################

Launch directory: C:\PROGRA~1\FOLD@H~1
Executable: FAH502-Console.exe
Arguments: -send all

[04:23:12] - Ask before connecting: No
[04:23:12] - User ID: 6CFF11C3B9D8896
[04:23:12] - Machine ID: 1
[04:23:12]
[04:23:12] Loaded queue successfully.
[04:23:12] Attempting to return result(s) to server...


[04:23:12] + Attempting to send results
[04:25:18] + Results successfully sent
[04:25:18] Thank you for your contribution to Folding@Home.
[04:25:18] + Starting local stats count at 1

Folding@Home Client Shutdown.
Restarting the service and we'll see it goes from here.
Thanks for the help marty.
 
171.65.103.100 VSPMF33 pande accept Accept

server came back up, appearently it never worked going to .162

restarting the service/waiting fixes 99.9% of FAH errors.
 
marty9876 said:
171.65.103.100 VSPMF33 pande accept Accept

server came back up, appearently it never worked going to .162

restarting the service/waiting fixes 99.9% of FAH errors.
Click to expand...


you lost me on this one.
 
ryan_975 said:
you lost me on this one.
Click to expand...

looks like the server it was trying to go to, .162, is not back up.

However if a server goes down, the client is suposta dump into a collection server (not really sure which one is collection server) so it *should* have went up anyways.

Generally when I hit these types of errors, stopping the service and restarting the service fixes the problem.
 
ah gotcha.

I finished another WU last night and it seems to have uploaded just fine, so maybe I won't have too many problem form here on out, and if I do I'll just do as you said, restart the service.

Now if my score would just be updated to show my 3 WUs and however point I have now.

 
ryan_975 said:
ah gotcha.

I finished another WU last night and it seems to have uploaded just fine, so maybe I won't have too many problem form here on out, and if I do I'll just do as you said, restart the service.

Now if my score would just be updated to show my 3 WUs and however point I have now.

Click to expand...

hf.com/EOC updates every 3 hours. Offical updates ever 1 hour
 
I just noticed that my FAH is doing the same thing, and I have 18 WUs backed up :( Nothing I do will make them go though :( Any advice?



 
saturnine2 said:
I just noticed that my FAH is doing the same thing, and I have 18 WUs backed up :( Nothing I do will make them go though :( Any advice?



Click to expand...

reboot?

I have submitted 4 work unit and none of them are showing up on my stats page on the main folding@home site.




 
ryan_975 said:
reboot?
Click to expand...
Already tried that, among many other things before getting fed up and browsing here :)

I have two other machines here folding, and they are both sending out WUs just fine.



 
saturnine2 said:
Already tried that, among many other things before getting fed up and browsing here :)

I have two other machines here folding, and they are both sending out WUs just fine.



Click to expand...

hmm, don't know what to tell ya then. I don't even know how mine got fixed, it just started working again. Marty had said something about restarting the service sometimes clears up rogue problems like this, but I didn't have my service running for a while before it finally connected.
 
You must log in or register to reply here.
Back
Top