Bitcoin Forum

Gentlemen,
I need your help.

on friday last week, my R4 showed up 0 Ghs hashrate w/o any influence from outside.

I decided to reboot and look what happens.

As i see in my pool's statistics is, the R4 is full working.
But when I try to connect via IP, I get a Error connection refused. So, everything is working, but I do not have any access to the miner.
I can ping its IP successfully. IP is definitly correct.

I tried then some reboots (plug out cord off the wall). Tried some different browsers. From inside network. From outside.
Always the same result.


Does anyone have a hint on that ? Any way to fix this ? Seems like only the webaccess does not work.

Any help appreciated!

Try to ssh inside this box at least it pinged.
root/admin
Run `ps | grep [h]tt`
start it like
/usr/sbin/lighttpd -f /etc/lighttpd.conf
from command line.

Hi neonox,

thanks for your reply.

I am not firm with unix systems. What do these commands do ?

No prob, I can help you.
If you use Windows, download http://www.putty.org/ and connect to antminer ip, it will open command line session.
ps | grep [h]tt will show you processes with name *htt*
maybe it'll be a help to show full process list:
ps
lighttpd is a web server that show you pages when you open ip port 80 in browser.
Hope it helps.

Neonox great help.

I can report that i could connect to my miner.

But entering the command

ps | grep [h]tt

does nothing, while

Ps

gives a list of processes:

PID   USER     TIME   COMMAND
    1 root       0:10 init [5]
    2 root       0:00 [kthreadd]
    3 root       3:22 [ksoftirqd/0]
    5 root       0:00 [kworker/0:0H]
    6 root       0:02 [kworker/u4:0]
    7 root       9:25 [rcu_preempt]
    8 root       0:00 [rcu_sched]
    9 root       0:00 [rcu_bh]
   10 root       0:06 [migration/0]
   11 root       0:01 [watchdog/0]
   12 root       0:01 [watchdog/1]
   13 root       0:05 [migration/1]
   14 root       3:13 [ksoftirqd/1]
   16 root       0:00 [kworker/1:0H]
   17 root       0:00 [khelper]
   18 root       0:00 [kdevtmpfs]
   19 root       0:00 [kworker/u4:1]
  216 root       0:00 [writeback]
  218 root       0:00 [bioset]
  220 root       0:00 [kblockd]
  236 root       0:00 [khubd]
  251 root       0:00 [edac-poller]
  342 root       0:00 [rpciod]
  343 root       0:24 [kworker/1:1]
  353 root       0:00 [khungtaskd]
  358 root       0:00 [kswapd0]
  359 root       0:00 [fsnotify_mark]
  360 root       0:00 [nfsiod]
  957 root       2:17 [kworker/0:1]
  998 root       0:00 [xemacps]
 1013 root       0:00 [kpsmoused]
 1073 root       0:00 [deferwq]
 1095 root       1:40 [jffs2_gcd_mtd1]
 1103 root       9:12 /usr/bin/monitor-ipsig
 1188 root       0:00 [kworker/1:2]
 1222 root       0:00 /usr/sbin/dropbear -r /config/dropbear_rsa_host_key -p 22
 1234 avahi      0:00 avahi-daemon: running [Natasha.local]
 1235 avahi      0:00 avahi-daemon: chroot helper
 1265 root       0:01 single-board-test
 1270 root       0:32 /usr/bin/monitor-recobtn /usr/bin/factory_config_reset.sh
 1280 root       0:00 /sbin/getty 115200 ttyPS0
 1281 root       0:00 /sbin/getty 38400 tty1
 1282 root       0:00 {monitorcg} /bin/sh /sbin/monitorcg
 1292 root       0:00 [kworker/0:2]
 1340 root       0:00 udhcpc -b -t 10 -A 10 -x hostname Natasha -i eth0
 1346 root       0:22 /usr/bin/ntpd -p /var/run/ntp.pid -g
 1363 root       0:00 sh -c /usr/bin/bmminer --version-file /usr/bin/compile_ti
 1364 root     495:43 /usr/bin/bmminer --version-file /usr/bin/compile_time --a
 5563 root       0:00 /usr/sbin/dropbear -r /config/dropbear_rsa_host_key -p 22
