• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Lagouste & F@H working right?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
GIXXERGUY6

GIXXERGUY6

Member
​
Joined
Nov 18, 2008
Location
Northwest Ohio
I can't log on the folding forums to post up, but something doesn't work right(unless that is how it's supposed to work)

LAGOUSTE
Code: 
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\THEBEAST>cd"\
'cd"\' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\THEBEAST>cd\ dist\win32\
The system cannot find the path specified.

C:\Users\THEBEAST>cd\fold\langouste3
The system cannot find the path specified.

C:\Users\THEBEAST>cd\fold

C:\FOLD>dir
 Volume in drive C has no label.
 Volume Serial Number is BAC2-5CF6

 Directory of C:\FOLD

01/25/2011  09:50 AM    <DIR>          .
01/25/2011  09:50 AM    <DIR>          ..
03/12/2010  11:30 AM    <DIR>          CoreTemp64
01/25/2011  09:52 AM    <DIR>          CPU
04/03/2010  03:10 AM             3,497 cpu-3gpu's.hfm
03/12/2010  11:30 AM    <DIR>          CPUZ
01/25/2011  01:57 AM    <DIR>          GPU 0
01/25/2011  01:57 AM    <DIR>          GPU 1
01/25/2011  08:12 AM             6,002 HFM Config 7 workers.hfm
01/25/2011  09:50 AM    <DIR>          langouste
03/12/2010  10:39 PM    <DIR>          Prime95
03/12/2010  11:38 AM    <DIR>          Realtemp
01/16/2011  07:43 PM    <DIR>          todd netbook
03/12/2010  11:40 AM    <DIR>          trayit_4_6_5_5
               2 File(s)          9,499 bytes
              12 Dir(s)  585,357,373,440 bytes free

C:\FOLD>cd\fold\langouste

C:\FOLD\langouste>cd\fold\langouste\dist\win32

C:\FOLD\langouste\dist\win32>langouste3-0.15.6.exe -1 8880
langouste3-0.15.6.exe: invalid option -- 1
Usage:
        langouste3-0.15.6.exe -l <port> [-v] [-L <logfile>] [-r <rate>] [-x] [-d
] [-C]
        langouste3-0.15.6.exe -h
        langouste3-0.15.6.exe -V

Regular options:
        -l <port>       listen on <port>
        -v              increase log verbosity; can be specified multiple times
        -L <logfile>    write log to <logfile>
        -r <rate>       limit upload data transfer rate to <rate> bytes
                        per second
        -h              display this help and exit
        -V              output version information and exit
Expert options:
        -x              drop connections related to receiving new WU
        -d              be dumb
        -C              do not perform sanity checks

C:\FOLD\langouste\dist\win32>langouste3-0.15.6.exe -l 8880
Tue Jan 25 09:59:18 2011 Langouste3 0.15.6 (compiled Mon Aug 30 11:01:54 MDT 201
0 by kszysiu@tentacle)
Tue Jan 25 09:59:18 2011 Langouste3 comes with ABSOLUTELY NO WARRANTY; for detai
ls
Tue Jan 25 09:59:18 2011 see `COPYING.txt' file located in source directory
Tue Jan 25 09:59:18 2011 Default Langouste helper temp directory: C:\Users\THEBE
AST\AppData\Local\Temp\langouste-THEBEAST\
Tue Jan 25 09:59:18 2011 Listening on 127.0.0.1:8880
Tue Jan 25 10:08:01 2011 Signal 2 received
Tue Jan 25 10:08:01 2011 Listen socket closed.
Tue Jan 25 10:08:01 2011 No more active connections. Exiting.
Tue Jan 25 10:08:01 2011 Bye.

C:\FOLD\langouste\dist\win32>langouste3-0.15.6.exe -l 8880 -r 256000
Tue Jan 25 10:08:58 2011 Langouste3 0.15.6 (compiled Mon Aug 30 11:01:54 MDT 201
0 by kszysiu@tentacle)
Tue Jan 25 10:08:58 2011 Langouste3 comes with ABSOLUTELY NO WARRANTY; for detai
ls
Tue Jan 25 10:08:58 2011 see `COPYING.txt' file located in source directory
Tue Jan 25 10:08:58 2011 Default Langouste helper temp directory: C:\Users\THEBE
AST\AppData\Local\Temp\langouste-THEBEAST\
Tue Jan 25 10:08:58 2011 Ratelimit: Output rate: 256000 bytes/s (250.00 kBps)
Tue Jan 25 10:08:58 2011 Listening on 127.0.0.1:8880
Wed Jan 26 08:11:57 2011 Accepted connection from: 127.0.0.1:52022
Wed Jan 26 08:11:57 2011 PID for socket: 7244
Wed Jan 26 08:11:57 2011 PID 7244: issending: 0
Wed Jan 26 08:11:57 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:11:57 2011 ===> Helper pid: -1
Wed Jan 26 08:11:57 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:11:57 2011 ===> now: 1296047517, last helper launched at: 0
Wed Jan 26 08:11:57 2011 ===> Launching helper: 'C:\FOLD\CPU\langouste-helper.ba
t' (exe name: 'C:\FOLD\CPU\FAH_CPU.exe')...
Wed Jan 26 08:11:57 2011 ===> Forked 0x000088
Wed Jan 26 08:11:57 2011 (0) Local: received 125 bytes, sent 0 bytes
Wed Jan 26 08:11:57 2011 Accepted connection from: 127.0.0.1:52023
Wed Jan 26 08:11:57 2011 PID for socket: 7244
Wed Jan 26 08:11:57 2011 PID 7244: issending: 0
Wed Jan 26 08:11:57 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:11:57 2011 ===> Helper pid: -1
Wed Jan 26 08:11:57 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:11:57 2011 ===> now: 1296047517, last helper launched at: 12960475
17
Wed Jan 26 08:11:57 2011 ===> WARNING: can only launch one helper in 2 minutes (
per client)
Wed Jan 26 08:11:57 2011 (0) Local: received 121 bytes, sent 0 bytes
Wed Jan 26 08:11:57 2011 Accepted connection from: 127.0.0.1:52024
Wed Jan 26 08:11:57 2011 PID for socket: 7244
Wed Jan 26 08:11:57 2011 PID 7244: issending: 0
Wed Jan 26 08:11:57 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:11:57 2011 ===> Helper pid: -1
Wed Jan 26 08:11:57 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:11:57 2011 ===> now: 1296047517, last helper launched at: 12960475
17
Wed Jan 26 08:11:57 2011 ===> WARNING: can only launch one helper in 2 minutes (
per client)
Wed Jan 26 08:11:57 2011 (0) Local: received 125 bytes, sent 0 bytes
Wed Jan 26 08:11:57 2011 Accepted connection from: 127.0.0.1:52025
Wed Jan 26 08:11:57 2011 PID for socket: 7244
Wed Jan 26 08:11:57 2011 PID 7244: issending: 0
Wed Jan 26 08:11:57 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:11:57 2011 ===> Helper pid: -1
Wed Jan 26 08:11:57 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:11:57 2011 ===> now: 1296047517, last helper launched at: 12960475
17
Wed Jan 26 08:11:57 2011 ===> WARNING: can only launch one helper in 2 minutes (
per client)
Wed Jan 26 08:11:57 2011 (0) Local: received 121 bytes, sent 0 bytes
Wed Jan 26 08:11:57 2011 Accepted connection from: 127.0.0.1:52026
Wed Jan 26 08:11:57 2011 PID for socket: 7244
Wed Jan 26 08:11:57 2011 PID 7244: issending: 0
Wed Jan 26 08:11:57 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:11:57 2011 ===> Helper pid: -1
Wed Jan 26 08:11:57 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:11:57 2011 ===> now: 1296047517, last helper launched at: 12960475
17
Wed Jan 26 08:11:57 2011 ===> WARNING: can only launch one helper in 2 minutes (
per client)
Wed Jan 26 08:11:57 2011 (0) Local: received 125 bytes, sent 0 bytes
Wed Jan 26 08:11:57 2011 Accepted connection from: 127.0.0.1:52027
Wed Jan 26 08:11:57 2011 PID for socket: 7244
Wed Jan 26 08:11:57 2011 PID 7244: issending: 0
Wed Jan 26 08:11:57 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:11:57 2011 ===> Helper pid: -1
Wed Jan 26 08:11:57 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:11:57 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:11:57 2011 ===> now: 1296047517, last helper launched at: 12960475
17
Wed Jan 26 08:11:57 2011 ===> WARNING: can only launch one helper in 2 minutes (
per client)
Wed Jan 26 08:11:57 2011 (0) Local: received 121 bytes, sent 0 bytes
23 File(s) copied
launching asynchronous part
Wed Jan 26 08:12:15 2011 Accepted connection from: 127.0.0.1:52028
Wed Jan 26 08:12:15 2011 PID for socket: 7244
Wed Jan 26 08:12:15 2011 PID 7244: issending: 0
Wed Jan 26 08:12:15 2011 ===> PID 7244 is contacting main assignment server
Wed Jan 26 08:12:15 2011 (0) resolving 'assign.stanford.edu:8080'
Wed Jan 26 08:12:15 2011 (0) Connecting to: 171.67.108.200:8080
Wed Jan 26 08:12:15 2011 (0) Connected.
Wed Jan 26 08:12:15 2011 (0) Local connection closed (bsize: 0).
Wed Jan 26 08:12:15 2011 (0) Local: received 559 bytes, sent 396 bytes
Wed Jan 26 08:12:15 2011 (0) Remote: received 396 bytes, sent 559 bytes
Wed Jan 26 08:12:15 2011 Accepted connection from: 127.0.0.1:52030
Wed Jan 26 08:12:15 2011 PID for socket: 7244
Wed Jan 26 08:12:15 2011 PID 7244: issending: 0
Wed Jan 26 08:12:15 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 512
Wed Jan 26 08:12:15 2011 (0) resolving '130.237.232.141:8080'
Wed Jan 26 08:12:15 2011 (0) Connecting to: 130.237.232.141:8080
Wed Jan 26 08:12:15 2011 (0) Connected.
Wed Jan 26 08:13:09 2011 Accepted connection from: 127.0.0.1:52040
Wed Jan 26 08:13:09 2011 PID for socket: 9372
Wed Jan 26 08:13:09 2011 PID 9372: issending: 1
Wed Jan 26 08:13:09 2011 (1) resolving '130.237.232.141:8080'
Wed Jan 26 08:13:09 2011 (1) Connecting to: 130.237.232.141:8080
Wed Jan 26 08:13:09 2011 (1) Connected.
Wed Jan 26 08:14:02 2011 (0) Local connection closed (bsize: 0).
Wed Jan 26 08:14:02 2011 (0) Local: received 631 bytes, sent 24870954 bytes
Wed Jan 26 08:14:02 2011 (0) Remote: received 24870954 bytes, sent 631 bytes
Wed Jan 26 08:14:02 2011 Accepted connection from: 127.0.0.1:52047
Wed Jan 26 08:14:02 2011 PID for socket: 7244
Wed Jan 26 08:14:02 2011 PID 7244: issending: 0
Wed Jan 26 08:14:02 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:14:02 2011 ===> Helper pid: 9372
Wed Jan 26 08:14:02 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:14:02 2011 ===> Helper (pid 9372) already running
Wed Jan 26 08:14:02 2011 ===> If you're sure that's not the case, please remove
C:\Users\THEBEAST\AppData\Local\Temp\fah\f1
Wed Jan 26 08:14:02 2011 (0) Local: received 125 bytes, sent 0 bytes
Wed Jan 26 08:14:02 2011 Accepted connection from: 127.0.0.1:52048
Wed Jan 26 08:14:02 2011 PID for socket: 7244
Wed Jan 26 08:14:02 2011 PID 7244: issending: 0
Wed Jan 26 08:14:02 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:14:02 2011 ===> Helper pid: 9372
Wed Jan 26 08:14:02 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:14:02 2011 ===> Helper (pid 9372) already running
Wed Jan 26 08:14:02 2011 ===> If you're sure that's not the case, please remove
C:\Users\THEBEAST\AppData\Local\Temp\fah\f1
Wed Jan 26 08:14:02 2011 (0) Local: received 121 bytes, sent 0 bytes
Wed Jan 26 08:14:02 2011 Accepted connection from: 127.0.0.1:52049
Wed Jan 26 08:14:02 2011 PID for socket: 7244
Wed Jan 26 08:14:02 2011 PID 7244: issending: 0
Wed Jan 26 08:14:02 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:14:02 2011 ===> Helper pid: 9372
Wed Jan 26 08:14:02 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:14:02 2011 ===> Helper (pid 9372) already running
Wed Jan 26 08:14:02 2011 ===> If you're sure that's not the case, please remove
C:\Users\THEBEAST\AppData\Local\Temp\fah\f1
Wed Jan 26 08:14:02 2011 (0) Local: received 125 bytes, sent 0 bytes
Wed Jan 26 08:14:02 2011 Accepted connection from: 127.0.0.1:52050
Wed Jan 26 08:14:02 2011 PID for socket: 7244
Wed Jan 26 08:14:02 2011 PID 7244: issending: 0
Wed Jan 26 08:14:02 2011 ===> PID 7244 is (most likely) contacting WU server, co
ntent length: 100198447
Wed Jan 26 08:14:02 2011 ===> Helper pid: 9372
Wed Jan 26 08:14:02 2011 FahCore_15.exe (PID 10728) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 FahCore_11.exe (PID 10992) appears to belong to another
 client, continuing.
Wed Jan 26 08:14:02 2011 ===> PID 7244: numcores: 0
Wed Jan 26 08:14:02 2011 ===> Helper (pid 9372) already running
Wed Jan 26 08:14:02 2011 ===> If you're sure that's not the case, please remove
C:\Users\THEBEAST\AppData\Local\Temp\fah\f1
Wed Jan 26 08:14:02 2011 (0) Local: received 121 bytes, sent 0 bytes
Wed Jan 26 08:32:26 2011 (1) Local connection closed (bsize: 0).
Wed Jan 26 08:32:26 2011 (1) Local: received 100198572 bytes, sent 636 bytes
Wed Jan 26 08:32:26 2011 (1) Remote: received 636 bytes, sent 100198572 bytes
Wed Jan 26 08:32:26 2011 (1) Ratelimit: sent 100198572 byte(s) in 1156.835 secon
ds, 86614 Bps (84.58 kBps)


FOLDING
Code: 
[03:47:24] Completed 212500 out of 250000 steps  (85%)
[04:26:29] Completed 215000 out of 250000 steps  (86%)
[05:05:30] Completed 217500 out of 250000 steps  (87%)
[05:43:35] Completed 220000 out of 250000 steps  (88%)
[06:21:20] Completed 222500 out of 250000 steps  (89%)
[06:57:36] Completed 225000 out of 250000 steps  (90%)
[07:34:21] Completed 227500 out of 250000 steps  (91%)
[08:14:52] Completed 230000 out of 250000 steps  (92%)
[08:50:34] Completed 232500 out of 250000 steps  (93%)
[09:09:15] - Autosending finished units... [January 26 09:09:15 UTC]
[09:09:15] Trying to send all finished work units
[09:09:15] + No unsent completed units remaining.
[09:09:15] - Autosend completed
[09:26:38] Completed 235000 out of 250000 steps  (94%)
[10:03:12] Completed 237500 out of 250000 steps  (95%)
[10:40:48] Completed 240000 out of 250000 steps  (96%)
[11:18:19] Completed 242500 out of 250000 steps  (97%)
[11:55:55] Completed 245000 out of 250000 steps  (98%)
[12:33:28] Completed 247500 out of 250000 steps  (99%)
[13:11:02] Completed 250000 out of 250000 steps  (100%)
[13:11:17] DynamicWrapper: Finished Work Unit: sleep=10000
[13:11:27]
[13:11:27] Finished Work Unit:
[13:11:27] - Reading up to 52713120 from "work/wudata_07.trr": Read 52713120
[13:11:28] trr file hash check passed.
[13:11:28] - Reading up to 47105148 from "work/wudata_07.xtc": Read 47105148
[13:11:28] xtc file hash check passed.
[13:11:28] edr file hash check passed.
[13:11:28] logfile size: 211727
[13:11:28] Leaving Run
[13:11:31] - Writing 100197935 bytes of core data to disk...
[13:11:33]   ... Done.
[13:11:52] - Shutting down core
[13:11:52]
[13:11:52] Folding@home Core Shutdown: FINISHED_UNIT
[13:11:57] CoreStatus = 64 (100)
[13:11:57] Unit 7 finished with 57 percent of time to deadline remaining.
[13:11:57] Updated performance fraction: 0.664738
[13:11:57] Sending work to server
[13:11:57] Project: 6900 (Run 4, Clone 23, Gen 20)


[13:11:57] + Attempting to send results [January 26 13:11:57 UTC]
[13:11:57] - Reading file work/wuresults_07.dat from core
[13:11:57]   (Read 100197935 bytes from disk)
[13:11:57] Connecting to http://130.237.232.141:8080/
[13:11:57] - Couldn't send HTTP request to server
[13:11:57] + Could not connect to Work Server (results)
[13:11:57]     (130.237.232.141:8080)
[13:11:57] + Retrying using alternative port
[13:11:57] Connecting to http://130.237.232.141:80/
[13:11:57] - Couldn't send HTTP request to server
[13:11:57] + Could not connect to Work Server (results)
[13:11:57]     (130.237.232.141:80)
[13:11:57] - Error: Could not transmit unit 07 (completed January 26) to work se
rver.
[13:11:57] - 1 failed uploads of this unit.
[13:11:57]   Keeping unit 07 in queue.
[13:11:57] Trying to send all finished work units
[13:11:57] Project: 6900 (Run 4, Clone 23, Gen 20)


[13:11:57] + Attempting to send results [January 26 13:11:57 UTC]
[13:11:57] - Reading file work/wuresults_07.dat from core
[13:11:57]   (Read 100197935 bytes from disk)
[13:11:57] Connecting to http://130.237.232.141:8080/
[13:11:57] - Couldn't send HTTP request to server
[13:11:57] + Could not connect to Work Server (results)
[13:11:57]     (130.237.232.141:8080)
[13:11:57] + Retrying using alternative port
[13:11:57] Connecting to http://130.237.232.141:80/
[13:11:57] - Couldn't send HTTP request to server
[13:11:57] + Could not connect to Work Server (results)
[13:11:57]     (130.237.232.141:80)
[13:11:57] - Error: Could not transmit unit 07 (completed January 26) to work se
rver.
[13:11:57] - 2 failed uploads of this unit.


[13:11:57] + Attempting to send results [January 26 13:11:57 UTC]
[13:11:57] - Reading file work/wuresults_07.dat from core
[13:11:57]   (Read 100197935 bytes from disk)
[13:11:57] Connecting to http://130.237.165.141:8080/
[13:11:57] - Couldn't send HTTP request to server
[13:11:57] + Could not connect to Work Server (results)
[13:11:57]     (130.237.165.141:8080)
[13:11:57] + Retrying using alternative port
[13:11:57] Connecting to http://130.237.165.141:80/
[13:11:57] - Couldn't send HTTP request to server
[13:11:57] + Could not connect to Work Server (results)
[13:11:57]     (130.237.165.141:80)
[13:11:58]   Could not transmit unit 07 to Collection server; keeping in queue.
[13:11:58] + Sent 0 of 1 completed units to the server
[13:11:58] - Preparing to get new work unit...
[13:11:58] Cleaning up work directory
[13:12:15] + Attempting to get work packet
[13:12:15] Passkey found
[13:12:15] - Will indicate memory of 6135 MB
[13:12:15] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5

[13:12:15] - Connecting to assignment server
[13:12:15] Connecting to http://assign.stanford.edu:8080/
[13:12:15] Posted data.
[13:12:15] Initial: ED82; - Successful: assigned to (130.237.232.141).
[13:12:15] + News From Folding@Home: Welcome to Folding@Home
[13:12:15] Loaded queue successfully.
[13:12:15] Sent data
[13:12:15] Connecting to http://130.237.232.141:8080/
[13:12:23] Posted data.
[13:12:23] Initial: 0000; - Receiving payload (expected size: 24870300)
[13:14:02] - Downloaded at ~245 kB/s
[13:14:02] - Averaged speed for that direction ~553 kB/s
[13:14:02] + Received work.
[13:14:02] Trying to send all finished work units
[13:14:02] Project: 6900 (Run 4, Clone 23, Gen 20)


[13:14:02] + Attempting to send results [January 26 13:14:02 UTC]
[13:14:02] - Reading file work/wuresults_07.dat from core
[13:14:02]   (Read 100197935 bytes from disk)
[13:14:02] Connecting to http://130.237.232.141:8080/
[13:14:02] - Couldn't send HTTP request to server
[13:14:02] + Could not connect to Work Server (results)
[13:14:02]     (130.237.232.141:8080)
[13:14:02] + Retrying using alternative port
[13:14:02] Connecting to http://130.237.232.141:80/
[13:14:02] - Couldn't send HTTP request to server
[13:14:02] + Could not connect to Work Server (results)
[13:14:02]     (130.237.232.141:80)
[13:14:02] - Error: Could not transmit unit 07 (completed January 26) to work se
rver.
[13:14:02] - 3 failed uploads of this unit.


[13:14:02] + Attempting to send results [January 26 13:14:02 UTC]
[13:14:02] - Reading file work/wuresults_07.dat from core
[13:14:02]   (Read 100197935 bytes from disk)
[13:14:02] Connecting to http://130.237.165.141:8080/
[13:14:02] - Couldn't send HTTP request to server
[13:14:02] + Could not connect to Work Server (results)
[13:14:02]     (130.237.165.141:8080)
[13:14:02] + Retrying using alternative port
[13:14:02] Connecting to http://130.237.165.141:80/
[13:14:02] - Couldn't send HTTP request to server
[13:14:02] + Could not connect to Work Server (results)
[13:14:02]     (130.237.165.141:80)
[13:14:02]   Could not transmit unit 07 to Collection server; keeping in queue.
[13:14:02] + Sent 0 of 1 completed units to the server
[13:14:02] + Closed connections
[13:14:02]
[13:14:02] + Processing work unit
[13:14:02] Core required: FahCore_a3.exe
[13:14:02] Core found.
[13:14:02] Working on queue slot 08 [January 26 13:14:02 UTC]
[13:14:02] + Working ...
[13:14:02] - Calling '.\FahCore_a3.exe -dir work/ -nice 19 -suffix 08 -np 8 -che
ckpoint 15 -verbose -lifeline 7244 -version 630'

[13:14:02]
[13:14:02] *------------------------------*
[13:14:02] Folding@Home Gromacs SMP Core
[13:14:02] Version 2.22 (Mar 12, 2010)
[13:14:02]
[13:14:02] Preparing to commence simulation
[13:14:02] - Looking at optimizations...
[13:14:02] - Created dyn
[13:14:02] - Files status OK
[13:14:06] - Expanded 24869788 -> 30796293 (decompressed 123.8 percent)
[13:14:06] Called DecompressByteArray: compressed_data_size=24869788 data_size=3
0796293, decompressed_data_size=30796293 diff=0
[13:14:07] - Digital signature verified
[13:14:07]
[13:14:07] Project: 6900 (Run 11, Clone 10, Gen 24)
[13:14:07]
[13:14:07] Assembly optimizations on if available.
[13:14:07] Entering M.D.
[13:14:15] Completed 0 out of 250000 steps  (0%)
[13:52:05] Completed 2500 out of 250000 steps  (1%)
 
There should be a langouste directory with another FAHlog.txt in it that shows the upload of the WU.
 
ChasR said:
There should be a langouste directory with another FAHlog.txt in it that shows the upload of the WU.
Click to expand...

Ok I'll look at it. It uploaded my stats updated woot woot I did something right for once without needed a hand held :D Aren't you proud of my F@H daddy :D

I do have one question though. Can I use this for GPU's? or does it only work or benefit the best with the CPU's since they are so large?
 
Last edited:
Langouste was developed for FAHCore_a2 -bigadv WUs. They would sometimes take an hour or more to wrap up and write to disk at completion and then take a long time to upload. With todays a3 WUs it doesn't take nearly so much time to wrap up and send WUs.
In checking my Langouste machine, It takes it 6 minutes to wrap up, transfer to langouste, and restart a new p6701. THat is actually longer than the shortest time my non langouste machines take. THe client wastes several minutes trying to transmit the WU langouste transferred out of the Work directory. I haven't checked -bigadv times effects. Non p6701 WUs all wrap up and send in less time without Langouste than with it. GPU Wus are so small, Langouste may actually slow down their close, upload and download cycle times. It appears to me that Langouste is only worthwhile to people on SLOW internet connections. After checking mine, I'm going to disable it to rid myself of the garbage log messages.
 
ChasR said:
Langouste was developed for FAHCore_a2 -bigadv WUs. They would sometimes take an hour or more to wrap up and write to disk at completion and then take a long time to upload. With todays a3 WUs it doesn't take nearly so much time to wrap up and send WUs.
In checking my Langouste machine, It takes it 6 minutes to wrap up, transfer to langouste, and restart a new p6701. THat is actually longer than the shortest time my non langouste machines take. THe client wastes several minutes trying to transmit the WU langouste transferred out of the Work directory. I haven't checked -bigadv times effects. Non p6701 WUs all wrap up and send in less time without Langouste than with it. GPU Wus are so small, Langouste may actually slow down their close, upload and download cycle times. It appears to me that Langouste is only worthwhile to people on SLOW internet connections. After checking mine, I'm going to disable it to rid myself of the garbage log messages.
Click to expand...

I'm mainly using it because I am set the upload rate(which is good when having 1 or more potential WU's uploading and trying to play xbox live at the same time)
 
