" 1 error" message

[poppy01]

Release issued today

Maybe this will shed some light on what happened recently.

Not really, sorry.
According to my own tests my miners always have been disconnected properly in case I switched to another pool manually, so this cannot be the problem here. As per my opinion, this problem is caused by a misinterpretation of the password string by the new release.
This problem should be fixed since there is no chance - in case you are running several miners - to identify a non-performing miner by these cryptic ID strings.

Interestingly, I saw a strange behaviour just a few minutes ago. The amount of my connected miners was 22 (I have only 12) and the total hash power was greater than 10 GHS - which should be 6GHS max. Both counters came down to the correct values after a few seconds and remain there since then. However, this issue should be investigated as well.

Update: Currently 11 of my 12 miners show cryptic worker names. The hash rates seem to be ok.


BR
poppy01

[hashingpro]

When I gave you that link did you read all of it?
Read from the 6th list item Steve talks about down.


Try to lose the underscores, try with M1, M2, M3, M4
See if that makes any difference.

[poppy01]

What are you talking about???
I posted my names here earlier, and as you can see they are clearly different! A difference of one character makes it a different name, am I right?
On the help page there is also no hint about any forbidden characters that I used. And: it worked perfectly well before!

I guess neither you nor me can be aware of any changes made to the password string. Maybe Chris should enlighten us here....

[MaterialResources]

Poppy01 is definitely experiencing the same problem. My production has now dropped significantly. I may register a new account to see if that helps.

[MaterialResources]

I tried a new account and the same problem followed me. Even a miner from the other account showed up on the new account, and the miner had not been changed over.There is definitely something odd happening. I have no idea what. These are Antminer L3+ s .

[Kfedorek]

Ya i have the same name error issue yet all of my workers are different and it never happened until recently. Then it was 2 workers then it was normal and now its still 1.

[hashingpro]

What worker names are you using Kfedorek?

Can you list the n= settings for them.

[hashingpro]

What are you talking about???
I posted my names here earlier, and as you can see they are clearly different! A difference of one character makes it a different name, am I right?
On the help page there is also no hint about any forbidden characters that I used. And: it worked perfectly well before!

I guess neither you nor me can be aware of any changes made to the password string. Maybe Chris should enlighten us here....

My password string is:
n=Antminer_L3_01
n=Antminer_L3_02

They recently made changes to worker names.
What if, and I didn't test it, they ignore from the underscore on down.
Then ALL your worker names to the pool are the same. Yes you are changing them, but only if the _ wasnt an illegal character and got parsed out?
if so you have all your miners named, at least to the pool, Antminer

All I was asking is, did you try M1, M2, M3...LOSE the underscore to see if that mattered?

[Lapy]

I am also facing this error outta e blue