10242 root       0:00 -sh
12365 root       0:00 ps
27585 root       0:00 sleep 20m
root@Natasha:~#

Can somebody interprete this ?(

the lighttpd command gives the following:

root@Natasha:~# /usr/sbin/lighttpd -f /etc/lighttpd.conf
Segmentation fault

What tf is "segmentation fault" and how can it be fixed ?

Hmm.. are you sure that your miner is mining?
I can't see process like this
{screen} SCREEN -S cgminer -t cgminer
but I have no Natasha here, just beaglebone.
edt. Ah bmminer here, ok.

Ok, look at log file: /www/logs/lighttpd.error.log
cat /www/logs/lighttpd.error.log

Can you show me disc space, it could be the reason:
df -k

2016-12-12 14:15:39: (log.c.166) server started
2016-12-12 16:28:46: (log.c.166) server started
2016-12-12 17:48:11: (log.c.166) server started
2016-12-12 19:18:03: (log.c.166) server started
2016-12-12 20:13:35: (log.c.166) server started
2016-12-12 20:48:24: (log.c.166) server started
2016-12-12 21:26:47: (log.c.166) server started
2016-12-12 22:06:32: (log.c.166) server started
2016-12-13 03:48:50: (log.c.166) server started
2017-01-21 05:35:00: (log.c.166) server started
2017-01-21 05:36:38: (log.c.166) server started
2017-02-06 11:26:04: (log.c.166) server started
2017-02-06 15:23:21: (log.c.166) server started
2017-02-06 23:26:37: (log.c.166) server started
2017-02-07 04:01:30: (log.c.166) server started
2017-03-09 15:06:29: (log.c.166) server started
2017-03-09 15:09:25: (log.c.166) server started
2017-03-09 15:13:34: (log.c.166) server started
2017-03-23 06:39:14: (log.c.166) server started
2017-03-23 06:39:46: (http_auth.c.1148) digest: auth failed for  root : wrong password, IP: 192.168.92.166
2017-03-23 06:44:18: (server.c.1546) server stopped by UID = 0 PID = 1997
2017-03-23 06:44:58: (log.c.166) server started
2017-03-27 11:26:54: (server.c.1546) server stopped by UID = 0 PID = 6895
2017-03-27 11:27:29: (log.c.166) server started
2017-03-27 11:33:32: (log.c.166) server started
2017-03-28 08:09:30: (log.c.166) server started
2017-03-28 08:11:10: (log.c.166) server started
2017-03-27 11:27:00: (log.c.166) server started
2017-03-27 12:23:54: (server.c.1546) server stopped by UID = 0 PID = 4065
2017-03-27 12:23:00: (log.c.166) server started
2017-03-27 12:23:00: (log.c.166) server started
2017-04-11 21:06:39: (server.c.1546) server stopped by UID = 0 PID = 7777

Diskspace is
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root               147456     22904    124552  16% /
devtmpfs                442264         0    442264   0% /dev

as far as i see there are no entrys from may...

So far so good.
Run this please
/usr/sbin/lighttpd -v
and
/usr/sbin/lighttpd -tf /etc/lighttpd.conf

root@Natasha:~# /usr/sbin/lighttpd -v
Segmentation fault

******

No comment. Probably everything lost ???

To reduce text walls, please use the 'code' post function, (the '#' in formatting area above)
eg.

Heh, don't panic )
run these two commands
stat /usr/sbin/lighttpd
and
which lighttpd

There is external repository opkg and we can try to update lighttpd.

root@Natasha:~# stat /usr/sbin/lighttpd
  File: /usr/sbin/lighttpd
  Size: 117720          Blocks: 230        IO Block: 4096   regular file
Device: 1f01h/7937d     Inode: 1179        Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2016-07-13 09:28:56.000000000
Modify: 2016-07-13 09:28:56.000000000
Change: 2016-07-13 09:28:56.000000000

What are these magic words mean ?)

