Bitcoin Forum
September 29, 2022, 02:43:14 AM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 [153] 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 ... 502 »
  Print  
Author Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 773355 times)
keksik
Jr. Member
*
Offline Offline

Activity: 169
Merit: 1


View Profile
March 03, 2019, 08:06:52 PM
 #3041

hello,

i would like to ask some questions:
- when i start to mine, how long it takes to start dev mining?
- when i start stop miner, does it reset counter for dev mining? for example im mining with another miner, then it starts with claymore, after couple hours, it switch back and then after couple hours again with claymore, so does it reset dev mining counter? or another example, im fine tunning and i left miner run for half hour or less, does the counter reset all the time?

thank you
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Bigdrago
Newbie
*
Offline Offline

Activity: 312
Merit: 0


View Profile
March 03, 2019, 09:20:41 PM
 #3042

My gpu is 48C and fan is 0%  according to phoenix miner program. (I have set target temp 50C).
 
But I also have set minimum rpm. Is the fan completely shut off when my  mining program shows that the fan is 0%? Or is it 0% compared to what  minimum fan speed is. That it is actually 500rpm (0%) and max is 2400rpm  (100%) ?
I cant look at the gpus because they are boxed in and safe outside.
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 04, 2019, 12:44:13 PM
 #3043

For AMD

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 2345678 -acm -clKernel 2 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

For Nvidia

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 1345 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

is geth running on same machine?

can you add -v 3 to the command line its for more verbose output.


geth is on a different machine.

-v only prints version and exits - doesn't enable verbose.  -log 2 is supposed to enable debug messages, but doesn't really appear any different.  Here's a full log with -log 2

So same thing here - why is it monitoring a stratum thread and rebooting because of it if we are not using stratum.  Seems like a pretty clear bug to me.

Code:
2019.03.04:07:37:05.759: main Phoenix Miner 4.1c Linux/gcc - Release build
2019.03.04:07:37:05.759: main Cmd line: -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 6 -gpureset 1 -rmode 2 -log 0 -wal address_redacted -worker m01n6 -log 2
2019.03.04:07:37:05.887: main CUDA version: 10.0, CUDA runtime: 8.0
2019.03.04:07:37:05.902: main Available GPUs for mining:
2019.03.04:07:37:05.902: main GPU1: GeForce GTX 1060 6GB (pcie 16), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2019.03.04:07:37:05.905: main NVML library initialized
2019.03.04:07:37:05.952: main Nvidia driver version: 415.27
2019.03.04:07:37:05.953: main Eth: the pool list contains 1 pool (1 from command-line)
2019.03.04:07:37:05.953: main Eth: primary pool: http://10.69.1.10:8547
2019.03.04:07:37:05.953: main Starting GPU mining
2019.03.04:07:37:05.953: main Eth: Connecting to http://10.69.1.10:8547 (GetWork/Solo)
2019.03.04:07:37:05.953: wdog Starting watchdog thread
2019.03.04:07:37:05.954: eths Eth: New job #ec69b6c7 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:05.954: eths Eth: Connected to ethash pool http://10.69.1.10:8547
2019.03.04:07:37:05.954: GPU1 GPU1: Starting up... (0)
2019.03.04:07:37:05.954: GPU1 GPU1: Generating ethash light cache for epoch #72
2019.03.04:07:37:06.153: main GPU1: 43C 33%
2019.03.04:07:37:07.040: GPU1 Light cache generated in 1.1 s (23.0 MB/s)
2019.03.04:07:37:07.360: eths Eth: New job #3bbc6801 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:07.557: GPU1 GPU1: Allocating DAG for epoch #72 (1.56) GB
2019.03.04:07:37:07.559: GPU1 GPU1: Allocating light cache buffer (25.0) MB; good for epoch up to #72
2019.03.04:07:37:07.682: GPU1 GPU1: Generating DAG for epoch #72
2019.03.04:07:37:09.313: GPU1 GPU1: DAG  16%
2019.03.04:07:37:10.371: eths Eth: New job #b53c3d01 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:10.930: GPU1 GPU1: DAG  34%
2019.03.04:07:37:10.958: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:12.542: GPU1 GPU1: DAG  53%
2019.03.04:07:37:13.385: eths Eth: New job #e9bee5d8 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:14.159: GPU1 GPU1: DAG  72%
2019.03.04:07:37:15.771: GPU1 GPU1: DAG  91%
2019.03.04:07:37:15.969: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:16.310: GPU1 GPU1: DAG generated in 8.6 s (185.4 MB/s)
2019.03.04:07:37:19.221: eths Eth: New job #c9a57953 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:20.980: main Eth speed: 13.738 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:22.237: eths Eth: New job #5a97fd50 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:25.991: main Eth speed: 13.455 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:30.998: main Eth speed: 13.395 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:33.290: eths Eth: New job #15d1a238 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:34.005: main GPU1: 52C 33%
2019.03.04:07:37:36.009: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:39.322: eths Eth: New job #def4241f from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:41.020: main Eth speed: 13.274 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:44.348: eths Eth: New job #91a13849 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:46.031: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:51.037: main *** 0:00 *** 3/4 07:37 **************************************
2019.03.04:07:37:51.037: main Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
2019.03.04:07:37:51.037: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.03.04:07:37:51.037: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.03.04:07:37:51.037: main Eth: Average speed (5 min): 13.326 MH/s
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:56.049: main Eth speed: 13.276 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:56.650: main Stratum thread not responsive for 51 s
2019.03.04:07:37:56.958: wdog Thread(s) not responding. Restarting.
lesjokolat
Jr. Member
*
Offline Offline

Activity: 117
Merit: 3


View Profile
March 04, 2019, 04:29:01 PM
 #3044

For AMD

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 2345678 -acm -clKernel 2 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

For Nvidia

Code:
PhoenixMiner -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 1345 -gpureset 1 -rmode 2 -log 0 -wal $wallet -worker $worker

is geth running on same machine?

can you add -v 3 to the command line its for more verbose output.


geth is on a different machine.

-v only prints version and exits - doesn't enable verbose.  -log 2 is supposed to enable debug messages, but doesn't really appear any different.  Here's a full log with -log 2

So same thing here - why is it monitoring a stratum thread and rebooting because of it if we are not using stratum.  Seems like a pretty clear bug to me.

Code:
2019.03.04:07:37:05.759: main Phoenix Miner 4.1c Linux/gcc - Release build
2019.03.04:07:37:05.759: main Cmd line: -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -nvidia -gpus 6 -gpureset 1 -rmode 2 -log 0 -wal address_redacted -worker m01n6 -log 2
2019.03.04:07:37:05.887: main CUDA version: 10.0, CUDA runtime: 8.0
2019.03.04:07:37:05.902: main Available GPUs for mining:
2019.03.04:07:37:05.902: main GPU1: GeForce GTX 1060 6GB (pcie 16), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2019.03.04:07:37:05.905: main NVML library initialized
2019.03.04:07:37:05.952: main Nvidia driver version: 415.27
2019.03.04:07:37:05.953: main Eth: the pool list contains 1 pool (1 from command-line)
2019.03.04:07:37:05.953: main Eth: primary pool: http://10.69.1.10:8547
2019.03.04:07:37:05.953: main Starting GPU mining
2019.03.04:07:37:05.953: main Eth: Connecting to http://10.69.1.10:8547 (GetWork/Solo)
2019.03.04:07:37:05.953: wdog Starting watchdog thread
2019.03.04:07:37:05.954: eths Eth: New job #ec69b6c7 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:05.954: eths Eth: Connected to ethash pool http://10.69.1.10:8547
2019.03.04:07:37:05.954: GPU1 GPU1: Starting up... (0)
2019.03.04:07:37:05.954: GPU1 GPU1: Generating ethash light cache for epoch #72
2019.03.04:07:37:06.153: main GPU1: 43C 33%
2019.03.04:07:37:07.040: GPU1 Light cache generated in 1.1 s (23.0 MB/s)
2019.03.04:07:37:07.360: eths Eth: New job #3bbc6801 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:07.557: GPU1 GPU1: Allocating DAG for epoch #72 (1.56) GB
2019.03.04:07:37:07.559: GPU1 GPU1: Allocating light cache buffer (25.0) MB; good for epoch up to #72
2019.03.04:07:37:07.682: GPU1 GPU1: Generating DAG for epoch #72
2019.03.04:07:37:09.313: GPU1 GPU1: DAG  16%
2019.03.04:07:37:10.371: eths Eth: New job #b53c3d01 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:10.930: GPU1 GPU1: DAG  34%
2019.03.04:07:37:10.958: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:12.542: GPU1 GPU1: DAG  53%
2019.03.04:07:37:13.385: eths Eth: New job #e9bee5d8 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:14.159: GPU1 GPU1: DAG  72%
2019.03.04:07:37:15.771: GPU1 GPU1: DAG  91%
2019.03.04:07:37:15.969: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:16.310: GPU1 GPU1: DAG generated in 8.6 s (185.4 MB/s)
2019.03.04:07:37:19.221: eths Eth: New job #c9a57953 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:20.980: main Eth speed: 13.738 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:22.237: eths Eth: New job #5a97fd50 from http://10.69.1.10:8547; diff: 15570670MH
2019.03.04:07:37:25.991: main Eth speed: 13.455 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:30.998: main Eth speed: 13.395 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:33.290: eths Eth: New job #15d1a238 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:34.005: main GPU1: 52C 33%
2019.03.04:07:37:36.009: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:39.322: eths Eth: New job #def4241f from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:41.020: main Eth speed: 13.274 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:44.348: eths Eth: New job #91a13849 from http://10.69.1.10:8547; diff: 15555465MH
2019.03.04:07:37:46.031: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:51.037: main *** 0:00 *** 3/4 07:37 **************************************
2019.03.04:07:37:51.037: main Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
2019.03.04:07:37:51.037: main Eth speed: 13.275 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:51.037: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.03.04:07:37:51.037: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.03.04:07:37:51.037: main Eth: Average speed (5 min): 13.326 MH/s
2019.03.04:07:37:51.037: main  
2019.03.04:07:37:56.049: main Eth speed: 13.276 MH/s, shares: 0/0/0, time: 0:00
2019.03.04:07:37:56.650: main Stratum thread not responsive for 51 s
2019.03.04:07:37:56.958: wdog Thread(s) not responding. Restarting.

