▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 188.

crackfoo

legendary

Activity: 3486

Merit: 1126

Quote from: Windozxpert on August 23, 2017, 07:38:50 AM

Quote from: crackfoo on August 23, 2017, 07:33:53 AM

This week I'm in the process of replacing the main zpool server which runs the frontend, sql and stratums. This requires updates to all the coin boxes due to new IP's. There be some bumps along the way as coinds are restarted etc... interruptions should be fairly short and will announce when the actual changeover will take place. I'm hoping later today to pull the trigger.

Cool beans. I just noticed all my Neoscrypt miners were down and was about to mention it. Thanks for the server upgrade. Anything we can do to help?

yes, I hope this will allow for a much more responsive webpage as well as stratums, the machine is more than twice as big and fast with 100% ssd now.

Just be patient

I've one more coin box to reconfigure and a bunch more coinds will be restarted, then I can get back to finishing the setup on the main server.

I stopped the scripts just now cause I failed to look at the new payout time and it was right now, so I want those coins back online before kicking off the payout. Mining should still be working though on most all algos and the blocks will get processed in a few more mins.

Windozxpert

full member

Activity: 196

Merit: 100

Quote from: crackfoo on August 23, 2017, 07:33:53 AM

This week I'm in the process of replacing the main zpool server which runs the frontend, sql and stratums. This requires updates to all the coin boxes due to new IP's. There be some bumps along the way as coinds are restarted etc... interruptions should be fairly short and will announce when the actual changeover will take place. I'm hoping later today to pull the trigger.

Cool beans. I just noticed all my Neoscrypt miners were down and was about to mention it. Thanks for the server upgrade. Anything we can do to help?

crackfoo

legendary

Activity: 3486

Merit: 1126

This week I'm in the process of replacing the main zpool server which runs the frontend, sql and stratums. This requires updates to all the coin boxes due to new IP's. There be some bumps along the way as coinds are restarted etc... interruptions should be fairly short and will announce when the actual changeover will take place. I'm hoping later today to pull the trigger.

guytechie

hero member

Activity: 677

Merit: 500

All mining stopped. Cannot connect to the pool.

jmvarner83

member

Activity: 194

Merit: 12

Mined 4 bitcore blocks, they went to exchange and came back cleared but wallet balance never moved or updated and no deposit.

Huh

cryptolelefla

member

Activity: 121

Merit: 10

still having different time same miner's name on dashboard. it is a miner problem(prospector) or something else.
i also had a screenshot on my precedent post.
hope pool support have a few second to reply me. thanks

Fromage

sr. member

Activity: 338

Merit: 250

Quote from: bctcrypt on August 21, 2017, 08:30:40 PM

Hi,
Been trying ZPool and Hash Refinery Mining Pool but yet to get a payout to my actual wallet.

Still a little way off hitting the payout threshold with Zpool but a bit concerned that I have had over 0.0013 BTC Confirmed on Hash Refinery Mining Pool since mid last week but it didn't payout automatically on Sunday.

On the main page it says:

"Payouts are made automatically every 8 hours for all balances above 0.0025, or 0.00025 on Sunday."

As my balance was well over the 0.00025 well before Sunday, wondering why it hasn't payed out?

Just to confirm it does show my correct Bitcoin wallet address under the wallet section on ZPool and Hash Refinery Mining Pool. Still a little way off hitting the threshold of 0.0015 for Zpool but wondering it looks like it might end up with the same issue.

Mining Pool Hub has already payed out to the same wallet address successfully.

Yeah first of all this is Zpool's bitcointalk....Pm me for more info on the other one

bctcrypt

newbie

Activity: 8

Merit: 0

Hi,
Been trying ZPool and Hash Refinery Mining Pool but yet to get a payout to my actual wallet.

Still a little way off hitting the payout threshold with Zpool but a bit concerned that I have had over 0.0013 BTC Confirmed on Hash Refinery Mining Pool since mid last week but it didn't payout automatically on Sunday.

On the main page it says:

"Payouts are made automatically every 8 hours for all balances above 0.0025, or 0.00025 on Sunday."

As my balance was well over the 0.00025 well before Sunday, wondering why it hasn't payed out?

Just to confirm it does show my correct Bitcoin wallet address under the wallet section on ZPool and Hash Refinery Mining Pool. Still a little way off hitting the threshold of 0.0015 for Zpool but wondering it looks like it might end up with the same issue.

Mining Pool Hub has already payed out to the same wallet address successfully.

crackfoo

legendary

Activity: 3486

Merit: 1126

nova exchange has been disabled until further notice. Coins listed only on there will show 0 value until their issue is resolved

amitim

newbie

Activity: 59

Merit: 0

Quote from: guytechie on August 21, 2017, 02:31:11 PM

That's the worker's ID or name. It is a valid way of adding a identifier.

