8000
Skip to content

XvB may have desynced from Proxy #161

Description

@Mahobear8

OS & Version:

e.g: Windows 11, Gupaxx v2.0.0

Bug

I'm not certain the exact cause, but what I saw happen was the XvB tab listed "Currently Mining no where", and the Proxy elected to send fully to P2Pool instead.

Restarting XvB fixed the issue. I think I caught it somewhat early (I can confirm within less than 15 minutes, because the 15min avg was spiking, but not yet at the full amount), so I'm not certain whether it would've successfully self-corrected. Might be something to watch for.

Additional context

I think the logs on XvB looked normal in terms of the distributions, but I can't for sure confirm. I restarted it before I confirmed I was fully scrolled down on the logs on the tab, so I can't be certain. If relevant, I currently use the Manual XvB option, and a few minutes prior, the Proxy did briefly disconnect and correct itself. (I can't immediately be certain how long XvB was desynced like this, so it may or may not be a direct correlation.)

Additionally, as I was writing this, perhaps a separate issue, I caught it getting partially stuck (but self corrected) on P2Pool for one of the minutes. This correlated to when it calculated
Sending 0.9759423s to Local P2pool
Sending 59.02406s to XvB North America Pool

I wonder if there is perhaps an issue when it's under one second that makes it get stuck, because it ended up sending the full minute to Local P2Pool, with the XvB tab showing such, with 0s on the timer.

Or perhaps it was incidental and maybe it gets stuck generally. Difficult to determine without watching it constantly

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    0