Connection to dev pool closed by remote #30
Comments
|
dev pool down or unstable - 0.40. Tks |
|
Same problem here. v0.4.5. But only for my 1 rig. Connection is stable via Ethernet, no drops or lags related to Internet. After 12+ hours mining it cant connect to dev pool and hash reduced. It must be fixed asap. |
|
Hi @postalman, can you give us a little more information about your setup? |
|
Hi @todxx I have similar issue with version 0.4.5 in Windows 10. I have 4 x VEGA56 and 1x VEGA64. Today It worked approx. 4 hours normally, then this message appeared [2019-05-29 13:32:31] Dev pool connection was closed by remote side. Since then pool hashrate goes down a lot. You can find all history in the attached log file... Please solve this issue. I have AMD driver v. 18.6.1. Thank you. |
|
Hallo @todxx. This one rig in another city. Its 6xVega64. Windows pro x64 1903 May, with latest updates. It was connected by Wi-Fi when I saw this error. Than changed to Ethernet via cable. Same mistake. Connected to Tp-Link 941nd last revision and latest firmware. 100mb connection. about 18+ hours of normal mining and than this error apears. |
|
I m running on windows. My other old 290x who is running stak is working fine. Only those rigs tht is running trm encountering dev pool connection issue. It even crash my 550 2gb rigs after few failed attempts. Annoying bcos hv to keep monitor and restart the rigs
Sent from Yahoo Mail for iPhone
On Wednesday, May 29, 2019, 10:19 PM, vasssek <[email protected]> wrote:
Hi @todxx I hase similar issue with version 0.4.5 in Windows 10. I have 4 x VEGA56 and 1x VEGA64. Today It works approx. 4 hours normally, then this message appeared [2019-05-29 13:32:31] Dev pool connection was closed by remote side. Since then pool hashrate goes down a lot. You can find all history in the attached log file... Please solve this issue.
Thank you.
Vasssek
TeamRedMiner_0.4.5_dev_pool_issue.txt
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Bro.
Based on my observation. It seems tht your mining sw have low timeout / counts on connection issue. I m not sure the numbers but it will crash or blue screen on my win10 rigs. Normally it happened to those rigs tht hv more gpus. For Vegas , normally it kill off one gpu. If it happened again then another gpus died off. Those connection issue also could be due to firewall blocking by pool. Maybe due to rigs chg of dynamic ip. Of course normally , telco won’t simply chg the end user ip unless switched of location , telco maintenance , implementation 5g or etc.
Sent from Yahoo Mail for iPhone
On Wednesday, May 29, 2019, 12:05 PM, todxx <[email protected]> wrote:
Hi @postalman, can you give us a little more information about your setup?
Is this rig running windows or linux?
Is your network setup for this rig different than your other rigs?
Are your rigs going through a router? If so, what kind of router? (Some routers will occasionally block unknown traffic)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Its very annoying. I run all kind of miners with different allgos for 2 years with the same Internet provider and router and so far only this miner give such error. Also its ridiculous to make hash lower if not my problem. It would be fair to change such a defense from hacking method or release miner without it. I simply cant watch 24\7 when this error will appear. Hope it will be fixed. For now Im lookink for alternatives. |
|
Bro. Pls look into your dev pool as I m hit by intermittent dev pool error. Suggestion;- chg telco or other hosting.
Sent from Yahoo Mail for iPhone
On Sunday, June 2, 2019, 1:50 AM, postalman <[email protected]> wrote:
Its very annoying. I run all kind of miners with different allgos for 2 years with the same Internet provider and router and so far only this miner give such error. Also its ridiculous to make hash lower if not my problem. It would be fair to change such a defense from hacking method or release miner without it. I simply cant watch 24\7 when this error will appear. Hope it will be fixed. For now Im lookink for alternatives.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
The dev pool servers are hosted on google cloud and amazon web services. The miner will try to connect to the servers one by one until it can establish a connection. If you cannot connect to any of these servers, then the problem is most likely your ISP. We know that users in Russia and China have had issues due to their governments actively blocking internet traffic. Unfortunately, there isn't much we can do about that other than to suggest using a VPN. Do you mind sharing what country you are connecting from? |
|
From Malaysia site.
It’s intermittent and I suspect is the firewall detected chg of ip addrss or reset of dynamic ip. Trm doesn’t handle well when detected error “ forcefully rejected error”. Stak will report such error without crashing but trm will crash with blue screen OR one gpu night reported dead.
Just my finding this far.
Sent from Yahoo Mail for iPhone
On Friday, June 7, 2019, 12:25 PM, todxx <[email protected]> wrote:
The dev pool servers are hosted on google cloud and amazon web services. The miner will try to connect to the servers one by one until it can establish a connection. If you cannot connect to any of these servers, then the problem is most likely your ISP.
We know that users in Russia and China have had issues due to their governments actively blocking internet traffic. Unfortunately, there isn't much we can do about that other than to suggest using a VPN. Do you mind sharing what country you are connecting from?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
My country doesn’t block amazon nor google so we can rules tht out. I can connect to your dev pool after restart. normally it happened when trying to connect to your pool , after 1-2 hours. As I said, intermittently.
Sent from Yahoo Mail for iPhone
On Sunday, June 9, 2019, 5:57 PM, robson <[email protected]> wrote:
From Malaysia site.
It’s intermittent and I suspect is the firewall detected chg of ip addrss or reset of dynamic ip. Trm doesn’t handle well when detected error “ forcefully rejected error”. Stak will report such error without crashing but trm will crash with blue screen OR one gpu night reported dead.
Just my finding this far.
Sent from Yahoo Mail for iPhone
On Friday, June 7, 2019, 12:25 PM, todxx <[email protected]> wrote:
The dev pool servers are hosted on google cloud and amazon web services. The miner will try to connect to the servers one by one until it can establish a connection. If you cannot connect to any of these servers, then the problem is most likely your ISP.
We know that users in Russia and China have had issues due to their governments actively blocking internet traffic. Unfortunately, there isn't much we can do about that other than to suggest using a VPN. Do you mind sharing what country you are connecting from?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Nice features and new supported algo for 0.51. Just downloaded and testing on more the problematic 550x rigs. (550 will crash to blue screen, Vegas gpu dead only but still mining. All win10 ).
Question : I did not chg any config and merely copy the teamreadminer exe and replace current 0.45. Auto config kicks in and shown L2+3:AAA. 2+3 is my current setting. So do I need to replace current cn_config with the AAA? It also shown tht my current setting is correct and nothing to do with OC.
I noticed normally failed first attempt connect to your dev pool, then reconnect successfully. Sometimes failed 2nd or 3rd attempts. After tht will crash if more failed attempts.
For my vega 56 all Samsung original bios. Can i use the same method like 550 to run without changing any config ? Currently on 0.40 16+14. Very stable. Pool hash reporting slightly less than dash.
Sent from Yahoo Mail for iPhone
On Friday, June 7, 2019, 12:25 PM, todxx <[email protected]> wrote:
The dev pool servers are hosted on google cloud and amazon web services. The miner will try to connect to the servers one by one until it can establish a connection. If you cannot connect to any of these servers, then the problem is most likely your ISP.
We know that users in Russia and China have had issues due to their governments actively blocking internet traffic. Unfortunately, there isn't much we can do about that other than to suggest using a VPN. Do you mind sharing what country you are connecting from?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I solve it this way: every 12 hrs I close miner sw via scheduler and start it again. Now I don't have issues with dev pool. And if I have, it will persist only 12hrs :-). Btw. I'm from Slovakia and have no problem with ISP... |
|
It doesnt solve problem at all, cause devpool error may happens when it wants. In my case its can be 1 hour of mining or 12+ hours. Simple and random during day. Last day I checked in to the miner for couple hours and when saw devpool error start pinging google servers and AWS (amazon web services). Everything is fine and works perfect. Also after few hours of mining with devpool error I simply cant reboot system properly. It hangs and only power off from the wall helps. Conclusion: Its may be my isp problem but there is nothing I can on my side with this, otherwise no problems with xmr stak and srb miner for 24 hours on this system. Hope dev will fix this issue cause if other miners works than its definitely miner related or pools problems. |
|
Hi Todxx.
Hmm. Pretty sure is tiur amazon or google hosting. I decided sit down there and monitor a while. Dev switch at 5 min, then 27 mins. Same issue with failed attempt to your dev pool, 2nd attempt is usually ok. After a few hours of such failed attempt then crash on rigs. Is the hosting firewall. Pls do something bout it ASAP.
Sent from Yahoo Mail for iPhone
On Wednesday, June 12, 2019, 5:31 PM, postalman <[email protected]> wrote:
It doesnt solve problem at all, cause devpool error may happens when it wants. In my case its can be 1 hour of mining or 12+ hours. Simple and random during day. Last day I checked in to the miner for couple hours and when saw devpool error start pinging google servers and AWS (amazon web services). Everything is fine and works perfect. Also after few hours of mining with devpool error I simply cant reboot system properly. It hangs and only power off from the wall helps. Conclusion: Its may be my isp problem but there is nothing I can on my side with this, otherwise no problems with xmr stak and srb miner for 24 hours on this system. Hope dev will fix this issue cause if other miners works than its definitely miner related or pools problems.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I had this issue a few weeks back it fixed it self after a couple of days wasnt my ISP or PC. |
|
This is still an issue. Connection is fine downloading and connected and even connected to my pool.. in team red miner.. but not the devpool.. THIS HAS TO BE THE DEVPOOL |
|
This is with the new one... v 0.55 as you can see it was connected to support XMR the entire time.. but then not the DEV POOL then the Dev pool connects. It said it was closed... then immedietly connected! but in the post above this one.. it doesnt connect... and were at a reduced rate.
|
|
Ya , am having the same issues for sometime until I switched to stak 2.5.10 without problem. Stak hash for all my 12 x 550 2gb are lower vs trm (470 vs 501) but stable. I suspect is the amazon or whatever hosting firewall setting bcos the error on my side are very clear. First connection after restart TRM no issue, but subsequently will encountered failed on first connection, hash reduce then reconnect 2nd time will be successful. It doesnt happened all the time, and when no issue the 550's will run stable for a week+ hence its not OC problem. The crash only happened to 12x 550 since it send more jobs than Vega's x6. the following are my rigs setup. |
Hi.
I saw this message 20 mins ago (from my posting time) for all my rigs. It was fine yesterday. Can u reconnect after 10 or 30 minutes later else my rigs will be running slow.
The connection closed by your pool. So pls look into tht
The text was updated successfully, but these errors were encountered: