pool connection failed check internet pool url or worker что делать
Ошибка: «socket was closed remotely (by pool)» — Решено!
Большинство майнеров сталкиваются со следующей ошибкой майнинга: socket was closed remotely (by pool), как на рисунке ниже. Данная ошибка может возникнуть из-за нескольких проблем, ниже рассмотрим каждую.
В первую очередь мы написали в службу поддержку ethermine.org. получили вот такой ответ:
«Thank you for your response, this seems to be related to the newest version of claymore miner. Please try rolling back a version, this should solve this.»
Перевод ответа: «Решением проблемы является использование более старой версии Claymore.»
Если вам указанный выше совет не помог, то рекомендуем попробовать следующие установки:
Добавить комментарий Отменить ответ
Промокод на скидку в интернет магазине для читателей моего сайта
Доброго дня, любимый читатель! Я являюсь менеджером сайта OZON.ru и хочу поделиться с вами промокодом на скидку 300 руб. для первого заказа: OZON0NB71A (Условия акции). Если вы уже совершали покупки на сайте озон, то активировав указанный выше промокод, вы получите дополнительные скидки на товары. На озоне вы сможете приобрести электронику и комплектующие к ним по приятным ценам и удобной доставкой.
Cрок действия приветственных баллов — 5 дней. Баллами можно оплатить 25% от стоимости покупок.
Connection to dev pool closed by remote #30
Comments
rb116 commented Mar 12, 2019
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:
rb116 commented Apr 16, 2019
postalman commented May 28, 2019
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.
todxx commented May 29, 2019
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)
vasssek commented May 29, 2019 •
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.
postalman commented May 29, 2019
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.
postalman commented Jun 1, 2019
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.
todxx commented Jun 7, 2019
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?
vasssek commented Jun 12, 2019
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.
postalman commented Jun 12, 2019
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.
SomethingGettingWrong commented Jun 27, 2019
I had this issue a few weeks back it fixed it self after a couple of days wasnt my ISP or PC.
SomethingGettingWrong commented Jul 10, 2019 •
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 
SomethingGettingWrong commented Jul 10, 2019 •
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.
Reccomend LAXING the timings on the REDUCED RATE of mining trigger point
It said it was closed. then immedietly connected! but in the post above this one.. it doesnt connect. and were at a reduced rate.
IM From the USA and literaly 4 hours from Amazon Webservers.
@todxx
rb116 commented Aug 9, 2019
Connection pool is full, discarding connection with ThreadPoolExecutor and multiple headless browsers through Selenium and Python
Most of the the logic is ok to be executed by the single browser instance, but for some part i have to launch 10-20 instances to have a decent execution speed.
browser setup:
relevant code:
this is working:
these options are not working: ( connectionpool errors )
UPDATE:
2 Answers 2
This error message.
. seems to be an issue in urllib3 ‘s connection pooling which raised these WARNING while executing the def _put_conn(self, conn) method in connectionpool.py.
ThreadPoolExecutor
ThreadPoolExecutor is an Executor subclass that uses a pool of threads to execute calls asynchronously. Deadlocks can occur when the callable associated with a Future waits on the results of another Future.
As per your question as you are trying to launch 10-20 instances the default connection pool size of 10 seems not to be enough in your case which is hardcoded in adapters.py.
It looks like within the requests code, None objects are normal. If _get_conn() gets None from the pool, it simply creates a new connection. It seems odd, though, that it should start with all those None objects, and that _put_conn() isn’t smart enough to replace None with the connection.
However the merge Add pool size parameter to client constructor have fixed this issue.
Solution
Increasing the default connection pool size of 10 which was earlier hardcoded in adapters.py and now configurable will solve your issue.
Update
I stepped into the code to the point where it mounts the adapter just to play with the pool size and see if it made a difference. What I found was that the queue is full of NoneType objects with the actual upload connection being the last item in the list. The list is 10 items long (which makes sense). What doesn’t make sense is that the unfinished_tasks parameter for the pool is 11. How can this be when the queue itself is only 11 items? Also, is it normal for the queue to be full of NoneType objects with the connection we are using being the last item on the list?
That sounds like a possible cause in your usecase as well. It may sound redundant but you may still perform a couple of ad-hoc steps as follows:
Русские Блоги
Пул соединений с базой данных Spring Boot HikariCP
1、HikariCP？
HikariCP происходит от японского, что означает «легкий», что означает, что он быстрый! Spring boot 2.0 сделал HikariCP пулом ссылок на источники данных по умолчанию.
На официальном веб-сайте подробно объясняются некоторые оптимизации, сделанные HikariCP, вкратце:
2. Пул подключений к базе данных
3. Конфигурация общих атрибутов
3.1 autoCommit
This property controls the default auto-commit behavior of connections
returned from the pool. It is a boolean value. Default: true
Этот атрибут управляет поведением автоматической фиксации по умолчанию для подключений, возвращаемых из пула. Это логическое значение. Значение по умолчанию: true
3.2 connectionTimeout
This property controls the maximum number of milliseconds that a
client (that’s you) will wait for a connection from the pool. If this
time is exceeded without a connection becoming available, a
SQLException will be thrown. Lowest acceptable connection timeout is
250 мс. По умолчанию: 30000 (30 секунд). Этот атрибут определяет максимальное количество миллисекунд, в течение которых клиент (то есть вы) ожидает соединения в пуле.
Если это время превышено при отсутствии доступного соединения, будет сгенерировано исключение SQLException. Минимально допустимое время ожидания соединения составляет 250 миллисекунд.
Значение по умолчанию: 30000 (30 секунд).
3.3 idleTimeout
3.4 maxLifetime
This property controls the maximum lifetime of a connection in the
pool. An in-use connection will never be retired, only when it is
closed will it then be removed. On a connection-by-connection basis,
minor negative attenuation is applied to avoid mass-extinction in the
pool. We strongly recommend setting this value, and it should be
several seconds shorter than any database or infrastructure imposed
connection time limit. A value of 0 indicates no maximum lifetime
(infinite lifetime), subject of course to the idleTimeout setting.
По умолчанию: 1800000 (30 минут). Этот атрибут управляет наибольшим сроком жизни соединения в пуле.
Используемое соединение никогда не будет отключено и будет удалено только после закрытия. Для каждого соединения применяется небольшое отрицательное затухание, чтобы избежать массовых вымираний в бассейне.
Мы настоятельно рекомендуем установить это значение, которое должно быть на несколько секунд меньше, чем ограничение времени подключения, установленное любой базой данных или инфраструктурой. Значение 0 означает, что нет максимального жизненного цикла (бесконечный жизненный цикл), конечно, предмет
параметр idleTimeout. Значение по умолчанию: 1800000 (30 минут).
3.5 connectionTestQuery
If your driver supports JDBC4 we strongly recommend not setting this
property. This is for “legacy” drivers that do not support the JDBC4
Connection.isValid() API. This is the query that will be executed just
before a connection is given to you from the pool to validate that the
connection to the database is still alive. Again, try running the pool
without this property, HikariCP will log an error if your driver is
not JDBC4 compliant to let you know. Default: none
Если ваш драйвер поддерживает JDBC4, мы настоятельно рекомендуем не устанавливать это свойство. Это относится к соединениям, которые не поддерживают JDBC4 Connection.isValid () API.
«устаревший» драйвер. Это запрос, выполняемый до того, как соединение будет предоставлено из пула, чтобы проверить, существует ли еще соединение с базой данных.
Попробуйте снова запустить пул без этого атрибута. Если ваш драйвер не соответствует JDBC4, HikariCP регистрирует ошибку, чтобы уведомить вас. Значение по умолчанию: Нет
3.6 minimumIdle
This property controls the minimum number of idle connections that
HikariCP tries to maintain in the pool. If the idle connections dip
below this value and total connections in the pool are less than
maximumPoolSize, HikariCP will make a best effort to add additional
connections quickly and efficiently. However, for maximum performance
and responsiveness to spike demands, we recommend not setting this
value and instead allowing HikariCP to act as a fixed size connection
pool. По умолчанию: то же, что и maximumPoolSize. Это свойство контролирует минимальное количество незанятых соединений, которые HikariCP пытается поддерживать в пуле.
Если количество незанятых подключений ниже этого значения, а общее количество подключений в пуле меньше maximumPoolSize, HikariCP сделает все возможное, чтобы добавить другие подключения быстро и эффективно.
Однако для максимальной производительности и реакции на пиковый спрос мы рекомендуем не устанавливать это значение, а позволить HikariCP действовать как пул соединений фиксированного размера. Значение по умолчанию: и
тот же maximumPoolSize
3.7 maximumPoolSize
This property controls the maximum size that the pool is allowed to
reach, including both idle and in-use connections. Basically this
value will determine the maximum number of actual connections to the
database backend. A reasonable value for this is best determined by
your execution environment. When the pool reaches this size, and no
idle connections are available, calls to getConnection() will block
for up to connectionTimeout milliseconds before timing out. Please
прочтите о размере пула. По умолчанию: 10 Этот атрибут управляет максимальным размером, разрешенным для пула, включая неактивные и используемые соединения.
Как правило, это значение определяет максимальное фактическое количество подключений к серверной части базы данных. Разумное значение для этого лучше всего определяется средой выполнения. Когда пул достигает этого размера и отсутствуют свободные подключения,
Вызов getConnection () будет блокироваться в течение миллисекунд connectionTimeout до истечения времени ожидания. Пожалуйста, прочтите информацию о размере бассейна.
Значение по умолчанию: 10
3.9 metricRegistry
This property is only available via programmatic configuration or IoC
container. This property allows you to specify an instance of a
Codahale/Dropwizard MetricRegistry to be used by the pool to record
various metrics. See the Metrics wiki page for details. Default: none
Этот атрибут можно получить только с помощью конфигурации программирования или контейнера IoC. Этот атрибут позволяет указать Codahale / Dropwizard, используемый пулом.
Экземпляр MetricRegistry для записи различных показателей. Подробности см. На вики-странице показателей. Значение по умолчанию: Нет
3.10 healthCheckRegistry
This property is only available via programmatic configuration or IoC
container. This property allows you to specify an instance of a
Codahale/Dropwizard HealthCheckRegistry to be used by the pool to
report current health information. See the Health Checks wiki page for
подробности. По умолчанию: нет. Этот атрибут можно получить только с помощью конфигурации программирования или контейнера IoC. Этот атрибут позволяет указать Codahale /
Экземпляр Dropwizard HealthCheckRegistry для сообщения текущей информации о состоянии здоровья. Дополнительные сведения см. На вики-странице проверки работоспособности.
Значение по умолчанию: нет
3.11 poolName
This property represents a user-defined name for the connection pool
and appears mainly in logging and JMX management consoles to identify
pools and pool configurations. Default: auto-generated
Этот атрибут представляет определяемое пользователем имя пула соединений, которое в основном отображается в консоли управления журналами и JMX для идентификации пула и конфигурации пула. Значение по умолчанию: генерируется автоматически
4. Пример конфигурации
5. Дополнительная конфигурация
5. Производительность
Желающие могут попробовать пройти тест самостоятельно.
6. Ссылка для сравнения функций
Роль нитей
stratum_recv_line failed / Stratum connection interrupted #124
Comments
amit177 commented Jun 23, 2017
Hey,
No matter on what pool I’m mining,
I’m getting this error.
«stratum_recv_line failed»
«Stratum connection interrupted»
OS: Ubuntu 16.04
Current pool: F2Pool
The text was updated successfully, but these errors were encountered:
pooler commented Jun 24, 2017
Please provide more information. Which version of cpuminer? Did you build it yourself? If not, where did you get the binary? What parameters are you passing? Does the error pop up immediately after you start the miner or after some time?
Linkin87 commented Jul 2, 2017
@pooler Mee too, I’m using ubuntu 17.x I’ve build by myself. But when i use cpumier of JayDDee, everything is ok.
amit177 commented Jul 2, 2017
pooler commented Jul 2, 2017
This looks like an issue with the server or with the network connection, not with the miner.
Could you provide detailed instructions to reproduce it? Please do not omit the address of the server, it is relevant.
Linkin87 commented Jul 2, 2017
i dont think so, there are many pepple like me and they change to use another tool.
amit177 commented Jul 2, 2017
I changed alot of pools, all of them has the same problem,
Also, is it not supposed to say accepted or something?
pooler commented Jul 2, 2017
Again, please provide one pool address where you can consistently reproduce this issue, so that I can try to reproduce it myself.
Also, is it not supposed to say accepted or something?
Sure, but if you’re mining Bitcoin finding a share can take a really long time.
amit177 commented Jul 2, 2017
My fault, eu1.bitminter.com:3333
pooler commented Jul 2, 2017
After running cpuminer against eu1.bitminter.com:3333 for two hours, what I observed is that the server interrupts the connection every 11 minutes exactly. This is clearly a timeout to disconnect clients that appear to be inactive (not submitting any shares).
There doesn’t appear to be anything wrong with the miner or the server, they’re both behaving as expected. The server simply disconnects you because you’re not submitting any shares, you’re not finding any shares because you’re extremely slow relative to the difficulty that the server sets, and the difficulty is set so high because the server is not expecting anyone to mine with a CPU.
@Linkin87: just for the sake of completeness I also tested the fork you mentioned, and it exhibits the exact same behavior.
amit177 commented Jul 2, 2017
uh, okay thank you!
do you have any pools that has low difficulty? or its not the right place?
pooler commented Jul 2, 2017
This is not the right place to ask, but if you want my opinion, you shouldn’t be mining Bitcoin with CPUs at all.
calidion commented Feb 19, 2018
i am encountering the same problem.
lordvalium commented Feb 25, 2018
usscsmith commented Aug 27, 2018
I’m brand new to mining and still trying to digest even the basics. But I’ve been playing with Awesome Miner while I figure everything out and I started a new miner and kept seeing with every profit pool.
Turns out it did not like my BTC Wallet address. When I changes the Wallet address to my NiceHash and restarted the miner; it had no issues.
hiphopservers commented Oct 17, 2018
I had the same error but like @pooler mention this error in my case was related to a slow pool server loosing or not allowing connectivity. Anyone with this issue should consider using a different pool. It is also agreed that if that a miner should mine crypto with a reasonable low difficulty on CPU mining.
leshacat commented May 8, 2020 •
I have same issue, from sounds of this discussion it is likely server-side.
@pooler is right about the timeout, makes perfect sense. I have noticed this only on my smaller miners who I also noticed don’t submit shares as often. I assume it just reconnects and sends any shares afterwards.
The thing you should be concerned with is if it says «booooo» thats when it rejected a share.