-
Notifications
You must be signed in to change notification settings - Fork 229
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
error: "Unauthenticated", code: -1 #67
Comments
Ok, the problem persits in 2.5.1. This time the Error appeared after 7h. I mine on the same PC with a gtx960 with xmrig-nvidia. No Issues with this one... very odd.. |
Sorry was to busy yesterday. It strange, I upload version with enabled protocol debug, it verbose, because print each network packet in console, it helps understand what happen, miner sent something wrong or pool. |
In v2.5.1 was found critical bug, I remove this version and publish v2.5.2, link above updated too. |
oh ok.. |
No it can changed only in compile time, if you can't build from source, I built verbose version for you https://github.com/xmrig/xmrig-amd/releases/download/v2.5.2/xmrig-amd-2.5.2-debug-win64.zip |
Sorry for the long paste, but here it stopped:
You see, that it also got 2 jobs from th dev donate, but did not post any results... I'll put up the debug version. PS: here are the lines, when I start it:
(I put a xxx on user and pass) Not I have the debug version online - piping everything into a log file ... Maybe I have the settings for the Radeon set to hard - so it runs in some kind of buffer overflow at some point... |
Miner stop working |
hmm .. until now I am unable to reproduce this particular error in the debug version of xmrig-amd. However, the miner seems to crash without any error messages from time to time. Now I have two Radeon R9 M360 Cards. The Specs are: I am not 100% about the config: In princible is "intensity" the number of shaders (if I understood it right), "worksize" - is this some kind of package size per shader? Because when starting xmrig it shows worksize/256? #0, GPU #1 (AMD Radeon (TM) R9 M360), intensity: 500 (8/256), cu: 8 What does (8/256) mean? |
lol .. it's kiddin me - I have it reproduced - see attached file. [2018-03-27 12:24:30] I send the last result In the file you can see how long (in average) the calculation of a package takes. So either it's a really difficult one sent by the pool (I use now the normal pool with diff. 5000) Here is the log: https://pastebin.com/P48vB5i2 So if I see it right, the card simply does not calculate anything for 15 mins (why?) and then the pool cuts the connection. Would it be possible that in case of "Unauthenticated" the miner simply "die;" or restarts from scratch? A self termination would be nice (eg. setable in the config), because then I could check with a script if the process is still running. But if it does not mine and is still running it's hard to check. |
Hello again. I "think" we can conclude this issue solved. The following situation: I noticed that the cards did deliver max 120 shares, then they powered down. I said max 120 - usually less (thats about ~60 min runtime). However, in some rare cases the AMD driver did a reset aswell. More stangely, when I tried to open the Radeon Settings tool, it did not open at all (never tried to open it before). So I downloaded the minimal driver setup tool from the amd page and it told me that I am using the latest drivers for the card. But there was also a non recommendet beta driver. So I installed this one and now the Radeon Settings tool works. I guess the stable version of this driver would work aswell because somehow it seems to have installed the Radeon driver comming via Windows Update. Even having the same version number, it seems to be glitchy somehow. Now the cards seem to run smoothly, now 90 minutes with 195 and 175 submitted shares. Sorry that I thought it was an issue with/of xmrig-amd ;) The learning curve: Don't use the Driver Windows Update wants to install - even it's the same version Number. Maybe this helps some people in the future having a similar issue... PS: even for such a small card the hashrates are pretty good - stable 160 H/s for a small profile card powered only via PCI-E. If it runs now stable, maybe I try to overclock them a bit... |
Hello,
I am using xmrig-amd to mine at supportXMR.com. I do use other versions of XMRig for CPU mining at lower hashrates but only on xmrig-amd I get occcationally the following error:
The Radeon manages to get around 150 H/s steady and even on port 7777 the pool sets the difficulty to somwhere between 5000 and 7000. So xmrig-amd sends around 4 to 6 shares per minute.
The stange thing is, that this error appears sometimes after a few minutes, sometimes after an hour and sometimes after 20h+
I had keepalive set to true and now do a "test" run with "false".
Can anyone chat some light onto this - is the a bug?
PS: the version I use is:
PPS: I see a new version came out 2h ago - so was this a known issue on 2.5.0?
The text was updated successfully, but these errors were encountered: