Stratum from pool 0 requested work restart что делать
Как запустить майнинг биткоина с multipool.us
Вот тебе хороший совет : не вкладывай денег в майнинг. Гораздо выгодней сразу купить битков.
Ещё более хороший совет, не стоит вкладывать деньги в то, в чем не разбираешься.
я и не вкладывал.
сколько времини надо ждать появления воркера в списке активных?
сколько времини надо ждать появления воркера в списке активных?
Как бы говорит, что не дождёшься.
Как я понял, без этих «свистков» можно даже и не пытаться. А как сделать так, чтобы майнинг шёл на процессоре?
Ещё более хороший совет, не стоит вкладывать деньги во всякое МММ
поискать древний майнер, умеющий на процессоре
Скорее до сих пор из криокамеры не выбрался.
А как тогда сделать так, чтобы майнинг шёл на видеокарте?
Скачать древний майнер, который умеет майнить на видеокарте. Это примерно четырёхлетней давности. Свежие майнеры для битков умеют только асики.
Или майнь что-то другое, а не битки.
Как я понял, без специального оборудования майнить не как не получится
Майни альткойны, сливай их в биток. Но там неделю колупаться в теории, прежде чем поймешь что именно майнить выгодно тебе.
Купи парочку циклонов, прошей туды майнерский асик и майни себе, и можешь даже кидать понты: «а у меня биткоин ферма на асиках!».
Битки только асиками. Остальное можно на видеокарте. Есть хитрожопые монетки, которые можно только на процессоре. Майнить именно битки очень странное желание в 2017 году. Майнь что угодно, меняй на битки на бирже, или в обменниках. Майнить вообще лучше какой-нибудь свежак в надежде что потом выстрелит. Поскольку у популярных монеток сложность уже такая, что майнинг ближе к ситуации «вернуть бы своё».
Майни Etherium на GPU и Monero на CPU. А биткоин майнят на ASIC.
Stratum keeps requesting work restart #95
Comments
colt05 commented Nov 29, 2015
Hey guys, I have been mining for bitcoins on Slush’s Pool (stratum+tcp://stratum.bitcoin.cz:3333) and cpuminer is running on a Koding VM. I keep getting «Stratum requested work restart» but then I get this:
thread 0: 257818480 hashes, 8591 khash/s
DEBUG: hash > target (false positive)
Hash: 0000000050ea2b0ac608b30d08178e7b13d21e13a47f12d6ebd6a253466ef777
Target: 000000001fffe000000000000000000000000000000000000000000000000000
DEBUG: hash > target (false positive)
Hash: 00000000484c19edc82403e1a83b785ddb210c653f4d00e8b05336a370960acf
Target: 000000001fffe000000000000000000000000000000000000000000000000000
I never got this far on TomPool multipool (I am using Slush’s pool now though which tells me my worker is offline), so is there a fix for the work restart? Thanks.
The text was updated successfully, but these errors were encountered:
pooler commented Nov 29, 2015
A few work restarts per minute are totally normal. Besides, it’s the server that decides when the client should start working on a new job, and there’s nothing you can do about that.
False positives are also totally normal when the share difficulty is higher than 1. (Your examples show a difficulty of 8).
colt05 commented Nov 30, 2015
Thanks! But sometimes, it says «Stratum requested work restart» after every time it says something like «thread 0: 257818480 hashes, 8591 khash/s.»
pooler commented Nov 30, 2015
That is also normal. When switching jobs the number of computed hashes and the speed are printed (unless quiet mode is enabled).
colt05 commented Nov 30, 2015
Oh, is that so? Thanks for the information.
reppolice commented May 7, 2017
Hmm, doesn’t that «switching jobs» mean the work has been lost, since only «shares yay» count?
pooler commented May 8, 2017
@reppolice No, it doesn’t. Mining is a memoryless process, there is no «progress» that you can lose.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
What does “Stratum requested work restart” mean?
Recently, BiblePay released an external miner (a fork of minerd by pooler, aka cpuminer).
This has been working great for solo mining with and without anti-bot-net (ABN).
Now that solo mining is working well, BiblePay is improving code to allow the miner to work with stratum and the NOMP pool.
Should I be concerned about stratum requested work restart?
The stratum server decides when to send new work to the miner.
A few work restarts per minute are totally normal. Besides, it’s the server that decides when the client should start working on a new job, and there’s nothing you can do about that.
When a new block is found, stratum asks client to start on new work.
If you see restart followed by stratum from pool 0 detected new block you know the block was just mined and miner needs to start work on the new block.
The short version is that the work to produce the “next” block depends on the previous block. The moment a new block is found, any in-progress searching is aborted because it won’t produce anything useful. This is important because it encourages a “found” block to be used and distributed quickly.
You should see this message each time the … network as a whole finds a new block.
The miner and pool software is constantly evolving so the performance and usefulness of the web site (e.g. stats) should improve over time.
In BiblePay version 1.4.5.1b, Rob added an enhancement to getblockforstratum where the merkle root changes every second due to randomization of the extraNonce field with a random integer. In previous versions, the merkle root would not change unless the block height changed. This previously made receiving unique blocks from the pool to miners very difficult. This also helps to mitigate bugs in NOMP where some miners were submitting different case (upper case instead of lower case) of share data to make it seem the pool was receiving a unique share. The cheat is mitigated by issuing a new merkleroot after a share is accepted. It does create more bandwidth demand, but with NOMP being fully tested, it is better to be cautious.
With every acceptable share submitted to the pool, the stratum requests a work restart for that miner (or perhaps entire thread on NOMP) and authorizes the miner again in the pool. Duplicate shares are still possible, but they tend to be from different miners in the same thread number. The most common error now will be job not found (stale share) which can happen if the miner submits a share from the old merkle root and does not realize a new “block” is available.
To keep the pool efficient, it is really the miner’s job to change things like the nTime to have more work to exhaust before requesting more from the pool or until the pool announces a block height change.
Stratum requested work restart #4
Comments
lolbob181 commented Dec 3, 2017
I constantly keep getting Stratum requested work restart
i keep thinking its doing the mining but not anymore.
This is what it says:
The text was updated successfully, but these errors were encountered:
demogorgonz commented Dec 3, 2017
The short version is that the work to produce the «next» block depends on the previous block. The moment a new block is found, any in-progress searching is aborted because it won’t produce anything useful. This is important because it encourages a «found» block to be used and distributed quickly.
You should see this message each time the coin network as a whole finds a new block.
Also make sure to configure worker’s «Share Diff» to 64.
lolbob181 commented Dec 8, 2017
Its been like this this for 4days left it running 24/7 everyday same not made a single penny
demogorgonz commented Dec 9, 2017
You should try some other pool than. I have no clue why ipominer would reject low h/s.
demogorgonz commented Dec 11, 2017
Since there is no response, i will close this issue for now. Feel free to reopen if other pools doesn’t work.
lolbob181 commented Dec 11, 2017
Whats your discord? Think it will be easier to communicate
peppre commented Jan 3, 2021
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Stratum from pool 0 requested work restart что делать
Post by hashingpro » Fri Sep 01, 2017 1:22 am
Open to testing ideas. anything I can ping or tracert to get some answers as to why I cant connect now, was fine for a day or so, nothing changed on my end, now cant connect in again, and the miners status pages all list the prohash site as DEAD. Finds and mines on the two backups just fine.
Tracert over to prohashing.com seems normal, not sure how to test to the stratum site address.
C:\Windows\system32>tracert http://www.prohashing.com
Tracing route to http://www.prohashing.com [167.88.14.215]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 11 ms 9 ms 96.120.62.45
3 10 ms 9 ms 10 ms te-0-5-0-1-sur02.pittsburgh.pa.pitt.comcast.net [68.85.157.197]
4 10 ms 11 ms 10 ms te-0-0-0-0-ar01.mckeesport.pa.pitt.comcast.net [68.86.147.109]
5 17 ms 17 ms 17 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
6 18 ms 16 ms 16 ms hu-0-11-0-3-pe04.ashburn.va.ibone.comcast.net [68.86.88.78]
7 15 ms 16 ms 20 ms 23.30.206.206
8 43 ms 47 ms 45 ms 89.149.141.253
9 45 ms 49 ms 44 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
10 46 ms 43 ms 51 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 45 ms 45 ms 49 ms 29-96-79-64.as20278.net [64.79.96.29]
12 44 ms 48 ms 46 ms 215-14-88-167.reverse-dns [167.88.14.215]
any suggestions on why it cant find the site to mine here when it could a day or so ago just fine?
Sometimes it will even show up ALIVE, send all the miners there for the next work share, then go DEAD and disconnect again, showing 12 miners doing 16megahash instead of 5.5 GH.
Re: L3s still not finding prohash
Post by micca410evo » Fri Sep 01, 2017 5:04 am
Re: L3s still not finding prohash
Post by Steve Sokolowski » Fri Sep 01, 2017 8:12 am
Chris has been working on this issue for days and is not able to reproduce it and has not made any progress as to the cause.
Any additional information is helpful. Unfortunately, we don’t have any idea where to go from here and Chris may have to stop actively working on it. But we’ll still keep monitoring the forums in the hope that maybe the reports, taken as a whole, could yield some clues.
Re: L3s still not finding prohash
Post by mycide » Fri Sep 01, 2017 10:09 am
Re: L3s still not finding prohash
Post by hashingpro » Fri Sep 01, 2017 2:57 pm
Well, if Chris has been working on this for days and cant reproduce it, get ahold of me I can make my farm available to you to remote in and do testing on to figure out why the site is showing as DEAD from my miners. Its not port 3333, other pools are on it, but I did try the proxy server address same results. Its NOT dns related or the miners would NEVER find the address, sometimes 8-12 units will connect to prohash hash a few seconds then get kicked back off. And its not any settings in the password, I defaulted it to n=test on a few machines to eliminate that issue. I also used another users account name to see if the miner would mine for them on their account in case it was a database or account issue, using 2 other peoples account names to mine with, still showed the pool as DEAD from the miners.
I was fine and connected and working as well as everyone else until the service change to the new data lines, since then, it will not let me connect in for more than just a few seconds then boot me off.
And the fact others are having this issue means it must actually still be an issue. If we had a specific site to do a tracert or a ping test or some type of info gathering for all those having the issue and feed you the data would that help in anyway you finding out what the problem or issue is?
Re: L3s still not finding prohash
Post by hashingpro » Fri Sep 01, 2017 3:29 pm
So the miners are connected now, but still having errors thrown out on the logs not being able to find prohash.
Sep 1 18:17:36 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:18:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:18:06 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:18:19 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:18:36 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:18:56 (none) local0.notice cgminer[25546]: Network diff set to 247K
Sep 1 18:18:56 (none) local0.info cgminer[25546]: New block: 0000000000000cdfbbaf614a0b48d81f84bd2aa413fda81de71efe2e4bcf53e6. diff 247K
Sep 1 18:18:56 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:19:00 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:19:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:19:07 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:19:19 (none) local0.info cgminer[25546]: New block: fe767d35195d81647aec8d162ccc6f2f6a588c102c706bedf7ad8ae4f69d618e. diff 247K
Sep 1 18:19:19 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:19:37 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:20:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:20:08 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:20:20 (none) local0.notice cgminer[25546]: Network diff set to 266K
Sep 1 18:20:20 (none) local0.info cgminer[25546]: New block: 0000000000003c67d0e74a5342c6533f49222e37a5269f1ea3e52f84cac4042d. diff 266K
Sep 1 18:20:20 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:20:38 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:20:39 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:20:42 (none) local0.info cgminer[25546]: New block: ef059d254b46934476de555c713378e0e0caf04b68e6a56d057e1a62cb122c7c. diff 266K
Sep 1 18:20:42 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:20:55 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:21:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:21:08 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:21:21 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:21:38 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:21:45 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:22:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:22:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:22:39 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:22:46 (none) local0.notice cgminer[25546]: Pool 1 difficulty changed to 65536
Sep 1 18:23:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:23:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:23:17 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:23:29 (none) local0.notice cgminer[25546]: Network diff set to 215K
Sep 1 18:23:29 (none) local0.info cgminer[25546]: New block: 000000000000043f776549f49d5b430d004683e4842290fa8ca3644d9ad7aef1. diff 215K
Sep 1 18:23:29 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:23:39 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:24:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:24:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:24:16 (none) local0.warn cgminer[25546]: Stratum reconnect requested from pool 1 to scrypt.usa.nicehash.com:3333
Sep 1 18:24:16 (none) local0.info cgminer[25546]: Cleared 2 work items due to stratum disconnect on pool 1
Sep 1 18:24:16 (none) local0.info cgminer[25546]: Stratum authorisation success for pool 1
Sep 1 18:24:16 (none) local0.notice cgminer[25546]: Pool 1 difficulty changed to 16384
Sep 1 18:24:16 (none) local0.notice cgminer[25546]: Stratum from pool 1 requested work restart
Sep 1 18:24:19 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:24:23 (none) local0.notice cgminer[25546]: Stratum from pool 1 requested work restart
Sep 1 18:24:37 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:24:39 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:24:41 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:24:48 (none) local0.info cgminer[25546]: New block: 0000000000000e95b4e544b08b88fc15751b56ef51102c81c8f345fe38281c75. diff 215K
Sep 1 18:24:48 (none) local0.notice cgminer[25546]: Stratum from pool 1 detected new block
Sep 1 18:24:49 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:25:00 (none) local0.info cgminer[25546]: Testing pool stratum+tcp://prohashing.com:3333
Sep 1 18:25:05 (none) local0.info cgminer[25546]: Pool 1 stratum share result lag time 1 seconds
Sep 1 18:25:09 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Sep 1 18:25:40 (none) local0.info cgminer[25546]: Failed to connect to stratum on prohashing.com:3333
Re: L3s still not finding prohash
Post by hashingpro » Sat Sep 02, 2017 12:11 am
Miners re-connected around 3:20 pm est today and have been on ever since rock steady.
Haven’t been to backup pools now in hours, nothing changed on my end they just started detecting prohash as ALIVE and started mining on it again.
Now just don’t touch any settings so I can get a solid 24-hours in please!
Thanks for all your hard work you do, and offer still stands, If you need outside access to try some remote testing or settings from some miners let me know.
Re: L3s still not finding prohash
Post by Steve Sokolowski » Sat Sep 02, 2017 9:57 am
Re: L3s still not finding prohash
Post by hashingpro » Sun Sep 03, 2017 2:44 pm
I woke up around 1 PM est, 3 miners still going other 5 showed DEAD on the site, all using the same account.
All on the same rack, same switch, same router, same ISP.
refreshed the webpage and the 3 working miners all showed ALIVE.
Rebooted the 5 not connecting, after reboot they still showed PH site as DEAD.
5 mins later the 3 working ones got kicked off and showed PH site as DEAD.
15 after the reboot all 8 came online and showed PH as ALIVE and are working now the past hour or so.
The 3 that were on when i woke up were never touched other than to refresh their status pages, so no reboots the site just came back up for them all after 15 mins.