Bitcoin Forum
May 09, 2024, 09:36:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Socket was closed by pool - nanopool - ethos claymore  (Read 360 times)
hardworker27 (OP)
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile WWW
October 20, 2017, 08:22:12 PM
 #1

Hi guys, I have been looking for a solution but I still couldn't find one that work. So my error is as follow.
I'm using ethos, 6 rx 570. I have been working with ethermine with no problem in dual mining with sia in claymore. Today I wanted to switch to nanopool but I couldn't. I got the following error:
"Socket was closed by pool"
And 0 hashrate is reported.
When I tried to mine only eth in nanopool, I cleared claymore.stub.conf, it works. So, I think the problem is my claymore conf file when dual mining. Please have a look and advice me, I'm pretty new Sad

Here is my claymore conf file:

Code:
-colors 0
-dbg -1
-esm STRATUMTYPE
-epool eth-us-east1.nanopool.org:9999
-ewal MYWALLET
-epsw x
-eworker WORKER
-allpools 1
-gser 2
-allcoins 1
-wd 0
-ethi 16
#uncomment and configure the -dpool and -dwal lines below to enable dualmining.
-mode 0
-epool eth-us-east1.nanopool.org:9999
-ewal MYWALLET
-epsw x
-dpool stratum+tcp://us-east.siamining.com:7777
-dwal MYSIAWALLET
-dpsw x
-esm 1
-mode 0
-dcoin sia
-dcri 15

And my local.conf file:

Code:
globalminer claymore
maxgputemp 85
stratumproxy enabled
proxywallet MYWALLET
proxypool1 eth-us-east1.nanopool.org:9999
proxypool2 eth-us-west1.nanopool.org:9999
flags --cl-global-work 16387 --farm-recheck 200
globalfan 66

cor 6c3bec 1180 1150 1180 1180 1180 1180
mem 6c3bec 2100 2100 2100 2100 2100 2100
vlt 6c3bec 880 880 880 880 880 880
pwr 6c3bec 5 5 5 5 5 5


Thanks very much!
1715290592
Hero Member
*
Offline Offline

Posts: 1715290592

View Profile Personal Message (Offline)

Ignore
1715290592
Reply with quote  #2

1715290592
Report to moderator
The block chain is the main innovation of Bitcoin. It is the first distributed timestamping system.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715290592
Hero Member
*
Offline Offline

Posts: 1715290592

View Profile Personal Message (Offline)

Ignore
1715290592
Reply with quote  #2

1715290592
Report to moderator
1715290592
Hero Member
*
Offline Offline

Posts: 1715290592

View Profile Personal Message (Offline)

Ignore
1715290592
Reply with quote  #2

1715290592
Report to moderator
hardworker27 (OP)
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile WWW
October 20, 2017, 08:58:24 PM
 #2

I found the solution! Just remove -esm then it works now!
Pages: [1]
  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!