In a command line see if geth is truly set to mine:

geth --rpc --rpcapi eth --rpcaddr IPADDR --rpcport YOURPORT --mine --miner.etherbase <the-eth-address-where-you-want-to-credit-your-rewards> console


Ok so it is supposed to be supported protocal so try one of these 3 things:

ADD -G see if it will trigger the getwork method.

Claymore command:
-mode 1

Phoenix command:
-gwtime 200 (Recheck period for Solo/GetWork mining default: 200 ms)

see if any of these help.
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 04, 2019, 08:21:51 PM
Last edit: March 04, 2019, 08:43:23 PM by puithove
 #3045

In a command line see if geth is truly set to mine:

geth --rpc --rpcapi eth --rpcaddr IPADDR --rpcport YOURPORT --mine --miner.etherbase <the-eth-address-where-you-want-to-credit-your-rewards> console


Ok so it is supposed to be supported protocal so try one of these 3 things:

ADD -G see if it will trigger the getwork method.

Claymore command:
-mode 1

Phoenix command:
-gwtime 200 (Recheck period for Solo/GetWork mining default: 200 ms)

see if any of these help.

Thanks, but still no.

Geth is truly ready to mine.  I'm using ethminer against it and successfully mining blocks.  In fact, PhoenixMiner starts mining with it before it craps out due to the stratum thread error - so it's not an issue with being able to get work with eth_getwork (refer to log posted above)

Had previously tried -gwtime - no change

-G is invalid option for PhoenixMiner

-mode 1 - no change

PhoenixMiner is not an option currently.
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
March 04, 2019, 11:04:55 PM
 #3046

Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
ManDoneKTM
Newbie
*
Offline Offline

Activity: 150
Merit: 0


View Profile
March 06, 2019, 03:52:04 AM
 #3047

Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
why you would use pm with newest drivers ? you will have the same results in hashrate ... ffs
UnclWish
Sr. Member
****
Offline Offline

Activity: 1484
Merit: 253


View Profile
March 06, 2019, 04:43:24 AM
 #3048

Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
why you would use pm with newest drivers ? you will have the same results in hashrate ... ffs

I didn't want to use old drivers for one miner. With support of new drivers PM works faster. Without support of drivers PM gives many rejected shares and speed is lower cause of impossibility of using new and 3rd kernels.
Joncatch
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
March 06, 2019, 05:32:34 AM
 #3049

Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
why you would use pm with newest drivers ? you will have the same results in hashrate ... ffs



Not really; they also said that the newest miner is not optimized for newer cards like the nvidia 2070's .. also the new Radeon VII is a beast and im sure they could get over 100mhs with optimized miner configs. I also noticed the newest version is not as stable as 3.5 was I crash regularly, especialyl with my two mixed nvidia/amd rigs.
biospb
Newbie
*
Offline Offline

Activity: 64
Merit: 0


View Profile
March 06, 2019, 03:59:38 PM
 #3050

What about ZIL support for dual mine (switching when time is come) ?
justoiurii
Newbie
*
Offline Offline

Activity: 103
Merit: 0


View Profile
March 07, 2019, 06:17:10 AM
 #3051

6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)
hustleman
Jr. Member
*
Offline Offline

Activity: 154
Merit: 6


View Profile
March 07, 2019, 06:57:02 AM
 #3052

6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)

Are you running windows?  Do you have the window defender running?  if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it. 
justoiurii
Newbie
*
Offline Offline

Activity: 103
Merit: 0


View Profile
March 07, 2019, 08:02:24 AM
 #3053

6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)

Are you running windows?  Do you have the window defender running?  if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it. 

Thanks, but it doesn't help(
hustleman
Jr. Member
*
Offline Offline

Activity: 154
Merit: 6


View Profile
March 07, 2019, 02:27:30 PM
 #3054

6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)

Are you running windows?  Do you have the window defender running?  if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it. 

