Page 6 of 7
Re: Problem uploading to 129.74.246.143
Posted: Tue Nov 25, 2014 11:43 pm
by Kent Irwin
Why no definitive word from Pande group? We contributors PAY real money to operate our folding systems. We contributors who make the whole system work PAY real money for hardware and utility bills in order to fold. Forget points.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 2:33 am
by DrBB1
billford wrote:DrBB1 wrote:
In the meantime, I suggest those like me who are waiting for the fix to simply check the server status using the "Server Status" link at the top of this page.
Sound advice if it was working properly- viewtopic.php?f=18&t=27054#p271527
billford-- Thanks for pointing out this other issue with the server status reports. All the more reason to update the community periodically on the status of 129.74.246.143.
Re: 0.0.0.0 collection server for about 3-4 Wu's straight
Posted: Wed Nov 26, 2014 4:45 am
by Bensen85
Hi guys,
I have a small problem with two PCs (same problem), since 6 days 21.11.2014)!
Please look on the picture, maybe you have an explanation for that!?
problem no 1:
one WU in the client is not sent. Cellection Server 0.0.0.0?
problem no 2:
Since then I only get small WU 800-1700 points (2 hours work), before that it was WUs with more than 12,000 points!
Meanwhile, I have the problem with PC No. 3
PC No.1 2 from 2CPUs
PC No.2 7 from 8CPUs
PC No.3 4 from 7CPUs
can anyone help, I need to change something?
http://www.imgbox.de/show/img/BfhyAIcfEl.PNG
http://www.imgbox.de/show/img/XuHj6Uklkp.png
about help I would be very grateful!
Warning Protocol
Code: Select all
07:19:23:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
07:19:30:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-24 *******************************
12:41:24:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
12:41:31:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-24 *******************************
18:41:30:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
18:41:37:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-24 *******************************
00:41:31:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
00:41:38:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-25 *******************************
06:41:19:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
06:41:25:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-25 *******************************
************ Log Started 2014-11-24T12:20:32Z ***********************
12:20:39:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:20:41:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
12:20:54:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:21:10:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
12:22:00:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:22:01:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
12:23:26:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:23:33:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
12:26:05:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:26:12:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
12:30:11:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:30:13:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
12:37:03:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:37:07:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
12:48:08:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
12:48:15:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
13:06:17:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
13:06:19:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
13:35:09:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
13:35:23:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
14:22:23:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
14:22:42:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
15:38:07:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
15:38:14:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
17:41:07:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:41:08:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-24 *******************************
21:00:12:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
21:00:14:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
******************************* Date: 2014-11-25 *******************************
02:22:12:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
02:22:26:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.
******************************* Date: 2014-11-25 *******************************
Mod edit: added code tags to log and moved post to a more appropriate thread
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 5:48 am
by Windego
Came back about a month ago, I see not much has changed. Finishing up what my system is working on, if this gets resolved before then great, if not too bad at the lost science. The silence is deafening.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 7:40 am
by billford
DrBB1 wrote:All the more reason to update the community periodically on the status of 129.74.246.143.
Don't hold your breath, this is par for the course.
PG simply take it for granted that donors will still be there when a problem is fixed, panting for new WUs to fold. Because most do it for reasons of conscience, to help in the fight against disease.
And the trouble is that PG are right, which makes the lack of interest in addressing donors' concerns the more reprehensible.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 1:31 pm
by 7im
Take the hard facts any way you want. It's not going to change reality. Points are not guaranteed. Servers break down.
PG is on holiday all week like most every university is during Thanksgiving. Be thankful there is a fah project that will some day save lives and that you were part of it.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 3:18 pm
by billford
7im wrote:Take the hard facts any way you want. It's not going to change reality. Points are not guaranteed. Servers break down.
PG is on holiday all week like most every university is during Thanksgiving. Be thankful there is a fah project that will some day save lives and that you were part of it.
Thanksgiving is a day, not a week, and PG haven't bothered to provide cover, even on a voluntary basis, to ensure that donors are kept informed should problems occur.
As a hard fact that speaks volumes.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 3:39 pm
by howler4x4
Thanksgiving is a day, not a week
When I did server support for a major bank in NYC we got a day and a half off for Thanksgiving, not everybody, but wherever possible. Universities take multiple days for what is a major family holiday in the US.
Perhaps I won't get points for the job I have waiting, it's not a big deal. I do feel for those that have multiple jobs waiting. Gnashing of teeth won't help but will make folks unhappy. Please be patient.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 4:10 pm
by billford
howler4x4 wrote:Please be patient.
Yes, I'm aware of the status of Thanksgiving in the USA, and the points I'm losing don't bother me unduly either.
But when you run a world-wide project requiring the participation of donors who volunteer the (largely) 24/7 use of their own equipment and the associated expenses then a little consideration in return is, I think, in order. Holiday or no holiday.
It's not as if this is an isolated example of PG taking donors for granted- I don't think it's a matter of policy, just a lack of real appreciation of the effect that their single-minded concentration on the science has on donor relations. They're in danger of forgetting that without those donors they would have no science. And all that has really been asked for in this topic is
information, which isn't too hard to provide and doesn't involve substantial inroads into anyone's festivities.
I've had jobs where I was on 24 hour call, and have been called out. And situations when providing limited unpaid cover over major holidays was necessary. It's a nuisance, but if it's required then it's required.
Much has been made elsewhere of the general decline of interest in distributed computing, PG should be doing whatever they can, including maintaining good relationships with existing donors, to reverse that trend for their own project. It's in their own interest.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 4:41 pm
by Kougar
howler4x4 wrote:Thanksgiving is a day, not a week
When I did server support for a major bank in NYC we got a day and a half off for Thanksgiving, not everybody, but wherever possible. Universities take multiple days for what is a major family holiday in the US.
My Alma Mater only gave Thurs/Fri off, I remember a few professors loved to give exams on Wednesday, because as they put it nobody would remember the material if they waited till the following Monday.
It appears Notre Dame's starts Wednesday and ends on Sunday however, so unless someone makes an exception and goes in it may be till next week till this gets resolved.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 6:33 pm
by Gooders
Has this thread really turned into a witch hunt?
Servers down... Meh... least the whole project isnt down.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 6:39 pm
by 7im
billford wrote:7im wrote:Take the hard facts any way you want. It's not going to change reality. Points are not guaranteed. Servers break down.
PG is on holiday all week like most every university is during Thanksgiving. Be thankful there is a fah project that will some day save lives and that you were part of it.
Thanksgiving is a day, not a week, and PG haven't bothered to provide cover, even on a voluntary basis, to ensure that donors are kept informed should problems occur.
As a hard fact that speaks volumes.
Boxing Day is a just a day, and yet many people take the whole week off.
And the problem already occurred. PG was notified. And several forum volunteers have tried to explain this process several times. And you will be informed when there is new information. Sounds covered to me.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 6:42 pm
by Esko_Kauppinen
Makes me wonder if this data my computers have been crunching is worth anything as nobody seems interested of it.
I think I will give my computers a rest and shut down FAH for the time being.
Re: Problem uploading to 129.74.246.143
Posted: Wed Nov 26, 2014 7:33 pm
by sortofageek
As this topic is far off track from the site purpose of members doing our best to help other members fold, I am going to place a temporary lock.
If anyone has news to add about the status of this server, please let a mod know why you would like the thread unlocked.
TIA for your cooperation. I hope all who celebrate Thanksgiving are getting ready for a happy day of food, family and friendship tomorrow.
Re: work units not sending. Also, idle not working properly
Posted: Sun Nov 30, 2014 6:56 pm
by SeyfertR
Good afternoon.
I'm running into an issue where a finished unit is being actively refused by the return server on port 8080 and 80 (according to the log). No other finished packets have been denied, since I have been participating on this project 48M points ago. It is one of the CPU units so I'd just as soon delete the thing and move on with my life. However if solving the issue is worth anything to someone, please let me know how I shall move forward.
The relevant log period looks like this:
Code: Select all
18:19:31:Removing old file 'configs/config-20141015-103116.xml'
18:19:31:Saving configuration to config.xml
18:19:31:<config>
18:19:31: <!-- Folding Core -->
18:19:31: <checkpoint v='5'/>
18:19:31:
18:19:31: <!-- Logging -->
18:19:31: <verbosity v='5'/>
18:19:31:
18:19:31: <!-- Network -->
18:19:31: <proxy v=':8080'/>
18:19:31:
18:19:31: <!-- Slot Control -->
18:19:31: <power v='full'/>
18:19:31:
18:19:31: <!-- User Information -->
18:19:31: <passkey v='********************************'/>
18:19:31: <team v='200386'/>
18:19:31: <user v='SeyfertR'/>
18:19:31:
18:19:31: <!-- Folding Slots -->
18:19:31: <slot id='0' type='CPU'>
18:19:31: <client-type v='advanced'/>
18:19:31: <cpus v='4'/>
18:19:31: </slot>
18:19:31: <slot id='1' type='GPU'>
18:19:31: <client-type v='beta'/>
18:19:31: </slot>
18:19:31: <slot id='2' type='GPU'>
18:19:31: <client-type v='beta'/>
18:19:31: </slot>
18:19:31: <slot id='3' type='GPU'>
18:19:31: <client-type v='beta'/>
18:19:31: </slot>
18:19:31: <slot id='4' type='GPU'>
18:19:31: <client-type v='beta'/>
18:19:31: </slot>
18:19:31:</config>
18:20:18:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7043 run:0 clone:903 gen:0 core:0xa4 unit:0x000000000001329c546e64c4ee6fb2bf
18:20:18:WU00:FS00:Uploading 16.83MiB to 129.74.246.143
18:20:18:WU00:FS00:Connecting to 129.74.246.143:8080
18:20:19:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
18:20:19:WU00:FS00:Connecting to 129.74.246.143:80
18:20:20:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: No connection could be made because the target machine actively refused it.
18:21:05:WU02:FS02:0x17:Completed 3125000 out of 5000000 steps (62%)
18:21:05:WU02:FS02:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
18:21:14:WU01:FS00:0xa4:Completed 60000 out of 250000 steps (24%)
18:22:55:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7043 run:0 clone:903 gen:0 core:0xa4 unit:0x000000000001329c546e64c4ee6fb2bf
18:22:55:WU00:FS00:Uploading 16.83MiB to 129.74.246.143
18:22:55:WU00:FS00:Connecting to 129.74.246.143:8080
18:22:56:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
18:22:56:WU00:FS00:Connecting to 129.74.246.143:80
18:22:57:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: No connection could be made because the target machine actively refused it.
18:23:37:WU01:FS00:0xa4:Completed 62500 out of 250000 steps (25%)
18:26:00:WU01:FS00:0xa4:Completed 65000 out of 250000 steps (26%)
18:26:02:WU06:FS04:0x17:Completed 1750000 out of 5000000 steps (35%)
18:27:09:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7043 run:0 clone:903 gen:0 core:0xa4 unit:0x000000000001329c546e64c4ee6fb2bf
18:27:09:WU00:FS00:Uploading 16.83MiB to 129.74.246.143
18:27:09:WU00:FS00:Connecting to 129.74.246.143:8080
18:27:10:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
18:27:10:WU00:FS00:Connecting to 129.74.246.143:80
18:27:12:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: No connection could be made because the target machine actively refused it.
18:27:47:WU04:FS01:0x18:Completed 125000 out of 2500000 steps (5%)
18:28:10:WU05:FS03:0x18:Completed 1325000 out of 2500000 steps (53%)
18:28:23:WU01:FS00:0xa4:Completed 67500 out of 250000 steps (27%)
18:30:18:WU02:FS02:0x17:Completed 3150000 out of 5000000 steps (63%)
18:30:46:WU01:FS00:0xa4:Completed 70000 out of 250000 steps (28%)
18:32:59:WU06:FS04:0x17:Completed 1800000 out of 5000000 steps (36%)
18:33:08:WU01:FS00:0xa4:Completed 72500 out of 250000 steps (29%)
18:33:20:Started thread 66 on PID 6780
18:34:01:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7043 run:0 clone:903 gen:0 core:0xa4 unit:0x000000000001329c546e64c4ee6fb2bf
18:34:01:WU00:FS00:Uploading 16.83MiB to 129.74.246.143
18:34:01:WU00:FS00:Connecting to 129.74.246.143:8080
18:34:02:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
18:34:02:WU00:FS00:Connecting to 129.74.246.143:80
18:34:03:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: No connection could be made because the target machine actively refused it.
18:35:31:WU01:FS00:0xa4:Completed 75000 out of 250000 steps (30%)
18:36:09:WU04:FS01:0x18:Completed 150000 out of 2500000 steps (6%)
18:36:54:WU05:FS03:0x18:Completed 1350000 out of 2500000 steps (54%)
18:37:54:WU01:FS00:0xa4:Completed 77500 out of 250000 steps (31%)
18:39:56:WU06:FS04:0x17:Completed 1850000 out of 5000000 steps (37%)
18:40:17:WU01:FS00:0xa4:Completed 80000 out of 250000 steps (32%)
18:42:39:WU01:FS00:0xa4:Completed 82500 out of 250000 steps (33%)
18:44:31:WU04:FS01:0x18:Completed 175000 out of 2500000 steps (7%)
18:45:02:WU01:FS00:0xa4:Completed 85000 out of 250000 steps (34%)
18:45:06:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:7043 run:0 clone:903 gen:0 core:0xa4 unit:0x000000000001329c546e64c4ee6fb2bf
18:45:06:WU00:FS00:Uploading 16.83MiB to 129.74.246.143
18:45:06:WU00:FS00:Connecting to 129.74.246.143:8080
18:45:07:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
18:45:07:WU00:FS00:Connecting to 129.74.246.143:80
18:45:09:WARNING:WU00:FS00:Exception: Failed to send results to work server: Failed to connect to 129.74.246.143:80: No connection could be made because the target machine actively refused it.
18:45:38:WU05:FS03:0x18:Completed 1375000 out of 2500000 steps (55%)
In addition, before running I turned the router IPS and the firewall off, as I know that these sometimes get in the way of other things, like iTunes downloads. It was turned back on after running the test and the change seems to have made no difference.
I would send a snapshot of the main screen I took; however, I am unsure how to post .jpg's to this board. I can email it to someone if they like. The most important information I think someone might want from it is as follows:
PRCG: 7043 (0,903,0)
Status: Send
ETA: Unknown
FahCore: 0xa4
Waiting On: Send Results
Attempts: 31
Work Server: 129.74.246.143
Collection Server: 0.0.0.0
I can email, post as instructed or type in other information from the main screen that is relevant.
As I mentioned help deleting the work unit out of the outbound queue is fine too, as after 14 days, it has gotten to be annoying to look at. These core tasks are more to keep the CPU warm, then for anything else. The GPUs seem to do all of the heavy lifting in this problem space, according to "points".
Take care, God bless and hope everyone enjoyed the Thanksgiving Holiday.
Rich Seyfert
mod edit: added code tags and moved post to the relevant thread on the server's outage ... thank you for your report