problem with 158.130.118.25 fah server

[Smookin_Joe]

problem with 158.130.118.25 fah server
The above says it all
12 attempts to upload...and counting

[Smookin_Joe]

After 30 tries I guess deleting the work folder is probably the best solution...

[Smookin_Joe]

Had to do it 2 times tonight
Pause everything shutdown..deleted the gpu work folder.
Computer has 2 4090's and they are working fine.
This server doesn't like this computer...
Why?

[Smookin_Joe]

Update
Please accept my apology for deleting finished wu's and for accusing a FAH server of wrong doing.
This morning I was having the same problem with a different server.
I believe I have found the issue within my own network.
I am sorry and I will try and do better.
I had a number of things that were bothering me and I let it affect my judgement.
Sorry...
Joe

[BobWilliams757]

I had seen your message and noticed that the servers showed as up without issues, but failed to comment since I don't have much expertise other than basic firewall things on the user end that might cost a problem.

But based on your stats seems to me you have more than made up for dumping a few finished work units. With only a small handful of people that have contributed more to folding, I don't think anybody will take any strong offense to a human error.

I'm sure your contribution to science is appreciated by many, and I know in my case it is appreciated.

[jjmiller]

Ack- sorry for not commenting earlier, I just got back into the office. Absolutely no worries - glad the connection is resolved! Please do let me know if more issues pop up - I'll do my best to address anything we can from our end.

Thanks as well for folding- we appreciate every WU you fold!

[bikeaddict]

I've started getting this error on one client.

Code: Select all

19:10:31:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:10:31:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:10:31:WU02:FS00:Connecting to 158.130.118.25:8080
19:11:02:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:11:02:WU02:FS00:Trying to send results to collection server
19:11:02:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:11:02:WU02:FS00:Connecting to 158.130.118.26:8080
19:11:32:ERROR:WU02:FS00:Exception: Not connected
19:11:32:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:11:32:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:11:32:WU02:FS00:Connecting to 158.130.118.25:8080
19:12:03:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:12:03:WU02:FS00:Trying to send results to collection server
19:12:03:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:12:03:WU02:FS00:Connecting to 158.130.118.26:8080
19:12:33:ERROR:WU02:FS00:Exception: Not connected
19:12:33:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:12:33:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:12:33:WU02:FS00:Connecting to 158.130.118.25:8080
19:13:04:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:13:04:WU02:FS00:Trying to send results to collection server
19:13:04:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:13:04:WU02:FS00:Connecting to 158.130.118.26:8080
19:13:34:ERROR:WU02:FS00:Exception: Not connected
19:14:10:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:14:10:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:14:10:WU02:FS00:Connecting to 158.130.118.25:8080
19:14:40:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:14:40:WU02:FS00:Trying to send results to collection server
19:14:40:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:14:40:WU02:FS00:Connecting to 158.130.118.26:8080
19:15:11:ERROR:WU02:FS00:Exception: Not connected
19:16:48:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:16:48:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:16:48:WU02:FS00:Connecting to 158.130.118.25:8080
19:17:18:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:17:18:WU02:FS00:Trying to send results to collection server
19:17:18:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:17:18:WU02:FS00:Connecting to 158.130.118.26:8080
19:17:48:ERROR:WU02:FS00:Exception: Not connected
19:21:02:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:21:02:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:21:02:WU02:FS00:Connecting to 158.130.118.25:8080
19:21:32:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:21:32:WU02:FS00:Trying to send results to collection server
19:21:32:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:21:32:WU02:FS00:Connecting to 158.130.118.26:8080
19:22:02:ERROR:WU02:FS00:Exception: Not connected
19:27:53:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:27:53:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:27:53:WU02:FS00:Connecting to 158.130.118.25:8080
19:28:24:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:28:24:WU02:FS00:Trying to send results to collection server
19:28:24:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:28:24:WU02:FS00:Connecting to 158.130.118.26:8080
19:28:54:ERROR:WU02:FS00:Exception: Not connected
19:38:59:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:18224 run:129 clone:1 gen:50 core:0x23 unit:0x00000001000000320000473000000081
19:38:59:WU02:FS00:Uploading 30.26MiB to 158.130.118.25
19:38:59:WU02:FS00:Connecting to 158.130.118.25:8080
19:39:29:WARNING:WU02:FS00:Exception: Failed to send results to work server: Not connected
19:39:29:WU02:FS00:Trying to send results to collection server
19:39:29:WU02:FS00:Uploading 30.26MiB to 158.130.118.26
19:39:29:WU02:FS00:Connecting to 158.130.118.26:8080
19:39:59:ERROR:WU02:FS00:Exception: Not connected

[Joe_H]

I've started getting this error on one client.

See the announcement - viewtopic.php?p=364584#p364584

[Smookin_Joe]

Thank you for the responses and understanding.
Near as I can figure out, the problem I had was a new, much faster, router.
It had the Telnet "disabled" suggesting I use SSH.
After I enabled it, the problems seemed to have disappeared.
The problem did not immediately start when the new Asus RT-AX88U Pro, was installed, and there was a few, lingering, set backs after telnet was turned on.
Side note...
I have a very complex network that I have upgraded over the years and I haven't had to have someone come in and fix anything...yet...lol
ISP Router/gateway guest router/VPN router/home router all subnetted together with managed switches and EAP''s and folding computers using TPLink AP's in the client mode. I can remote in to all my equipment from my home office...most times..lol
I do what I can to give back and my guests (foreign students, going to local schools) have largely made that possible.
I do not overcharge and I see little or no wear and tear on my guest house.
Again..
Thank You for the kind words of understanding
Joe

[Smookin_Joe]

I've started getting this error on one client.

See the announcement - viewtopic.php?p=364584#p364584

LoL
Now ya tell me!

[jjmiller]

That sounds like quite an impressive network and a great setup.

The server outage in the linked post above started on June 18th ~3P EST. As far as I can tell it was an immediate and total shutdown on the networking side. I haven't heard yet what led to the failure. It actually took down our local compute cluster as well.

[Smookin_Joe]

That sounds like quite an impressive network and a great setup.

The server outage in the linked post above started on June 18th ~3P EST. As far as I can tell it was an immediate and total shutdown on the networking side. I haven't heard yet what led to the failure. It actually took down our local compute cluster as well.

Thank you jjmiller
It wasn't an easy trip getting to this point. Quite the learning curve, over the years...
I do know I had a couple of minor hiccups with my new routers.
I had tested, what was to become, my new home router as a temporary guest router while I was shopping for a better gateway/guest router.
I am very pleased it has become quite boring to maintain
Sounds like I was experiencing my troubles at the beginning of the shutdown.
Canary in the coal mine? or just coincidence?
I did come home to find a number of finished wu's stacked up on one machine (5 or 6) and when I rebooted the TPLink client they got sent.(coincidence? my equipment?)
I swapped it out with a pre configured client and ended up chasing a new remote desktop issue because of it.
That new problem got fixed by reinstalling the supposedly bad client in the same computer.
Rather than think I can't replace a TPLink client if I need to...I have ordered up a number of USB wifi adapters to replace the TPLink clients.
The new router is unable to correctly identify the computers using TPLink clients because there is 2 different mac addresses and 2 different ip's associated with each of those computers.
My old home router did not have this problem but the throughput was 150Mbps.
With the two new routers now I am at 850+Mbps on most of my wired machines and 950Mbps at the routers.