So what is ",xmg"? I thought it had to be the algo, which is ",m7m", not the coin.

BTW, removing the worker's name, as well as removing the difficulty setting (d=x) still does not work.

I'm using cpuminer-opt 3.6.8 if that matters.

XMG is Coin of Magi
Ok, my batch for win with cpuminer-opt 3.6.7:

Code:

e:
cd e:\cpuminer367\

:start
cpuminer-sse2.exe -r 0 -a m7m -o stratum+tcp://mine.zpool.ca:6033 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=my_rig,c=BTC,xmg,xevan,yescrypt,stats
cpuminer-sse2.exe -r 0 -a xevan -o stratum+tcp://mine.zpool.ca:3739 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=my_rig,c=BTC,xmg,xevan,yescrypt,stats
cpuminer-sse2.exe -r 0 -a yescrypt -o stratum+tcp://mine.zpool.ca:6233 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=my_rig,c=BTC,xmg,xevan,yescrypt,stats

pause 10
goto start

cryptolelefla

member

Activity: 121

Merit: 10

Quote from: crackfoo on August 20, 2017, 07:15:00 PM

Quote from: nsummy on August 20, 2017, 06:52:44 PM

Is the "24 Actual Payout" for X11 in MH or GH? The footnote claims the that only blake and sha256 are listed in GH, but it doesn't seem like that is accurate.

fixed. missed a couple spots for that. it is in GH

getting 22 miners instead of 2. is this normal??
https://i.imgur.com/a/G58xz

guytechie

hero member

Activity: 677

Merit: 500

Quote from: amitim on August 21, 2017, 01:22:48 PM

Quote from: guytechie on August 21, 2017, 12:03:43 PM

The example is exactly how I wrote my script out.

try w/o "d=..."
for example "...-u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p worker,xevan,yescrypt,m7m
or
"...-u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p worker,xevan,yescrypt,xmg"
Hmmm... What is it "...worker..."? algo? I don't show this in list on the zpool.ca
Try strictly by example:

ccminer -r 0 -a x11 -o stratum+tcp://x11.mine.zpool.ca:3533 -u joe -p x11,x13,x14,x15,quark,lyra2
ccminer -r 0 -a x13 -o stratum+tcp://x13.mine.zpool.ca:3633 -u joe -p x11,x13,x14,x15,quark,lyra2

That's the worker's ID or name. It is a valid way of adding a identifier.

So what is ",xmg"? I thought it had to be the algo, which is ",m7m", not the coin.

BTW, removing the worker's name, as well as removing the difficulty setting (d=x) still does not work.

I'm using cpuminer-opt 3.6.8 if that matters.

BTW, the fact that the stratum_recv_line failed should indicate it's a server-side issue.

[2017-08-21 18:53:17] stratum_recv_line failed
[2017-08-21 18:53:17] ...terminating workio thread
[2017-08-21 18:53:17] workio thread dead, exiting.

amitim

newbie

Activity: 59

Merit: 0

Quote from: guytechie on August 21, 2017, 12:03:43 PM

The example is exactly how I wrote my script out.

try w/o "d=..."
for example "...-u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p worker,xevan,yescrypt,m7m
or
"...-u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p worker,xevan,yescrypt,xmg"
Hmmm... What is it "...worker..."? algo? I don't show this in list on the zpool.ca
Try strictly by example:

ccminer -r 0 -a x11 -o stratum+tcp://x11.mine.zpool.ca:3533 -u joe -p x11,x13,x14,x15,quark,lyra2
ccminer -r 0 -a x13 -o stratum+tcp://x13.mine.zpool.ca:3633 -u joe -p x11,x13,x14,x15,quark,lyra2

guytechie

hero member

Activity: 677

Merit: 500

Quote from: amitim on August 21, 2017, 11:25:35 AM

Quote from: guytechie on August 21, 2017, 11:11:29 AM

Mine is Windows.

Code:

:start
cpuminer.exe -r 0 -a xevan -o stratum+tcp://mine.zpool.ca:3739 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=0.02,worker,xevan,yescrypt,m7m
cpuminer.exe -r 0 -a m7m -o stratum+tcp://mine.zpool.ca:6033 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=2,worker,xevan,yescrypt,m7m
cpuminer.exe -r 0 -a yescrypt -o stratum+tcp://mine.zpool.ca:6233 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=1,worker,xevan,yescrypt,m7m
goto start

http://www.zpool.ca/site/multialgo example. I'm not shure, but first need try as on example?

The example is exactly how I wrote my script out.

amitim

newbie

Activity: 59

Merit: 0

Quote from: guytechie on August 21, 2017, 11:11:29 AM

Mine is Windows.

Code:

