Something strange happens with my miner's monitor
I use Claymore monitor 3.4, miner version 10.0
1 or 2 rigs are constantly loosing connection with monitor. I.e. Monitor turns red and in "lost" state for corresponding miner.
While miner actually works (with pool) but with message:
ETH: GPU0 28.009 Mh/s, GPU1 28.529 Mh/s, GPU2 28.366 Mh/s, GPU3 27.995 Mh/s, GPU4 28.001 Mh/s
server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...
I tried different -mport values but it doesn't help. It happens since Saturnday. I use read-only mode and internal IP
LOL. I had similar behavior, no any error msg in logs though: single worker (out of multiple ones in the same LAN) was constantly loosing connection. And it seems I just fixed it in a
really weird way: get EthMon 2.9, place your config into its dir(to speed things up), remove all related entries from win firewall, run it and allow both public & private profiles = that's it. Have NO idea why it works now... or why it wasn't working before.
If I do the same procedure with 3.4 it wont solve the problem... I'm really confused.
EDIT:
@Kukus Please try and report back.
Reporting:
I didn't check anything in firewall. Just run ver2.9 and it works. But now, when I've tried 3.4, this mystic software works again. But I have to wait because miner looses connection after 6-10 hours only.
Freaking nightmare man! I just had the weirdest shit ever. Like I said before cleaning entries in windows firewall and running 2.9 made it all right. (no falsely lost miner) Until now...
I actually have two ethman running. One running on the LAN with workers (can access it with vnc) and another on my laptop with VLAN addresses (openvpn).
As I said, for the day+ it was completely fine... and then few minutes ago I noticed that the only miner not in red is the one that was getting lost all the time!
I checked and on both ethmans it was the same picture. So I tried to close the program, but it freaking refused! On LAN it gave me something like "access violation and 0x00000000 address" error. and one on VLAN said that it "cannot close program launched by external process". So I killed it from process explorer on both locations. Now whatever I do one of the miners is in red (the same one that was having issues before and the samer one that was reporting to work when all others were lost), while its working just fine. (I can see its working in VNC with no interruptions. Same with the hash arriving to the pool)
WTF is going on?
EDIT: removed all "ethdcrminer64" firewall entries, restarted miner, allowed rules for private profile - now it seems fine again.
