0
Under review

XDN Monero Pool, All My Miners Are Offline Since Yesterday Evening.. Says Bad Hash?

SPLDust 6 years ago updated 6 years ago 21

Hello, all my miners for XDN Monero, 48ZxFxTBFTRNZETCbrm2PsLGweo4uSEM6764Nynp1Zmq5EiwasA3j2VY3SJoynBoje2VT2Abea7Yr5zPsXs7RhyYJ9JBie4 , are saying "Bad Hash" when you hit "r" and it keeps saying result rejected by the pool. This started yesterday evening.

Dang... I spoke too soon... I replaced the XMR-Stak files, switched to the new pools.txt file, it connects to the pool, starts mining and then after submitting a couple results, comes back saying "All pools are dead, Idling, SOCKET ERROR - [xmr.coinfoundry.org:3133] CALL error: Timeout while waiting for a reply" then reconnects and repeats the same errors.

+1

Which IP does xmr.coinfoundry.org resolve to when you ping it? Also did you make sure that no old configuration files for XMR-Stak were retained as those are incompatible with XMR-Stak versions > 2.3.

97.107.139.34 and yes, I deleted old files and replaced with all new files


It seems to have started working in the past few minutes, submitted about 10 results now without the error, which is first time it went this far... Going to fire up the rest of my miners... TY...

+1

ANYONE ELSE HAVING THIS ISSUE, I BELIEVE IT HAS TO DO WITH YOUR MINING MACHINE CACHING THE IP ADDRESS INFO OF THE OLD POOL INFO... TURNING MY MINERS OFF FOR ABOUT 5 MINUTES AFTER UPDATING THE SOFTWARE AND SETTINGS DID THE TRICK ON ALL MY MACHINES.

Thank you Oliver for pointing me in the right direction!

+1

Ive had the same problems with new XMR-Stak just switched to XMRig and everything runs fine.

I am having issues with the new XMR-Stak crashing as well... May have to switch to XMR Rig as well... do you by any chance know if you can run multiple threads on AMD GPUS on XMR Rig? I am running 2 threads on each gpu on SMR Stak, with modified bios on each GPU, they were working flawlessly before the Fork and Program Update

+2

XMR-Stak appears to having serious issues with CPU Mining currently. I'd advise to use XMRig for the time being.

+1

maybe try the option: --noCPU

But using xmrig-amd and/or  xmrig would be best


Note that for me xmrig-nvidia required to use:  "nohup ... 2>&1 1>/dev/null &"

the -B option does not work well 


Edit:  still hope that tpruvot ccminer will support the fork

I tried that, still comes up with socket errors and every now and then the machines will crash and reboot. All was fine before the updated software.

+2

Hopefully this version will actually get us somewhere... 16 days and no blocks

+3

is it possible, that the pool Servers lose Connection to the monero network? 17 days without a block is disgusting :(

There must be something going on which we are not being told...

Yeah, I am wondering the same thing... We started hammering the blocks there for a minute then right before the fork, nothing... Currently still having issues, won't be able to switch to XMRig until tomorrow when I am back in the office.

+1

I've repeatedly checked every moving part of the Monero Pool for problems over the past weeks but found nothing. I'm just doing it again. Will keep you guys posted.

Wow, look at that difficulty drop! I think we just need to wait for things to normalize. Lots of changes going on.

I get the same socket error at another pool with only cpu mining, very weird.

I'm guessing its on the mining software end and not the pool end... I have noticed that it is not doing it as frequent now, but still occasionally doing it.