h9-dev / chia-miner

The miner for Chia.
https://www.h9.com
225 stars 40 forks source link

HPool-Miner-chia-v1.4.0-2-arm cannot connect #535

Open terencelcc opened 3 years ago

terencelcc commented 3 years ago

Hi, I am try to run V1.4.0.2 ARM with my Raspberry Pi 4 mode B running 64 BitUbuntu 21.04. I got this error:

time="2021-05-31T21:28:24+08:00" level=error msg="update line fail" error="Get \"http://chia-15116df3dd.hpool.cn/proxy/wslines\": dial tcp: lookup chia-15116df3dd.hpool.cn: device or resource busy" f7="{loggers.go,logging.CPrint,156}" f8="{manager.go,line.(*Manager).update,125}" f9="{manager.go,line.NewManager,43}" tid=1

Is this version not support Raspberry Pi 4?

zhugcx commented 3 years ago

same issue

yuntk commented 3 years ago

i have same issue....

1nameman1 commented 3 years ago

trying 1.4.0.2 on Pi with ubuntu and getting fatal error: unexpected signal during runtime execution

ddaileyc commented 3 years ago

Same issue, when trying to run, when running the ./hpool-chia-miner-linux-arm64 & I see:

fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x1 addr=0xa084f60 pc=0xffff6dda09c0]

The nohup.out file says the following: farmer@farmer-desktop:~/Desktop/HPool-Miner$ tail -f nohup.out /usr/local/go/src/net/cgo_unix.go:218 +0x40 fp=0x400013dfb0 sp=0x400013df10 pc=0x571cf0 created by net.cgoLookupIP /usr/local/go/src/net/cgo_unix.go:228 +0x98 [signal SIGSEGV: segmentation violation code=0x1 addr=0x62 pc=0xffff8677f2ec]

runtime stack: runtime.throw(0x97c280, 0x2a) /usr/local/go/src/runtime/panic.go:1117 +0x54 runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:718 +0x29c

Would really appreciate it if this got fixed.

jorgefuertes commented 3 years ago

Same "device or resource busy" on Pi3 and Ubuntu 21.04.

yassien2000 commented 3 years ago

Did anyone get this issue figured out?

behrendsr commented 3 years ago

Same issue over here...

time="2021-06-06T02:20:27-03:00" level=error msg="update line fail" error="Get \"http://chia-15116df3dd.hpool.cn/proxy/wslines\": dial tcp: lookup chia-15116df3dd.hpool.cn: device or resource busy" f7="{loggers.go,logging.CPrint,156}" f8="{manager.go,line.(*Manager).update,125}" f9="{timer.go,utils.StartTime.func1,26}" tid=27
time="2021-06-06T02:20:28-03:00" level=error msg="update line fail" error="Get \"http://chia-0df3c2fd4e.hpool.xin/proxy/wslines\": dial tcp: lookup chia-0df3c2fd4e.hpool.xin: device or resource busy" f7="{loggers.go,logging.CPrint,156}" f8="{manager.go,line.(*Manager).update,125}" f9="{timer.go,utils.StartTime.func1,26}" tid=27
time="2021-06-06T02:20:29-03:00" level=error msg="update line fail" error="Get \"https://chia-1bca46b45f.hpool.com/proxy/wslines\": dial tcp: lookup chia-1bca46b45f.hpool.com: device or resource busy" f7="{loggers.go,logging.CPrint,156}" f8="{manager.go,line.(*Manager).update,125}" f9="{timer.go,utils.StartTime.func1,26}" tid=27
time="2021-06-06T02:20:30-03:00" level=error msg="update line fail" error="Get \"https://chia-e365767716.hpool.com/proxy/wslines\": dial tcp: lookup chia-e365767716.hpool.com: device or resource busy" f7="{loggers.go,logging.CPrint,156}" f8="{manager.go,line.(*Manager).update,125}" f9="{timer.go,utils.StartTime.func1,26}" tid=27
time="2021-06-06T02:20:31-03:00" level=error msg="update line fail" error="Get \"https://chia.hpool.com/proxy/wslines\": dial tcp: lookup chia.hpool.com: device or resource busy" f7="{loggers.go,logging.CPrint,156}" f8="{manager.go,line.(*Manager).update,125}" f9="{timer.go,utils.StartTime.func1,26}" tid=27
Zeefars commented 3 years ago

I have the same issue :( Trying on Ubuntu on Raspberry Pi 4.

did anyone manage to work this out?

spencecopper commented 3 years ago

Buhler?

spencecopper commented 3 years ago

Okay so here is how to fix this... Stracing the process it opens the following files on boot:

/etc/nsswitch.conf
/etc/resolv.conf
/etc/nsswitch.conf
/etc/host.conf
/etc/resolv.conf

Presumably to figure out what it should do for DNS and something about the setup of DNS in the prebaked ubuntu install for raspberry pi is causing issues. Usually I can do something such as touching the files above and that kicks the DNS portion of the OS back to life, however the rest of the processes using DNS on the OS are happy so it's something specific about the hpool miner.

Anyways.... To fix the issue disable systemd-resolved and reconfigure resolv.conf

sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved
rm -f /etc/resolv.conf && vim /etc/resolv.conf

Insert you favorite name servers to /etc/resolv.conf ex.

nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 8.8.4.4
nameserver 2.2.2.2

Restart the hpool miner and you should be good.

aiesst commented 3 years ago

Okay so here is how to fix this... Stracing the process it opens the following files on boot:

/etc/nsswitch.conf
/etc/resolv.conf
/etc/nsswitch.conf
/etc/host.conf
/etc/resolv.conf

Presumably to figure out what it should do for DNS and something about the setup of DNS in the prebaked ubuntu install for raspberry pi is causing issues. Usually I can do something such as touching the files above and that kicks the DNS portion of the OS back to life, however the rest of the processes using DNS on the OS are happy so it's something specific about the hpool miner.

Anyways.... To fix the issue disable systemd-resolved and reconfigure resolv.conf

sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved
rm -f /etc/resolv.conf && vim /etc/resolv.conf

Insert you favorite name servers to /etc/resolv.conf ex.

nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 8.8.4.4
nameserver 2.2.2.2

Restart the hpool miner and you should be good.

niubi