Closed Olegik-ah closed 6 years ago
My workaround:
For one of your nemo instances, edit Include.ps1:
Line 80, change $StartPort = 4068
to $StartPort = 4069
The TCP Port detection isn't working, or at least it's causing the running miner to close as you noticed. My way let's each instance start using it's own non-conflicting port
Why did you close the ticket? Why so rude? Any explanation?
To dealbreak3r - it is not port detection bug. I think the bug is in the lines 336 or 339 in core.ps1. But i dont know how to fix it.
Multi-instance is experimental. My method is quick and easy. If you are already going in and modifying config.json, you are advanced enough to make the port number tweak as well.
I've been multi-instance mining for the past 2 weeks with just the port number change, without having to touch Core_v3.0.ps1. Rock solid. They do not interfere with each other (Excavator requires additional tweaks, but that's an optional miner not enabled by default). Give it a try.
This is a minor bug (thanks for stating :)) has the miner will restart on the right port on next cycle. This happens only when starting the second instance. So this is not preventing anything from working. Editing include.ps1 is not even needed.
Still it will have to be fixed. But it is low priority on my list has it id non blocking. This one should be closed for now. We'll wake it up once actively working on it.
It appears that some miners (not all) do not like the way we poll the port to find out of it is free.
Yes, it happens only 1 time at startup 2nd instance. MrPlus, thanks. If you already know bug - ok. Nemo closed my ticket without any comment. It is so rude!
Hi! I found minor multiple instances bug. How to reproduce:
Hope well explained:)