Bitcoin Forum
May 08, 2024, 01:41:59 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Gridseed blade error  (Read 326 times)
Sir William (OP)
Member
**
Offline Offline

Activity: 128
Merit: 11


View Profile
March 05, 2017, 03:17:44 AM
 #1

   I'm getting the following error on a gridseed blade.  "Error 111 connecting to 127.0.0.1:6379. Connection refused."  Any idea how to fix this???

There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715132519
Hero Member
*
Offline Offline

Posts: 1715132519

View Profile Personal Message (Offline)

Ignore
1715132519
Reply with quote  #2

1715132519
Report to moderator
1715132519
Hero Member
*
Offline Offline

Posts: 1715132519

View Profile Personal Message (Offline)

Ignore
1715132519
Reply with quote  #2

1715132519
Report to moderator
1715132519
Hero Member
*
Offline Offline

Posts: 1715132519

View Profile Personal Message (Offline)

Ignore
1715132519
Reply with quote  #2

1715132519
Report to moderator
JaredKaragen
Legendary
*
Offline Offline

Activity: 1848
Merit: 1165


My AR-15 ID's itself as a toaster. Want breakfast?


View Profile WWW
March 05, 2017, 07:21:06 AM
 #2

provide more info;  such as blade model/type, configuration and version of what miner you are running.

This will help you get a better answer from me than this one.

Link to my batch and script resources here.  

DO NOT TRUST YOBIT  -JK

Donations: 1Q8HjG8wMa3hgmDFbFHC9cADPLpm1xKHQM
Sir William (OP)
Member
**
Offline Offline

Activity: 128
Merit: 11


View Profile
March 05, 2017, 09:27:44 AM
 #3

Thanks for replying.  I'll answer what I can?  I bought this second hand.  This is a dual blade model.  Was there more than the single and dual blade gridseeds?  I am not aware of any, but that doesn't mean much.  I have a 500 watt PS (I'll have to check the brand/quality, when I get home), it is the only item plugged into it.  I'm using the latest BFGMiner.  The batch file I'm using to run it is below:

Code:

bfgminer --scrypt -S gridseed:all --set-device gridseed:clock=825 -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub/#skipcbcheck -u (wallet address) -p 1
::pause


One thing of note, that I just thought of.  I am on WiFi.  I have no choice but to run on WiFi, as my roommate won't let me run an ethernet cable.  I usually don't have dropouts, but do occasionally.  I could browse the internet, at the time, but it was slow.  Could this explain the error?  I've been running this rig for a few months without difficulty, until now.

JaredKaragen
Legendary
*
Offline Offline

Activity: 1848
Merit: 1165


My AR-15 ID's itself as a toaster. Want breakfast?


View Profile WWW
March 05, 2017, 09:44:05 PM
 #4

Thanks for replying.  I'll answer what I can?  I bought this second hand.  This is a dual blade model.  Was there more than the single and dual blade gridseeds?  I am not aware of any, but that doesn't mean much.  I have a 500 watt PS (I'll have to check the brand/quality, when I get home), it is the only item plugged into it.  I'm using the latest BFGMiner.  The batch file I'm using to run it is below:

Code:

bfgminer --scrypt -S gridseed:all --set-device gridseed:clock=825 -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub/#skipcbcheck -u (wallet address) -p 1
::pause


One thing of note, that I just thought of.  I am on WiFi.  I have no choice but to run on WiFi, as my roommate won't let me run an ethernet cable.  I usually don't have dropouts, but do occasionally.  I could browse the internet, at the time, but it was slow.  Could this explain the error?  I've been running this rig for a few months without difficulty, until now.

check ebay;  there's a few different blade configs.  some came out of larger machines with multiple blades.


Try without the /# commands on the stratum port.


I always used:   stratum+tc....com:4444#xnsub on my antminers;  never a / before the #.   I did not know about the second # tag; just leave them both out for now and no slash after URL/port.


FYI, if you have good cooling and a good power supply;  I ran my orbs and blades at 1000Mhz stable.  I just used MinerA on a Pi to control them and it would auto-reboot if a miner went dead.   The LightningAsic rom for the Wiibox also had this feature, and an auto-overclock feature.

Link to my batch and script resources here.  

DO NOT TRUST YOBIT  -JK

Donations: 1Q8HjG8wMa3hgmDFbFHC9cADPLpm1xKHQM
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!