Second network S2 Antminer connected but not hashing

Justin Smith

On my network, I have one S2 Antminer with IP Address 192.168.168.99 that is successfully hashing at around 1000GH/sec. I added a second S2 Antminer, set up the IP Address as 192.168.168.98, achieved a successful connection with my MacBook Pro over the network, and entered the same three pool settings that are working well for my first S2. 

To my surprise, hashing does not commence. I have reseated the blades and control board and tightened the cable connections but it did not help. Pinging 192.168.168.98 shows a functioning connection. I am at a loss to try to troubleshoot this problem further and I welcome any suggestions.

Thank you,

Justin 

FabulousPanda

Is there a cgminer log on the web interface you can post?

Justin Smith

Here is the log from the second S2 obtained just after I logged in on the web:

I hope this will offer some insights.

Thank you,

Justin 

Mem: 59236K used, 451328K free, 0K shrd, 12K buff, 39360K cached

CPU:   0% usr   9% sys   0% nic  90% idle   0% io   0% irq   0% sirq

Load average: 1.00 1.02 1.05 1/65 7190

PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND

7189  7188 root     R     2148   0%   9% top -b -n 1

6925  6924 root     S    77136  15%   0% /usr/bin/cgminer --bitmain-dev /dev/bitmain-asic --bitmain-options 115200:32:8:40:196:5f06 --bitmain-checkn2diff --bitmain-hwerror --queue 8192 --api-listen --default-config /config/cgminer.conf

378     1 root     S     5980   1%   0% /usr/bin/monitor-recobtn /usr/bin/factory_config_reset.sh

331     1 root     S     3312   1%   0% /usr/bin/ntpd -p /var/run/ntp.pid -g

431   331 root     S     3312   1%   0% /usr/bin/ntpd -p /var/run/ntp.pid -g

346     1 root     S     3112   1%   0% /usr/sbin/lighttpd -f /etc/lighttpd.conf

1587     1 avahi    S     2860   1%   0% avahi-daemon: running [antMiner.local]

1588  1587 avahi    S     2728   1%   0% avahi-daemon: chroot helper

6924     1 root     S     2616   1%   0% {screen} SCREEN -S cgminer -t cgminer -m -d /usr/bin/cgminer --bitmain-dev /dev/bitmain-asic --bitmain-options 115200:32:8:40:196:5f06 --bitmain-checkn2diff --bitmain-hwerror --queue 8192 --api-listen --default-config /config/cgminer.conf

328     1 root     S     2272   0%   0% /usr/sbin/dropbear -r /config/dropbear_rsa_host_key -p 22

394     1 root     S     2148   0%   0% {minerlcd} /bin/sh /sbin/minerlcd

393     1 root     S     2148   0%   0% {monitorcg} /bin/sh /sbin/monitorcg

7188   346 root     S     2148   0%   0% /bin/sh /www/pages/cgi-bin/monitor.cgi

7190  7188 root     S     2148   0%   0% /bin/sh /www/pages/cgi-bin/monitor.cgi

6922   393 root     S     2016   0%   0% sleep 3m

7187   394 root     S     2016   0%   0% sleep 10s

391     1 root     S     1908   0%   0% /sbin/getty 115200 ttyO0

392     1 root     S     1908   0%   0% /sbin/getty 38400 tty1

1     0 root     S     1652   0%   0% init [5]

310     2 root     SW       0   0%   0% [kworker/0:2]

11     2 root     SW       0   0%   0% [watchdog/0]

10     2 root     SW       0   0%   0% [rcu_sched]

401     2 root     DW       0   0%   0% [lcd_test]

41     2 root     SW       0   0%   0% [khungtaskd]

16     2 root     SW       0   0%   0% [bdi-default]

13     2 root     SW       0   0%   0% [kdevtmpfs]

3     2 root     SW       0   0%   0% [ksoftirqd/0]

2     0 root     SW       0   0%   0% [kthreadd]

21     2 root     SW       0   0%   0% [kworker/u:1]

8     2 root     SW       0   0%   0% [migration/0]

5     2 root     SW<      0   0%   0% [kworker/0:0H]

7     2 root     SW<      0   0%   0% [kworker/u:0H]

9     2 root     SW       0   0%   0% [rcu_bh]

12     2 root     SW<      0   0%   0% [khelper]

14     2 root     SW<      0   0%   0% [netns]

17     2 root     SW<      0   0%   0% [kintegrityd]

18     2 root     SW<      0   0%   0% [kblockd]

19     2 root     SW       0   0%   0% [khubd]

20     2 root     SW       0   0%   0% [irq/86-44e0b000]

24     2 root     SW       0   0%   0% [irq/23-tps65217]

27     2 root     SW       0   0%   0% [irq/46-4819c000]

36     2 root     SW       0   0%   0% [irq/87-4802a000]

39     2 root     SW<      0   0%   0% [rpciod]

42     2 root     SW       0   0%   0% [kswapd0]

43     2 root     SW       0   0%   0% [fsnotify_mark]

44     2 root     SW<      0   0%   0% [nfsiod]

45     2 root     SW<      0   0%   0% [crypto]

48     2 root     SW<      0   0%   0% [pencrypt]

49     2 root     SW<      0   0%   0% [pdecrypt]

56     2 root     SW<      0   0%   0% [OMAP UART0]

57     2 root     SW       0   0%   0% [spi1]

60     2 root     SW       0   0%   0% [spi2]

63     2 root     SW<      0   0%   0% [kpsmoused]

64     2 root     SW       0   0%   0% [irq/150-mmc0]

76     2 root     SW<      0   0%   0% [deferwq]

77     2 root     SW       0   0%   0% [kworker/u:2]

116     2 root     SW       0   0%   0% [mmcqd/0]

290     2 root     SW<      0   0%   0% [kworker/0:1H]

1953     2 root     SW       0   0%   0% [kworker/0:1]

6929     2 root     SW<      0   0%   0% [bitmain-asic]

FabulousPanda

Ugh, that looks like the output of the linux program 'top' which just shows all the processes that are running - at the very least it seems to show that cgminer is running, but we want the logs of that to show up. Can you log in via ssh? I assume you've tried power cycling the miner to no effect?

Justin Smith

Yes, I have power cycled the miner but unfortunately it did not help. I appreciate the suggestion, however. 

I decided to try an experiment to test for some form of network conflict between the two miners as a cause for the failure to hash by #2. I disconnected the successfully hashing miner #1 from the network and I then used the known successful settings from the disconnected #1 to set up #2 which I connected to the network. 

With #1 disconnected, #2 promptly began hashing. From this I conclude that the reason that I can't get #2 to hash when #1 is connected to the network is because the two miners conflict in some way on the network, causing #2 to fail. Do you have any suggestions for how I can overcome this? To cover our home and outside areas, I have three Apple routers, one base station and two set as bridges. 

Thank you for any advice you are able to share. 

Justin 

FabulousPanda

Try a different IP address, perhaps there's a different .98 on the network?