Unauthenticated Error

[dr-bestore]

Hello, I'm encountering an issue that, each time if it's been a long time since the last successful commit, unauthenticated will be given. After that, the subsequence commits will be alright.

I checked the pool code, seems that worker is recorded after logging in. So I wonder how could it be unauthenticated since I'm already logged in and have been given a worker ID and even a job? Is there anything I missed?

Thanks!

[MoneroOcean]

This can happen when you have too high worker diff and not submitted shares for more than 10 minutes. If you have keepalive turned off, turning it on in the miner config can help with that.

…

On Tue, Apr 2, 2024 at 2:39 AM dr-bestore ***@***.***> wrote: Hello, I'm encountering an issue that, each time if it's been a long time since the last successful commit, unauthenticated will be given. After that, the subsequence commits will be alright. I checked the pool code, seems that worker is recorded after logging in. So I wonder how could it be unauthenticated since I'm already logged in and have been given a worker ID and even a job? Is there anything I missed? Thanks! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dr-bestore]

Thanks for your reply. How can I solve the first submitting unauthenticated error after login? For example, if I shutdown miner last night and launch again next morning, the first submit would be failed. Does this matter and will this result in being banned?

And btw according to the code I think unauthenticated error is given when a worker is idle too long, but the timer is reset at worker login. So I don't understand how does this error happen soon after logging in, can you help me please?

Thanks again!

[MoneroOcean]

If you can attach full miner log where I can see there errors I can likely say something more definite.

…

On Thu, Apr 4, 2024, 20:33 dr-bestore ***@***.***> wrote: Thanks for your reply. However, how can I solve the first submitting unauthenticated error after login? For example, if I shutdown miner last night and launch again next morning, the first submit would be failed. Does this matter and will this result in being banned? And btw according to the code I think unauthenticated error is given when a worker is idle too long, but the timer is reset at worker login. So I don't understand how does this error happen soon after logging in, can you help me please? Thanks again! — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIDIYFURXIZFU65IG6O5VEDY3YLSJAVCNFSM6AAAAABFTA7NWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZYG44DQMJUHA> . You are receiving this because you commented.Message ID: ***@***.***>

[dr-bestore]

yeah sure

[2024-04-03 17:42:18.389]  proxy    0.00 kH/s, shares: 0/0 +0, upstreams: 1, miners: 0 (max 0) +0/-0
[2024-04-03 17:43:18.454]  proxy    0.00 kH/s, shares: 0/0 +0, upstreams: 1, miners: 0 (max 0) +0/-0
[2024-04-03 17:44:18.521]  proxy    0.00 kH/s, shares: 0/0 +0, upstreams: 1, miners: 0 (max 0) +0/-0
[2024-04-03 17:45:18.587]  proxy    0000 rejected (0/1+0) diff 100 ip 43.27.6.119 "Unauthenticated" (9005 ms)
[2024-04-03 17:46:18.654]  net      0000 no active pools, stop
[2024-04-03 17:47:18.720]  proxy    0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 1 (max 1) +2/-1
[2024-04-03 17:48:18.786]  proxy    0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 1 (max 1) +0/-0
[2024-04-03 17:49:18.852]  proxy    11.78 kH/s, shares: 1/1 +1, upstreams: 1, miners: 1 (max 1) +0/-0

[MoneroOcean]

I hoped for more complete log that show time of previous submissions or connect time to pool.