Over the past week, there have been issues where some miners have multiple simultaneous connections open to the server, which results in increased CPU load and wasted bandwidth. Chris thinks that the cause of the problem is the same as what caused the old server to go offline when he plugged in the new server - network teaming.
Sometime today, he's going to experiment with disabling teaming on the switch, to confirm the hypothesis that the switch poorly programmed. Hopefully, he'll have this issue resolved by the morning.
Chris trying new fix
Forum rules
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The News forum is only for updates about the Prohashing pool.
Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Chris trying new fix
Chris identified the issue. It turns out that there are seven specific A4 workers that are establishing up to 134 connections every time there is a work restart.
Fortunately, the problem does not appear currently to be present anywhere else. We contacted the miner who is responsible to work on a solution.
Hopefully this is not a sign of A4 failures that happens over time. Whatever the case, we should have this issue resolved shortly.
Fortunately, the problem does not appear currently to be present anywhere else. We contacted the miner who is responsible to work on a solution.
Hopefully this is not a sign of A4 failures that happens over time. Whatever the case, we should have this issue resolved shortly.