Search found 19 matches
- Sat Jul 23, 2016 5:14 pm
- Forum: Issues with a specific server
- Topic: Failed to connect to 171.64.65.104:80
- Replies: 70
- Views: 22886
Re: Failed to connect to 171.64.65.104:80
Feeling similar pain and frustration here. Noticed yesterday that the number of attempts field rolls over in the low triple digits, caught it going from 103 to 11 over the course of a few hours. WU has been done for a week. Bandwidth wasted. Points bleeding away. will be automatically discarded in t...
- Wed Jul 20, 2016 7:36 pm
- Forum: Issues with a specific server
- Topic: Failed to connect to 171.64.65.104:80
- Replies: 70
- Views: 22886
Re: Failed to connect to 171.64.65.104:80
The current log entries are here - http://fah-web.stanford.edu/pybeta/logs ... 0.log.html, you can get there by connecting from the Server Status page. OK, so I'm looking at the correct link (Thanks Joe_H) with lines like: Wed Jul 20 12:00:17 PDT 2016 171.65.103.160 VSPMF93 - classic accept Accepti...
- Wed Jul 20, 2016 12:42 pm
- Forum: Issues with a specific server
- Topic: Failed to connect to 171.64.65.104:80
- Replies: 70
- Views: 22886
Re: Failed to connect to 171.64.65.104:80
Four days (94 attempts) of "PLEASE_WAIT" active refusals here. . . 05:50:18:WU01:FS01:Upload complete 05:50:18:WU01:FS01:Server responded PLEASE_WAIT (464) 05:50:18:WARNING:WU01:FS01:Failed to send results, will try again later 05:50:18:WU01:FS01:Sending unit results: id:01 state:SEND erro...
- Mon Jul 18, 2016 3:05 pm
- Forum: Issues with a specific server
- Topic: Failed to connect to 171.64.65.104:80
- Replies: 70
- Views: 22886
Re: Failed to connect to 171.64.65.104:80
I'd be annoyed, too, but Stanford has never had very good coverage on weekends. I don't know how many problems I've seen that were fixed on a Monday morning. I do see a lot of servers which have a status of either DOWN or Reject. The Collection Servers can only recover a certain percentage of WUs a...
- Tue Apr 08, 2014 12:08 am
- Forum: GPU Projects and FahCores
- Topic: Project 8018 Core 15 so low PPD why?
- Replies: 18
- Views: 13212
Re: Project 8018 Core 15 so low PPD why?
Plus one here . . . 8018 on Fermi: Huge effort + tiny points => waste of time. 111% electricity for 1/4th the points per day. Hope they work well for some other hardware, there sure are a LOT of them. I'd like them better if they made more points instead of less. :)
- Fri Mar 21, 2014 6:43 pm
- Forum: Problems with NVidia drivers
- Topic: 9401 fails on GM107 but not GK106 {Hopefully fixed}
- Replies: 160
- Views: 56677
Re: 9401 fails on 750ti
Anyone with a 750 (Ti) could temporarily install the v6 GPU client, as it cannot get core 17 projects and would therefore only get core 15. Thanks for the info. I personally wouldn't want to do that. Unfortunately I kind of doubt most people will either. Hopefully they can fix core 17 soon. FAH GPU...
- Sat Mar 15, 2014 2:48 am
- Forum: Problems with NVidia drivers
- Topic: 9401 fails on GM107 but not GK106 {Hopefully fixed}
- Replies: 160
- Views: 56677
Re: 9401 fails on 750ti
I think this proves that there is a need for a CUDA flag, and/or assignment server tweaks for this card. Seems the CUDA core was written well enough to keep working with new CUDA hardware. OpenCL in Fahcore_17 does not appear to be the same. . . . If that is unclear there, ask here! My lack of clari...
- Sat Mar 15, 2014 2:30 am
- Forum: Problems with NVidia drivers
- Topic: 9401 fails on GM107 but not GK106 {Hopefully fixed}
- Replies: 160
- Views: 56677
Re: 9401 fails on 750ti
. . .have to test it ... so it would have to be whitelisted. The need for development is clear, hopefully they have their own lists. I thought the point of the public whitelist was to identify supported hardware. Is there some other list that tells which cards "just work"??? Perhaps there...
- Fri Mar 14, 2014 9:53 pm
- Forum: Problems with NVidia drivers
- Topic: 9401 fails on GM107 but not GK106 {Hopefully fixed}
- Replies: 160
- Views: 56677
Re: 9401 fails on 750ti
First, thanks for the quick response, I always find good help here.
0x10de:0x1380:2:4:GM107 [GeForce GTX 750 Ti]
In light of the above, why is 750ti in the whitelist???bruce wrote: The Pande Group is aware of the fact that Maxwell is not yet supported, but there's no ETA for a fix.
[/code]
0x10de:0x1380:2:4:GM107 [GeForce GTX 750 Ti]
- Fri Mar 14, 2014 8:02 pm
- Forum: Problems with NVidia drivers
- Topic: 9401 fails on GM107 but not GK106 {Hopefully fixed}
- Replies: 160
- Views: 56677
Re: 9401 fails on 750ti plus one here
For me, Maxwell hardware GTX750ti FTW Does NOT fold on v7. (with or without client-type advanced. "Runs" for several minutes before failing. No steps complete. same same behavior when heavily underclocked) Good temps. Even overclocking (100% power target on precision) it tests ok: Explicit...
- Mon Apr 16, 2012 7:17 pm
- Forum: Issues with a specific server
- Topic: 130.237.232.237 going down for maintenance
- Replies: 58
- Views: 19402
Re: Failed uploads: 9 cannot ping 130.237.232.237:8080
im having the same issue with the same server. it sits there attempting to connect for 2 hours then pings out at its max time. tofu did yours finally send? Nope, it's still here (240 tries currently). My network is fast. The machine turns in four smp units a day. The initial stuck WU (slot #5) is s...
- Sun Apr 08, 2012 12:22 am
- Forum: 3rd party contributed software
- Topic: Langouste -- WU upload/download de-coupler (+upload capping)
- Replies: 173
- Views: 149918
Re: Langouste -- WU upload/download de-coupler (+upload capp
It looks like I MIGHT need to research BIOS && OS settings: :oops: tofuwombat@schnellzug:~$ uname -a Linux schnellzug 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linux tofuwombat@schnellzug:~$ dmesg | grep RAM [ 0.000000] BIOS-provided physical RAM map: [ 0.00000...
- Sat Apr 07, 2012 7:33 pm
- Forum: 3rd party contributed software
- Topic: Langouste -- WU upload/download de-coupler (+upload capping)
- Replies: 173
- Views: 149918
Re: Langouste -- WU upload/download de-coupler (+upload capp
IF the WU are still in the work directory, shut down the client and restart with the -configonly flag, tell it not to use a proxy and then restart the client with the -sendall switch. It should send the outstanding WU. I would then completely remove langouste, and recomplie/reinstall. Yes, I did tr...
- Sat Apr 07, 2012 7:25 pm
- Forum: 3rd party contributed software
- Topic: Langouste -- WU upload/download de-coupler (+upload capping)
- Replies: 173
- Views: 149918
Re: Langouste -- WU upload/download de-coupler (+upload capp
Yes, VERY repeatable. :( that log starts like this [1333824844.882126] Langouste3 0.15.7 (compiled Sat Apr 7 11:42:21 PDT 2012 by tofuwombat@schnellzug) [1333824844.882241] Langouste3 comes with ABSOLUTELY NO WARRANTY; for details [1333824844.882252] see `COPYING.txt' file located in source director...
- Fri Apr 06, 2012 6:43 pm
- Forum: 3rd party contributed software
- Topic: Langouste -- WU upload/download de-coupler (+upload capping)
- Replies: 173
- Views: 149918
Re: Langouste -- Two stranded WU no RL connections
I've got two stranded work units that I cannot send. Is there any way to force finished WU's out? (the files are there in the work directory) Kubuntu10.10/kraken/langouste My queueinfo: tofuwombat@schnellzug:~/fah$ ./fah6 -verbosity 9 -queueinfo Note: Please read the license agreement (fah6 -license...