Bitcoin Forum
May 28, 2024, 01:47:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Avalon 821 & 841 Socket connect failed => Connection refused  (Read 147 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
ccgllc (OP)
Copper Member
Full Member
***
Offline Offline

Activity: 658
Merit: 101

Math doesn't care what you believe.


View Profile
June 06, 2018, 04:36:28 PM
 #1

Woke up this morning to discover ALL my Avalons, both 821s and 841s, offline.  S9s on the same switch to the same pool are working fine.  These Avalons are spread between 3 controllers and 6 AUCs.  All have yellow lights on them.  I've tried rebooting the Pis several times - both by power cycling and soft reboots.

The cgminer API log is showing (with trivial variations):

[Firmware Version] => Avalon Firmware - 20180305
    luci: 62d814c
    cgminer: b5b497e
    cgminer-packages: 960e108
Socket connect failed => Connection refused


These machines have been working well for quite some time.

Any ideas?

Mined for a living since 2017.  Dabbled for years before that.
Linux admin since 0.96 kernel and Slackware distributions on (4) floppies...
ccgllc (OP)
Copper Member
Full Member
***
Offline Offline

Activity: 658
Merit: 101

Math doesn't care what you believe.


View Profile
June 06, 2018, 04:59:59 PM
 #2

Found it, compliments of Blokforge support asking me for screenshots...

My Avalons use Static IP addressing for the controllers.  My S9s use DHCP.  Ends up the DNS server tha Avalons were pointed too was having problems.

Mined for a living since 2017.  Dabbled for years before that.
Linux admin since 0.96 kernel and Slackware distributions on (4) floppies...
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!