:start
cpuminer.exe -r 0 -a xevan -o stratum+tcp://mine.zpool.ca:3739 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=0.02,worker,xevan,yescrypt,m7m
cpuminer.exe -r 0 -a m7m -o stratum+tcp://mine.zpool.ca:6033 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=2,worker,xevan,yescrypt,m7m
cpuminer.exe -r 0 -a yescrypt -o stratum+tcp://mine.zpool.ca:6233 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=1,worker,xevan,yescrypt,m7m
goto start

http://www.zpool.ca/site/multialgo example. I'm not shure, but first need try as on example?

guytechie

hero member

Activity: 677

Merit: 500

Quote from: amitim on August 21, 2017, 10:59:41 AM

Quote from: guytechie on August 21, 2017, 09:25:24 AM

Why is it that whenever you remove or disable an algo, the miners do not fail over to another algo? I have a script written out like how you suggest in the site, but when it fails the m7m, it would try xevan next, but then gets disconnected, then yescrypt, but then gets disconnected, then goes back to m7m (which fails), and repeats itself.

Shouldn't it fail m7m, then start mining the next profitable coin (in this case, xevan)?

show your script file. for me fine restarted to the next algo:

Code:

./cpuminer.sh

   ********** cpuminer-opt 3.6.7 ***********
   A CPU miner with multi algo support and optimized for CPUs
   with AES_NI and AVX extensions.
   BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
   Forked from TPruvot's cpuminer-multi with credits
   to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
   Wolf0, Jeff Garzik and Optiminer.

[2017-08-21 18:53:17] Starting Stratum on stratum+tcp://mine.zpool.ca:6033
[2017-08-21 18:53:17] 4 miner threads started, using 'm7m' algorithm.
[2017-08-21 18:53:17] Stratum connection failed: Failed to connect to mine.zpool.ca port 6033: Connection refused
[2017-08-21 18:53:17] ...terminating workio thread
[2017-08-21 18:53:17] workio thread dead, exiting.

[2017-08-21 18:53:17] Starting Stratum on stratum+tcp://mine.zpool.ca:3739
[2017-08-21 18:53:17] 4 miner threads started, using 'xevan' algorithm.
[2017-08-21 18:53:17] stratum_recv_line failed
[2017-08-21 18:53:17] ...terminating workio thread
[2017-08-21 18:53:17] workio thread dead, exiting.

[2017-08-21 18:53:17] Starting Stratum on stratum+tcp://mine.zpool.ca:6233
[2017-08-21 18:53:18] 4 miner threads started, using 'yescrypt' algorithm.
[2017-08-21 18:53:20] Stratum difficulty set to 1
[2017-08-21 18:53:37] yescrypt block 147294, diff 0.232
[2017-08-21 18:53:39] CPU #0: 512 H, 291.55 H/s
[2017-08-21 18:53:39] CPU #1: 512 H, 287.34 H/s
[2017-08-21 18:53:39] CPU #2: 512 H, 280.48 H/s
[2017-08-21 18:53:39] CPU #3: 512 H, 262.39 H/s

my script

Code:

#!/bin/bash
cd ~/cpuminer

for ((;;))
do

./cpuminer -r 0 -a m7m -o stratum+tcp://mine.zpool.ca:6033 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=mylinux_101,c=BTC,xmg=0.035,xevan=0.035,yescrypt,stats
./cpuminer -r 0 -a xevan -o stratum+tcp://mine.zpool.ca:3739 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=mylinux_101,c=BTC,xmg=0.035,xevan=0.035,yescrypt,stats
./cpuminer -r 0 -a yescrypt -o stratum+tcp://mine.zpool.ca:6233 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=mylinux_101,c=BTC,xmg=0.035,xevan=0.035,yescrypt,stats

sleep 5000
done

Mine is Windows.

Code:

:start
cpuminer.exe -r 0 -a xevan -o stratum+tcp://mine.zpool.ca:3739 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=0.02,worker,xevan,yescrypt,m7m
cpuminer.exe -r 0 -a m7m -o stratum+tcp://mine.zpool.ca:6033 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=2,worker,xevan,yescrypt,m7m
cpuminer.exe -r 0 -a yescrypt -o stratum+tcp://mine.zpool.ca:6233 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p d=1,worker,xevan,yescrypt,m7m
goto start

amitim

newbie

Activity: 59

Merit: 0

Quote from: guytechie on August 21, 2017, 09:25:24 AM

Why is it that whenever you remove or disable an algo, the miners do not fail over to another algo? I have a script written out like how you suggest in the site, but when it fails the m7m, it would try xevan next, but then gets disconnected, then yescrypt, but then gets disconnected, then goes back to m7m (which fails), and repeats itself.

Shouldn't it fail m7m, then start mining the next profitable coin (in this case, xevan)?

show your script file. for me fine restarted to the next algo:

Code:

./cpuminer.sh

   ********** cpuminer-opt 3.6.7 ***********
   A CPU miner with multi algo support and optimized for CPUs
   with AES_NI and AVX extensions.
   BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
   Forked from TPruvot's cpuminer-multi with credits
   to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
   Wolf0, Jeff Garzik and Optiminer.

[2017-08-21 18:53:17] Starting Stratum on stratum+tcp://mine.zpool.ca:6033
[2017-08-21 18:53:17] 4 miner threads started, using 'm7m' algorithm.
[2017-08-21 18:53:17] Stratum connection failed: Failed to connect to mine.zpool.ca port 6033: Connection refused
[2017-08-21 18:53:17] ...terminating workio thread
[2017-08-21 18:53:17] workio thread dead, exiting.

[2017-08-21 18:53:17] Starting Stratum on stratum+tcp://mine.zpool.ca:3739
[2017-08-21 18:53:17] 4 miner threads started, using 'xevan' algorithm.
[2017-08-21 18:53:17] stratum_recv_line failed
[2017-08-21 18:53:17] ...terminating workio thread
[2017-08-21 18:53:17] workio thread dead, exiting.

[2017-08-21 18:53:17] Starting Stratum on stratum+tcp://mine.zpool.ca:6233
[2017-08-21 18:53:18] 4 miner threads started, using 'yescrypt' algorithm.
[2017-08-21 18:53:20] Stratum difficulty set to 1
[2017-08-21 18:53:37] yescrypt block 147294, diff 0.232
[2017-08-21 18:53:39] CPU #0: 512 H, 291.55 H/s
[2017-08-21 18:53:39] CPU #1: 512 H, 287.34 H/s
[2017-08-21 18:53:39] CPU #2: 512 H, 280.48 H/s
[2017-08-21 18:53:39] CPU #3: 512 H, 262.39 H/s

my script

Code:

#!/bin/bash
cd ~/cpuminer

for ((;;))
do

./cpuminer -r 0 -a m7m -o stratum+tcp://mine.zpool.ca:6033 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=mylinux_101,c=BTC,xmg=0.035,xevan,yescrypt,stats
./cpuminer -r 0 -a xevan -o stratum+tcp://mine.zpool.ca:3739 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=mylinux_101,c=BTC,xmg=0.035,xevan,yescrypt,stats
./cpuminer -r 0 -a yescrypt -o stratum+tcp://mine.zpool.ca:6233 -u 153jhJMkgCMt5X8hoyQg8MawegeCibaBnZ -p ID=mylinux_101,c=BTC,xmg=0.035,xevan,yescrypt,stats

sleep 5000
done

guytechie

hero member

Activity: 677

Merit: 500

Quote from: crackfoo on August 21, 2017, 08:44:17 AM

Quote from: pginvest on August 21, 2017, 08:37:51 AM

m7m is offline and algo not liested...

their coin forked again. I'm not sure yet if I'll ever bring it back.

Why is it that whenever you remove or disable an algo, the miners do not fail over to another algo? I have a script written out like how you suggest in the site, but when it fails the m7m, it would try xevan next, but then gets disconnected, then yescrypt, but then gets disconnected, then goes back to m7m (which fails), and repeats itself.

[2017-08-21 09:23:57] Starting Stratum on stratum+tcp://mine.zpool.ca:3739
[2017-08-21 09:23:57] 8 miner threads started, using 'xevan' algorithm.
[2017-08-21 09:23:58] stratum_recv_line failed
[2017-08-21 09:23:58] ...terminating workio thread
[2017-08-21 09:23:58] workio thread dead, exiting.

[2017-08-21 09:24:13] Starting Stratum on stratum+tcp://mine.zpool.ca:6033
[2017-08-21 09:24:13] 8 miner threads started, using 'm7m' algorithm.
[2017-08-21 09:24:14] Stratum connection failed: Failed to connect to mine.zpool.ca port 6033: Connection refused
[2017-08-21 09:24:14] ...terminating workio thread
[2017-08-21 09:24:14] workio thread dead, exiting.

[2017-08-21 09:24:24] Starting Stratum on stratum+tcp://mine.zpool.ca:6233
[2017-08-21 09:24:24] 8 miner threads started, using 'yescrypt' algorithm.
[2017-08-21 09:24:26] stratum_recv_line failed
[2017-08-21 09:24:26] ...terminating workio thread
[2017-08-21 09:24:26] workio thread dead, exiting.

Shouldn't it fail m7m, then start mining the next profitable coin (in this case, xevan)?

crackfoo

legendary

Activity: 3486

Merit: 1126

Quote from: pginvest on August 21, 2017, 08:37:51 AM

m7m is offline and algo not liested...

their coin forked again. I'm not sure yet if I'll ever bring it back.

pginvest

sr. member

Activity: 308

Merit: 250

m7m is offline and algo not liested...

Topic: ▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 188. (Read 279614 times)