Thanks, but it doesn't help(

Sorry did you may have to disable defender thru registry, delete the current version of PhxM you have and download a new version of PhxM before this may work. 
Karlitosss
Jr. Member
*
Offline Offline

Activity: 150
Merit: 3


View Profile
March 07, 2019, 10:00:59 PM
 #3055

What is the best AMD drivers for windows 10. Since new Phoenix Miner, I get all sort of issues. My rigs used to never reboot, even after 40days+ stable. And now they reboot every 7 hours. Sometime a card is also disconnected

Can we use same BIOSes for mining ETH with RX (polaris) cards?
Guigs321
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
March 08, 2019, 11:49:28 AM
 #3056

What is the best AMD drivers for windows 10. Since new Phoenix Miner, I get all sort of issues. My rigs used to never reboot, even after 40days+ stable. And now they reboot every 7 hours. Sometime a card is also disconnected

Can we use same BIOSes for mining ETH with RX (polaris) cards?

I don't if they are the best but I have absolutely no issue on 3 RIGs with 18.3.4
justoiurii
Newbie
*
Offline Offline

Activity: 103
Merit: 0


View Profile
March 08, 2019, 06:59:36 PM
 #3057

6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)

Are you running windows?  Do you have the window defender running?  if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it. 

Thanks, but it doesn't help(

Sorry did you may have to disable defender thru registry, delete the current version of PhxM you have and download a new version of PhxM before this may work. 

I've done all as you sad but with no results( Thanks any way. Next step - upgrade GPU drivers or going on with Claymore
hobocoe
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
March 09, 2019, 03:38:23 AM
Last edit: March 09, 2019, 05:25:31 PM by hobocoe
 #3058

Im running MSOS (ubuntu 16.04, 4.15.0 kernel, 17.5 amd driver) and ever since the ETH upgrade I have had 10 times the amount of stale and invalid shares at the pool. I tried everything including dialing back the OC/UV settings and nothing could get my previous stability back. No mater what I tried it was always 5% stales and 1% invalid shares (normal was 0.5% or less stales and a random invalid every so often). I switched to claymore and while its running at a slower hash Im getting a way higher overall usable hashrate and little to no stales/ invalid. this is only at the pool side the miner side shows way less stales and invalids than what the pool shows. Im thinking this is a linux only issue as my windows rig running 4.1c is fine no unusual stales or invalids, and the linux/MSOS rig running claymore is fine but phoenix on linux/MSOS is just trash on stability now.... If you got any tricks to fix it let me know if not maybe its something you guys can look into on the next release?
thanks for any help
puithove
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
March 10, 2019, 05:35:01 PM
 #3059

I'm having the same issue.  I'm mining Callisto (CLO).  I had been using Parity with its built-in stratum support, but since they have not updated their Parity client (rust-callisto) for last week's hard fork, I tried to switch to Geth, which doesn't have stratum - thus needing to switch to the RPC interface for get_work.  This is where the issue comes in.

I am setting the coin on the commandline.

I tried setting a "password' in commandline as suggested above, but that doesn't make a difference.  Over the past few days, I've also tried as many other options as I can.  It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.

See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.

Code:
*** 0:00 *** 3/3 08:18 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 41.982 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.004 MH/s
 
Eth: New job #fec49625 from http://10.69.1.10:8547; diff: 14108624MH
Eth: New job #585617fa from http://10.69.1.10:8547; diff: 14115512MH
Eth speed: 41.946 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e9d5c9cf from http://10.69.1.10:8547; diff: 14115512MH
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.

@PhoenixMiner are you out there?
ManDoneKTM
Newbie
*
Offline Offline

Activity: 150
Merit: 0


View Profile
March 11, 2019, 10:03:59 PM
 #3060

I'm having the same issue.  I'm mining Callisto (CLO).  I had been using Parity with its built-in stratum support, but since they have not updated their Parity client (rust-callisto) for last week's hard fork, I tried to switch to Geth, which doesn't have stratum - thus needing to switch to the RPC interface for get_work.  This is where the issue comes in.

I am setting the coin on the commandline.

I tried setting a "password' in commandline as suggested above, but that doesn't make a difference.  Over the past few days, I've also tried as many other options as I can.  It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.

See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.

Code:
*** 0:00 *** 3/3 08:18 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 41.982 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.004 MH/s
 
Eth: New job #fec49625 from http://10.69.1.10:8547; diff: 14108624MH
Eth: New job #585617fa from http://10.69.1.10:8547; diff: 14115512MH
Eth speed: 41.946 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e9d5c9cf from http://10.69.1.10:8547; diff: 14115512MH
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.

@PhoenixMiner are you out there?
He always responde in time ... but something weird is happening ... idk what ....
Pages: « 1 ... 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 [153] 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 ... 502 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!