root@Natasha:~# which lighttpd
/usr/sbin/lighttpd

It provides some basic information about this binary.
Show me your:
opkg list-installed | grep [l]ight
and
opkg status lighttpd

Ok, seems the better way for you is just reflash Natasha with a newer firmware image. And it is recommended for all Ant devices as far as I know.

root@Natasha:~# opkg list-installed | grep [l]ight
lighttpd - 1.4.32-r3.18
lighttpd-module-access - 1.4.32-r3.18
lighttpd-module-accesslog - 1.4.32-r3.18
lighttpd-module-auth - 1.4.32-r3.18
lighttpd-module-cgi - 1.4.32-r3.18
lighttpd-module-dirlisting - 1.4.32-r3.18
lighttpd-module-expire - 1.4.32-r3.18
lighttpd-module-indexfile - 1.4.32-r3.18
lighttpd-module-staticfile - 1.4.32-r3.18

and

root@Natasha:~# opkg status lighttpd
Package: lighttpd
Version: 1.4.32-r3.18
Depends: lighttpd-module-dirlisting, libpcre1 (>= 8.33), lighttpd-module-auth, lighttpd-module-cgi, lighttpd-module-expire, lighttpd-module-access, libc6 (>= 2.18), lighttpd-module-staticfile, lighttpd-module-indexfile, lighttpd-module-accesslog
Recommends: update-rc.d
Provides: lighttpd-systemd
Replaces: lighttpd-systemd
Conflicts: lighttpd-systemd
Status: install user installed
Architecture: armv7ahf-vfp-neon
Conffiles:
 /etc/lighttpd.conf a7a5b79321fbb063fe2aad1fa350ffe1
Installed-Time: 1468402192

How can I flash a firmware through SSH ?

Perhaps recommended by Bitmain, but NOT recommended by us users!
Flashing to latest firmware is always a last-resort move.
As the saying goes, " If it ain't broke... " but in this case, yes, flashing to latest is the next step once the miner can be accessed.

opkg is not Bitmain :)
https://wiki.openwrt.org/doc/techref/opkg
Upgrading packages is generally NOT recommended for most users, because a typical OpenWrt system stores the base system in a read-only SquashFS partition.

We can try at least there are no other way to solve it.

Nice question ) Possible but quite complex.

Can you run
/usr/sbin/lighttpd-angel -f /etc/lighttpd.conf

This command seems to kill a lot of pids and restarting them.

These are a few thousands...?

Command is still running

How can this be stopped ?

Have you done the IP Reporter button trick? That will reflash to a backup older version of firmware that is embedded in the R4's.
BE AWARE THAT THIS RESETS ALL SETTINGS TO A FACTORY MODE! YOU WILL NEED TO RENTER ALL THE POOL INFORMATION!

Turn off PSU.
Press and hold in the red IP Reporter button.
While holding the button in, turn on PSU.
Keep pressing the IP Reporter button for 5-7 sec after PSU is turned on.
Release the button. The miner will now flash to backup firmware.
Wait a couple minutes, find the miner on your router (will probably be assigned a new address) and re-enter your pool info.

If all works then get the latest firmware and apply it through the GUI.

@neonox
Help! How can this be stopped ?

Is there a way to break a command like the Ctrl-C thing ?

@Not Fuzzy warm

Its worth a try! I am at the moment not at the place as the miner, but this will try definitly!

@neonox

I closed the ssh session. Hope this solved the problem)

I have to leave office now.

Would be great if you support me a little by wednesday ?

Hope on your help.

