bitcoin core 请求拒绝响应【或者】卡死

简介: bitcoin core 请求拒绝响应【或者】卡死

日志

经过排查节点日志,发现抛出异常

tail -f debug.log

日志:

2024-02-05T05:56:26Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T05:56:26Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T05:57:40Z Saw new header hash=00000000000000000002afccf4776dcaa9f27e7c83dd04b942d892a70a0ad0b3 height=828999
2024-02-05T05:57:40Z [net] Saw new cmpctblock header hash=00000000000000000002afccf4776dcaa9f27e7c83dd04b942d892a70a0ad0b3 peer=33
2024-02-05T05:58:04Z UpdateTip: new best=00000000000000000002afccf4776dcaa9f27e7c83dd04b942d892a70a0ad0b3 height=828999 version=0x20018000 log2_work=94.711111 tx=962392046 date='2024-02-05T05:57:15Z' progress=1.000000 cache=75.6MiB(236260txo)
2024-02-05T05:58:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T05:58:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T05:58:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T05:58:04Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T05:58:45Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

异常记录

记录1

2024-02-05T06:13:24Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T06:27:32Z Saw new header hash=0000000000000000000380aa9f106ee0d0eb3ae7e0710d9562663f0d65c25de1 height=829003
2024-02-05T06:27:32Z [net] Saw new cmpctblock header hash=0000000000000000000380aa9f106ee0d0eb3ae7e0710d9562663f0d65c25de1 peer=15
2024-02-05T06:27:38Z UpdateTip: new best=0000000000000000000380aa9f106ee0d0eb3ae7e0710d9562663f0d65c25de1 height=829003 version=0x22000000 log2_work=94.711169 tx=962396874 date='2024-02-05T06:26:35Z' progress=1.000000 cache=210.9MiB(1465958txo)
2024-02-05T06:27:38Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T06:27:38Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T06:27:38Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T06:27:38Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2024-02-05T06:30:30Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:30Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:30Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:30Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:36Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:36Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:36Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:36Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting
2024-02-05T06:30:36Z WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

https://github.com/bitcoin/bitcoin/issues/29384

建议

  1. 并发开太高请求 bitcoin 节点,对你的请求性能提升非常有限。再大一点还会降速。
目录
打赏
0
0
0
0
137
分享
相关文章
IE浏览器因缓存问题未能成功向后端发送请求的几个解决办法
这段时间前后端联调,解决IE、谷歌等浏览器兼容问题,真是让人有点焦头烂额,各种奇葩问题层出不穷,旧问题刚去,新麻烦又来,其中尤其以IE浏览器缓存的问题最多。有若干次都是因为这个缓存,使得前端的请求没有实际到达后台,造成304状态码。 经过前端同事和我的各种尝试,发现有三四种办法可以针对不同的情况解决这个问题。 方法一: 在网上一搜“html设置不缓存”就会看到大部分的答案都是这个,那就是在
1585 0
多次请求后tomcat网页无法响应请求,假死【控制台始终可以正常响应】
多次请求后tomcat网页无法响应请求,假死【控制台始终可以正常响应】
462 0
多次请求后tomcat网页无法响应请求,假死【控制台始终可以正常响应】
Chrome插件实现问题之网络进程接收到URL请求后会如何解决
Chrome插件实现问题之网络进程接收到URL请求后会如何解决
如何处理页面关闭时发送HTTP请求?
在实际项目开发中,可能会遇到这样的业务问题:如何在用户离开或关闭页面时发送HTTP请求给服务端?可能有人会觉得页面都关闭了,还需要发送什么请求,完全没必要噻。但如果真有这样的业务需求落到自己的头上,那么我们应该如何来实现呢?
2371 0
如何处理页面关闭时发送HTTP请求?
【C#编程最佳实践 二十二】如何发送带有重试机制的Http请求
【C#编程最佳实践 二十二】如何发送带有重试机制的Http请求
185 0
【C#编程最佳实践 二十二】如何发送带有重试机制的Http请求
在打开网站时,HTTP请求流程是如何处理的
【8月更文挑战第20天】流程包括:构建请求(如`GET /index.html HTTP/1.1`)、检查本地缓存、获取服务器IP及端口、等待TCP连接队列、建立TCP连接、发送HTTP请求。服务器处理后返回数据与响应头,可选择保持连接开启以便后续请求重用,最后断开TCP连接。
问题排查---应用程序不在接收新请求
关键词:springboot,jstack,Arthas
154 1
LoadRunner: 脚本回放时的错误“HTTP 状态码401未授权“
本文为遇到问题后在英文网站上找到的解答,将其翻译成中文以做记录:LoadRunner:脚本回放时的错误“HTTP 状态码401未授权(当前请求需要验证用户授权)”
2009 0

热门文章

最新文章