Open kucharskim opened 2 years ago
This is from testnet
machine.
$ /data/neard/neard --version
neard (release 1.30.0-rc.2) (build 1.30.0-rc.2) (rustc 1.63.0) (protocol 57) (db 31)
..and I cannot really take status
page as it's constantly timing out:
$ time curl -m120 -sSf localhost:3030/status | jq -r .
curl: (28) Operation timed out after 120001 milliseconds with 0 bytes received
real 2m0.013s
user 0m0.046s
sys 0m0.009s
I tried even longer timeouts and no luck.
@kucharskim There are a lot of bad blocks circulating in testnet now, the behavior of status page timing out is expected. We are working on resolving the issue. During this time, I think the best option for you is to just wait. If you really need to get a node started, you can try to use a243384f434d71f853287f4dc769d15fb12fdf3d from https://github.com/near/nearcore/commits/1.30.0-rpc-patch. That should help with your issues temporarily. We will release rc.4 soon
@mzhangmzz I'm aware. What I am reporting here is process panicked. That should not happen, no matter what is going on on the chain. This can be used as DDoS.
@mzhangmzz I'm aware. What I am reporting here is process panicked. That should not happen, no matter what is going on on the chain. This can be used as DDoS.
@kucharskim Yes, definitely. We will look into the panic issue. Thank you very much for reporting!