ChasR said:
I can see that. My soon to be Airman, XBOX playing son,would approve as well.
Click to expand...

Hey Chas since you have used it before I have a question for you.

I restarted the pc. Do I have to start lagouste again? my FAH isn't finding work and I believe it's because lagouste isn't working.
 
I've never used it in Windows. In Linux, I start langouste before FAH in the same script, so yes, I restart it when starting FAH.
 
I went ahead and checked my upload time with -bigadv. It looks like it takes about 4 minutes to upload the finished WU.

I guess I wouldn't really see any benefit from running Lagouste, right?
 
torin3 said:
I went ahead and checked my upload time with -bigadv. It looks like it takes about 4 minutes to upload the finished WU.

I guess I wouldn't really see any benefit from running Lagouste, right?
Click to expand...

Yeah 4 minutes at what upload speed?

I have 768 and it takes about 10 minutes for the internet to get back to normal while I'm playing xbox...It's really annoying(can't exactly stop playing in the middle of a match either)
 
You must log in or register to reply here.

Similar threads

Kenrou
Radeon RX 6500XT vs. New AAA Games, Just How Bad Is It?
Replies
1
Views
247
Woomack
W
dfonda
Gen 2 with RTX 3080 log for TPF info.
Replies
2
Views
955
dfonda
dfonda
FoldingAddict
Hung with no error
Replies
18
Views
777
Holdolin
Holdolin
Zerileous
PPD problem
Replies
3
Views
877
Zerileous
Zerileous
harlam357
WU_STALLED
Replies
3
Views
1K
WhitehawkEQ
WhitehawkEQ
Back