Skip to content
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

[Bug]: XMR node connection failure AFTER Synching #5985

Closed
1 task done
mbcr opened this issue May 16, 2024 · 2 comments
Closed
1 task done

[Bug]: XMR node connection failure AFTER Synching #5985

mbcr opened this issue May 16, 2024 · 2 comments

Comments

@mbcr
Copy link

mbcr commented May 16, 2024

What is your BTCPay version?

Version: v1.13.1+ca55e1f30 (Altcoins)

How did you deploy BTCPay Server?

Docker

What happened?

After a few days synching the XMR node (with correct block progress report), when the synching was supposed to be completed, the node synching status report fails to load and the node doesn't connect.
The "Your nodes are synching" reads:
Node available: False
Wallet available: False
Last updated: 01/01/0001 00:00:00
Synced: False (0 / 0)
whereas previously the synced reported the correct block numbers missing for complete sync.
image

How did you encounter this bug?

  1. Installed node with Docker, selecting BTC and XMR as enabled coins
  2. After installation, synching started for both coins
  3. I disabled BTC to focus server resources on the XMR synching process first
  4. I deleted the BTC node docker images and rerun the install so XMR was the first crypto
  5. The server was running properly, with the Synching report working
  6. When the synching process was supposed to have finished, the status report fails to load, and the node is offine

Relevant log output

Logs from restarting the server using the "btcpay-restart.sh" script:

2024-05-16 13:38:27.250 +00:00 [INF] DelayedTransactionBroadcasterHostedService successfully exited...
2024-05-16 13:38:27.253 +00:00 [INF] TorServices successfully exited...
2024-05-16 13:38:27.257 +00:00 [INF] CheckConfigurationHostedService successfully exited...
2024-05-16 13:38:27.280 +00:00 [INF] PullPaymentHostedService successfully exited...
2024-05-16 13:38:51.726 +00:00 [INF] NBXplorerListener successfully exited...
2024-05-16 13:38:51.749 +00:00 [INF] LightningListener successfully exited...
2024-05-16 13:38:51.752 +00:00 [INF] LightningPendingPayoutListener successfully exited...
2024-05-16 13:38:51.763 +00:00 [INF] Stop watching invoices
2024-05-16 13:38:51.843 +00:00 [INF] RatesHostedService successfully exited...
2024-05-16 13:38:51.852 +00:00 [INF] DynamicDnsHostedService successfully exited...
2024-05-16 13:38:51.856 +00:00 [INF] DbMigrationsHostedService successfully exited...
2024-05-16 13:39:02.193 +00:00 [INF] Root Path: /
2024-05-16 13:39:05.187 +00:00 [INF] Starting listening Monero-like daemons (XMR)
2024-05-16 13:39:05.439 +00:00 [INF] SSH settings detected, testing connection to root@host.docker.internal on port 22 ...
2024-05-16 13:39:05.700 +00:00 [INF] Checking if any payment arrived on lightning while the server was offline...
2024-05-16 13:39:05.834 +00:00 [INF] SSH connection succeeded
2024-05-16 13:39:06.132 +00:00 [INF] Processing lightning payments...
2024-05-16 13:39:06.351 +00:00 [INF] Start watching invoices
2024-05-16 13:39:06.478 +00:00 [INF] Starting payment request expiration watcher
2024-05-16 13:39:06.598 +00:00 [INF] 0 pending payment requests being checked since last run
2024-05-16 13:40:45.336 +00:00 [INF] XMR just became unavailable

What browser do you use?

Firefox 125.0.2 (64-bit)

Additional information

No response

Are you sure this is a bug report?

  • I confirm this is a bug report
@mbcr
Copy link
Author

mbcr commented May 18, 2024

After coming back to the server 2 days later, the situation has been resolved on its own.
The interface now shows "Node available: True".
I'm guessing the server remains temporarily in an intermediary state between finishing the synching/downloading the blockchain and becoming available on the web interface. This temporary phase is not displayed correctly in the user interface, which led to the lack of connection earlier. This lasted at the very least a few hours.

Unfortunately, I was busy with other activities, so I can't say with certainty how long that phase lasted. I'm just writing to report that at the 2 days mark, the server was fully operational.

@mbcr mbcr closed this as completed May 18, 2024
@chaosyoga
Copy link

i also just experienced this when at the very tail end of syncing my monero node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants