No ideas. It worked for me with Win7 and Linux, never tried with Win10.

Yes, run 2 instances with different -di switches.

Safari on latest MacOS. Definitely no such languages in Accept-Languages, Russian is the system language. In system settings Russian is the main, another one is English. That's all.

Same here, @ethermine right now. If this pool owner helps with language I might switch. Sure I can use Chinese interface, but still prefer to read without translations.

I see no flags to change language, and also there is no difference in URLs on a phone and mac. It seems to use some browser settings regarding preferred accepted language that is neither English nor Chinese for me. So same URL will look different.

Antpool is not a choice for me, I mine Ethereum but tired of DwarfPool glitches. Switched to Ethermine for now, but interested to try this one.

Anybody helps how to choose English interface?
I see English from my phone, but Chinese on a mac. There is no language switch.

Another series of rejects @ DwarfPool. I understand it is not a miner fault, but wonder why it did not detect issues like 2000/800 or 6000/600 shares/rejects as a reason to restart.

I sent you PM with logs from 4.6b3, please check what happened.

I am writing that again and again: why don't read the 1st message of this thread? There is a copy of README there, and this option is also explained.

Yes, I should confirm that since 4.6beta3 there is no more resource leakage in Linux version.

Also just received a report that there were recently another issues with DwarfPool so it rejected a lot of shares in a raw. But this time it was not CDM, but another miner. So I tend to think that my issue with 4.6 was not a miner fault. All I needed was to have an option to restart miner not after some percent of rejects, but after some percent per time interval or sliding window.

I am used to be the GenEthOS advocate and use it myself. But now I have to warn you that GenEthOS CONTAINS a backdoor to your system. The author said you may change the password from default one. What he does not say that the account 'work' has authorized_keys listing two of his ssh public keys. That means that if you expose GenEthOS to the Internet via ssh and even if you changed the password, it still can be accessed by the key owners, any software can run on behalf of that person including changing wallets to others or making a backdoors to run as a root on restart or via web GUI.

I was really disappointed finding this 'feature' in GenEthOS (not ethOS) image without any mention in the description.

And strictly speaking, they're right. Any fork breaks the main idea of blockchain, making Ethereum NOT that declared on their main page.

The worst thing is that so called hacker may be wrong in general, but strictly complied with the terms of TheDAO contract. Any fork means that a 3rd-party changes the rules of the game on the fly in favor of someone just because some business made something wrong and lost some investments. Any investment is a risk, and they should learn the lesson, fix it and move on. Instead, due to conflict of interests being in both Ethereum foundation and TheDAO curators, they decided to prove the world that they are right to break own rules just because they lost some money due to own fault. Be that a smaller project that failed, no one would ever thought about any forks. But this one just "too big to fail", and that's sad.

No any polls and votes should be treated as the network consensus - they just mean that people trust to the founders without own investigation. If one said 'theft', they do not do own judgement. And just led by a false goal. Killing the whole Ethereum thing as a result.

Also I can definitely confirm that the memory leak is directly related to the telemetry. I stopped the monitoring and found no memory leaks using the same top output. As soon as I started the monitor again, the leak resumed.

More info found, I'll PM it to you.

No, no. These are two different issues.

Rejects I saw with 4.6 right after release when switched from 4.5 in a hope to get fixed the telemetry problems. It run without logs since there was no issues with rejects until 4.6. So I cannot show those logs.

Now I run 4.5 again that has no such issues. But the memory leak is obvious and easily observed. If you run the program 'top', you'll see that the miner process consumes around 1M per second of virtual memory. Probably that is the reason why telemetry got dropped. You close the socket after every request and probably something leaks. I expected to open the control connection once and then just send requests and get replies over the same socket.

Please check the 'top' output on Linux and I am sure you will fix that leak easily.

That might be the memory leak since I reported you about that already. Now I still use 4.5 after 7 hours of total rejects @ Dwarf with 4.6 for both rigs. I can run the debug version but do not like an idea of having another few hours of rejects
Unfortunately I can't help with memory leak debug for closed source software.

I PMed you at the same time as I wrote it and sent links to full logs. PM was not answered.

Now I repeated the case. Again, both rigs started at the same time stopped responding at the same time. That is common, the uptime - it is around 45 hours. I think some timer overflows with that period.

In some cases, usually when risers are used, PCI-e bus can give wrong data reading temps. Usually it is not 100, but 511. But if that was the case, GPU usually does not behave right after that anyway.

Since you twice ignored this question, I assume the answer is "No changes, Linux 4.6 telemetry still is unstable".

Due to reject issues with 4.6 and some pools I set back to 4.5. After running two rigs for ~45 hours both at the same time and same uptime had lost telemetry sockets, still running fine for mining. I am sending you links to both full logs in PM.


Any chances to have stable telemetry on Linux? Or should I finally write an own process monitor and restart miner when telemetry is lost?

Why don't modify open-source ethmon? It almost ready for warning/error notifications now, I am adding emails, but you may add xmpp. Search the thread back if you need a link, I published it some time ago but saw no interest to it, thus no more links. But the project alive @github.

This time it run with logs disabled, since run off USB flash and I have never had any issues. So no logs.

There was no answer, sad.

Afraid, I've got another one: using CDM for more than a month, have never had any reject on Dwarf. With 4.6 just mined for 3 hours with all shares rejected after 30+ hours of normal run on TWO separate rigs. Version 4.5 on the 3rd rig works as it should. Both 4.6 stopped working at the same time (both booted at the same time). Nothing triggered, including "failover if pool rejects too many shares" after 800+ rejected shares in a raw. Had to switch back to 4.5.