Claymore-Dual / Claymore-Dual-Miner

Download Ethereum Miner (Updated 2020)
Other
290 stars 77 forks source link

what(): Type is not convertible to string #44

Open dgets opened 3 years ago

dgets commented 3 years ago

I have recently begun attempting to dual mine ethereum & lbry with the Claymore-Dual-Miner. Unfortunately, I'm receiving the following error when trying to run the miner with the following command line:

command line: ethdcrminer64 -epool us-east.ethash-hub.miningpoolhub.com:20535 -ewal xxx.desktopBOX -epsw x -mode 0 -dbg -1 -mport 0 -etha 0 -ftime 55 -retrydelay 1 -tt 79 -ttli 77 -tstop 89 -esm 2 -dpool stratum+tcp://us-east.luxor.tech:5555 -dcoin lbc -dwal xxx.desktopBOX -dpsw xxx error:

Phoenix Miner 5.2e Linux/gcc - Release build
--------------------------------------------

CUDA version: 9.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 1080 (pcie 1), CUDA cap. 6.1, 7.9 GB VRAM, 20 CUs
Nvidia driver version: 390.138
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: us-east.ethash-hub.miningpoolhub.com:20535
B2S: the pool list contains 1 pool (1 from command-line)
B2S: primary pool: us-east.luxor.tech:5555
Starting GPU mining
Eth: Connecting to ethash pool us-east.ethash-hub.miningpoolhub.com:20535 (proto: Stratum)
B2S: Connecting to blake2s pool us-east.luxor.tech:5555 (proto: Stratum)
GPU1: 47C 21% 45W
GPUs power: 44.8 W
Eth: Connected to ethash pool us-east.ethash-hub.miningpoolhub.com:20535 (18.204.40.75)
B2S: Connected to blake2s pool us-east.luxor.tech:5555 (35.202.11.182)
Eth: Subscribed to ethash pool
B2S: Subscribed to blake2s pool
terminate called after throwing an instance of 'dCKjmhGUOw4Xr7kZbmZ'
  what():  Type is not convertible to string
/home/sprite/bin/claymore-dualmining.sh: line 1: 185053 Aborted

Does anybody have any experience with this error or have any pointers as to what I may be doing wrong here? I would greatly appreciate any assistance that you might be able to offer!

marmartins commented 2 years ago

I faced the same error. No solution at this moment...