Problems With The Client

[DodgeViper]

I have been folding for some time now without a problem. Went to few my log and no text was avaliable, nothing but zero's. I have download a new client and removed anything to do with FAH on my system. I donwloaded a new text version and all I am getting is a error message. I am at Getwork #22 now. Whats up?

My firewall is turned off......

 

[NASsoccer]

hey there, are you still getting this error? a lot of server have been and or are rejecting right now and no real word why this is. An AS server has also been offline a lot lately too!

FOLD ON
NAS

 

[DodgeViper]

This is what was going on yesterday. It would send before the W/U was finished and then pickup again and send a small section. This continued all day. My system runs 24/7 and connected to a cable modem 24/7.

[00:03:25] Finished a frame (93)
[00:11:44] Finished a frame (94)

+ Attempting to send results
- Connecting to server (171.64.122.109:8080)
+ Results successfully sent
+ Starting local stats count at 1
[00:20:04] Finished a frame (95)
[00:28:50] Finished a frame (96)
[00:37:36] Finished a frame (97)
[00:46:42] Finished a frame (98)
[00:55:41] Finished a frame (99)
[01:04:43] Finished a frame (100)
[01:04:43] TINKER is Exiting following Normal Termination
[01:04:43]
[01:04:43] Finished Work Unit:
[01:04:43] ARC file integrity verified
[01:04:43] logfile size: 20480
[01:04:43] Leaving Run
[01:04:47] - Writing 156344 bytes of core data to disk.
[01:04:47] end (WriteWorkResults)
[01:04:47] - Shutting down core
[01:04:47]
[01:04:47] [email protected] Core Shutdown: FINISHED_UNIT
CoreStatus = 64 (100)
Sending work to server

+ Attempting to send results
- Connecting to server (171.64.122.112:8080)
+ Results successfully sent
+ Number of Units Completed: 2
+ Attempting to get work packet
- Connecting to assignment server
- Could not send request to AS #2
- Successful: assigned to (171.64.122.119).
+ News From [email protected]: Welcome to [email protected]
- Connecting to server (171.64.122.119) on port 80

 

[res0r9lm]

This is what was going on yesterday. It would send before the W/U was finished and then pickup again and send a small section. This continued all day. My system runs 24/7 and connected to a cable modem 24/7.

[00:03:25] Finished a frame (93)
[00:11:44] Finished a frame (94)

+ Attempting to send results
- Connecting to server (171.64.122.109:8080)
+ Results successfully sent
+ Starting local stats count at 1
[00:20:04] Finished a frame (95)
[00:28:50] Finished a frame (96)
[00:37:36] Finished a frame (97)
[00:46:42] Finished a frame (98)
[00:55:41] Finished a frame (99)
[01:04:43] Finished a frame (100)
[01:04:43] TINKER is Exiting following Normal Termination
[01:04:43]
[01:04:43] Finished Work Unit:
[01:04:43] ARC file integrity verified
[01:04:43] logfile size: 20480
[01:04:43] Leaving Run
[01:04:47] - Writing 156344 bytes of core data to disk.
[01:04:47] end (WriteWorkResults)
[01:04:47] - Shutting down core
[01:04:47]
[01:04:47] [email protected] Core Shutdown: FINISHED_UNIT
CoreStatus = 64 (100)
Sending work to server

+ Attempting to send results
- Connecting to server (171.64.122.112:8080)
+ Results successfully sent
+ Number of Units Completed: 2
+ Attempting to get work packet
- Connecting to assignment server
- Could not send request to AS #2
- Successful: assigned to (171.64.122.119).
+ News From [email protected]: Welcome to [email protected]
- Connecting to server (171.64.122.119) on port 80

Thats normal. It is the auto-send feature... I think it doesn't really send anything if you don't have a wu in your queue it just says it did.

 

[Tinker32]

I'm not sure if this is what NASsoccer was mentioning but around 4:30pm (EST) one of my folders was having major problems trying to download a new WU. Did Google eat them all?