Use the ps command to get the process id (PID) of this process.
kill -9 (PID)
But, I'm surprised that monitors/supervises lighttpd daemon can stop other process.
https://www.mankier.com/8/lighttpd-angel

Try to reboot, it'll restart all services
reboot

Closing ssh session will not kill daemon:)

Next time please fillow recommendation by @Not Fuzzy warm, it have more sence and less risky than patch application.

D****d, i am already out of office!

Hope its not a problem if this process runs the next two days?
Its just killing a lot of pids and restarting them.

i am back in office by wednesday only.

Problem?

Look at the pool stats, I can't see the problem from my end.

@neonox
@NotFuzzyWarm

Thanks guys for all the help provided.

I do not see the problem solved, but I definitly try the operation recommended by NotFuzzyWarm.
Will be at the miner#s place only by tuesday next week and will keep you informed.

But for general knowledge only:
How would one flash a new image with a ssh session ?

There should be a possibility, since the webinterface probably will only start the command line programs.
Correct ?

Did one try this ?

Yes, BUT(!) keep in mind:
1) procedure can be different from one version to another
2) you can get a brick until you physically flush box
3) this is just a trick and no guarantee it'll repair your box

Okay, if you read this and understand all risks:
I have no R4 around, so how it work in S5

1) look at the shell script /www/pages/cgi-bin/upgrade_clear.cgi
2) scp downloaded_image.tar.gz to R4
3) tar zxf downloaded_image.tar.gz
if you can see runme.sh - you are lucky
4) sh runme.sh
in other case you should do many wood magic described in upgrade_clear.cgi
after
else
    if [ -e /dev/mmcblk0p3 ]; then
...
fi


I uploaded lighthttpd that built for your arch
https://www.dropbox.com/s/p0pypos1y8bqfsq/lighttpd.gz?dl=0

Download it separately on r4 and try to run
/your/folder/lighttpd -v

@neonox
@NotFuzzyWarm

Gentlemen, you saved me and my miner!

Natasha is now accessible again)))) Thanks to all.

Hardware Version   4.8.1.0
Kernel Version   Linux 3.14.0-xilinx-gf387dab-dirty #38 SMP PREEMPT Fri Jun 17 20:02:51 CST 2016
File System Version   Tue Aug 9 21:00:51 CST 2016
BMminer Version   1.0.0

This is the image now active.

Is it buggy ? Or should I leave it as is ? I have also a backup from the image it was delivered with.

What image is recommended by the users ?
I have
Antminer-R4-all-201612020035-autofreq-user.tar.gz

and the all new
Antminer-R4-all-201704280718-autofreq-user-Update2UBI-NF.tar.gz

Which is the better choice ?

No bugs, that version is fine and in 2 respects, better - you should now have fan speed and frequency control back :)

The only thing you might run into is that now both boards run at the same freq. That means that the maximum speed will be limited to what the weakest board will run at vs autotune usually putting them at different speeds so each boards runs in its sweet spot.

As far as i can see now, this embedded image is really stable.

Works slightly under the hashrate of 8.7 promised. Average is 8.5-8.6 . Frequency is 600Mhz.

I think, the image which I bought the R4 with was clocked at 725, but not sure.

What I can say is, that quantity of Hw errors is down by far! was x thousand, now just a few.

What images are others using at which frequency ?

Pretty sure the original freq was ballpark of 625MHz (not 725) with 1 board no doubt being lower than the other. As for speed, I just kept setting the freq higher until the HW error rate started being over 0.002%, for 1 one of my R4's that is 606MHz and another R4 is set to 612.5MHz.

Yes, that can be true: probably it was really 625.

I had several other problems with that model, such as sudden reboots (not temperature related) and sudden stop of hashing.

This was then probably related with the frequency of 625; i do not understand why this is then the frequency factory set from Antminer.

In the end: miner is stable now and on low temps, even with slighty lower hashrate.

What would one want more ?