btcpayserver
btcpayserver copied to clipboard
[Bug]: NBXplorer hangs randomly
Requires a reboot.
Maybe there's something special in that block that's bugging it out. I'll keep posting which blocks it hangs on maybe we'll see a pattern.
another one
From this issue https://github.com/btcpayserver/btcpayserver/issues/4906
https://mempool.space/block/00000000000000000004748e9800a0e9e83843bad7f659541d71ce52fb291d7a https://mempool.space/block/0000000000000000000560268dbd186dbecdd347e6dad829c10c0fd3cffb2b1a https://mempool.space/block/0000000000000000000076d6ba131ea8181fccd09f3452f07d321c8e4f4b2259
Only pattern I see is that the Weight are 3.99MB
From https://github.com/btcpayserver/btcpayserver/issues/2722
hey @nostitos I see those are all different height. You have several server and it happened to all of them like that? Did reboot worked?
Have you fixed the issue?
I fixed the issue, check out this link: https://github.com/btcpayserver/btcpayserver-docker/issues/519
same here too after a short network down:
I found NBXplorer stuck too many time, but I think it is happening only after the power down.
Closing this one since it's related to very old version of btcpay try replicating it with 1.13.3 and if you still have issues let us know and we can re-open. https://github.com/btcpayserver/btcpayserver-docker/issues/519
It hasn't happened in a while, I also consider this solved.
On Wed, Jul 3, 2024, 06:41 Pavlenex @.***> wrote:
Closing this one since it's related to very old version of btcpay try replicating it with 1.13.3 and if you still have issues let us know and we can re-open. btcpayserver/btcpayserver-docker#519 https://github.com/btcpayserver/btcpayserver-docker/issues/519
— Reply to this email directly, view it on GitHub https://github.com/btcpayserver/btcpayserver/issues/5359#issuecomment-2205762852, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALSB6ME6UIXQEAJ7HQDGJQLZKPIPNAVCNFSM6AAAAAA5LEJME6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBVG43DEOBVGI . You are receiving this because you were mentioned.Message ID: @.***>