-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The node service is running normally, but the RPC cannot be accessed, and an error is reported #3220
Comments
It was available before, but it suddenly became unavailable, I don’t know what’s going on? EXCHAIN V1.7.0 |
@danny-dudu OKTC mainnet? Could you paste more logs? |
@danny-dudu Please help run |
I am running under screen, because I need to switch back and forth between the running of the monitoring node service, does it have something to do with this? |
OKTC mainnet |
|
i am running cmd <dmesg -T>, msg is as follows [Thu Jul 6 06:34:52 2023] KERNEL supported cpus: |
I think re-node should fix this, but it's not an optimal solution |
It seems the node is not killed by system. Could you share your start command? |
@danny-dudu Yes,and how long the node has been running |
1.first create screen like this 2.enter the screen and run start cmd like this |
root 2031 2022 34 Jul06 pts/2 4-18:54:14 exchaind start --home /data/exchaind it look like a long time |
Could you show more logs like this? |
Is there any panic logs? or stack logs? |
The node is running normally, but the RPC communication interaction cannot be performed. |
There is almost no error log or stack information, I can reproduce some for you, like this I[2023-07-20|04:57:50.470][2031] Height<20939033>, Tx<5>, BlockSize<6189>, BTInterval<3925ms>, LastBlockTime<3800ms>, GasUsed<484847>, InvalidTxs<0>, lastRun<8ms>, ApplyBlock<ApplyBlock<14ms>, abci<0ms>, persist<12ms>, mpUpdate<0ms>, SaveState<0ms>>, Prerun<1>, MempoolTxs<12>, Workload<0.01|0.01|0.01|0.01>, persistDetails<preChange<8ms>, flushCache<2ms>, commitStores<1ms>, flushMeta<0ms>>, Iavl[getnode<2267>, rdb<12>, rdbTs<7ms>, savenode<0>], DeliverTxs[RunAnte<0ms>, RunMsg<3ms>, refund<0ms>]. module=main |
I got the point, I will try to reproduce this situation. and If the node is still running with invalid RPC, could you please run then send the file to me? |
give email, thanks, i send to u file |
i sent to u already, [email protected] |
Hi @danny-dudu , |
E[2023-07-20|03:58:00.139][2031] Failed to read request. module=rpc-server protocol=websocket remote=157.245.40.246:56390 err="websocket: close 1006 (abnormal closure): unexpected EOF"
The text was updated successfully, but these errors were encountered: