Wallet Empty , Nodes running more than 5days

Nodes & Mining Problems
#1

Hi sirs,

my nodes has been running for 6 days. and my wallet still empty. can someone help me? unknown%20(1) unknown%20(2) unknown

1 Like
#2

One possible reason that you’re mining to a different address, are you sure you’re checking the right wallet address?

#3

Thanks for posting on forum so more people can help. Additional info from Discord private discussion:

  1. User is using 1-click on DO, and scp in the same wallet.dat and wallet.pswd
  2. Therefore the mining should go to the same wallet address
  3. User has ssh into all the droplets, and looked at /home/nkn/go/src/github.com/nknorg/nkn/wallet.dat. the address seems to be correct (and the same)
  4. The config.json seems to be standard without modification, and there is NO beneficiaryAddress
#4

One more update: the user has replaced wallet.dat and wallet.pswd to new wallet address on all droplets right now, and rebooted all the droplets. So debug might be a bit harder.

#5

nc: connect to 178.62.200.116 port 30003 (tcp) timed out: Operation now in progress
nc: connect to 142.93.143.93 port 30003 (tcp) timed out: Operation now in progress
nc: connect to 178.128.253.80 port 30003 (tcp) timed out: Operation now in progress
nc: connect to 178.128.99.45 port 30003 (tcp) failed: Connection refused
nc: connect to 142.93.132.49 port 30003 (tcp) failed: Connection refused
nc: connect to 104.248.151.231 port 30003 (tcp) failed: Connection refused
nc: connect to 178.128.57.253 port 30003 (tcp) timed out: Operation now in progress
nc: connect to 142.93.128.205 port 30003 (tcp) timed out: Operation now in progress
Connection to 142.93.128.153 30003 port [tcp/*] succeeded!
nc: connect to 104.248.155.184 port 30003 (tcp) failed: No route to host

I can not access 30003 port of above IPs except 142.93.128.153.
And the 142.93.128.153:30003 has no response for my RPC request

POST request: Post http://142.93.128.153:30003: read tcp 10.0.1.2:62789->142.93.128.153:30003: read: connection reset by peer
Post http://142.93.128.153:30003: read tcp 10.0.1.2:62789->142.93.128.153:30003: read: connection reset by peer

Are these nodes still online?

#6

I have the same problem
29 21
%D0%B2%D1%8B%D0%B2%D0%BE%D0%B41
77
what I missed?

#7

The NajnBLL3fmQovCFNFFJGw44tGi6aXHfHro was first appeared on network since 05/21 16:00.

Let’s more patient with them. I will continue to pursue this matter.

#8

I saw that NajnBLL3fmQovCFNFFJGw44tGi6aXHfHro dig out 3 blocks in one day with different nodes. :wink:
https://testnet.nkn.org/detail/address/NajnBLL3fmQovCFNFFJGw44tGi6aXHfHro/1