MoneroOcean/meta-miner

MM 1.2 restart errors

TESTICULEEZ opened this issue · 1 comments

MM v1.2 with stock xmrig 2.8.1 log file attached. I am experiencing restart errors similar to the attached on my rig. 3 different instances running (local host 3334,5, and 6) to separate different cards. Trying stock xmrig 2.8.3 has no change. Errors consistently reference the miner port being in use by another instance.
mm.log
mm config.json as follows
{
"miner_host": "127.0.0.1",
"miner_port": 3335,
"pools": [
"us.moneroocean.stream:10032"
],
"algos": {
"cn/1": "xmrig-amd.exe --config=config.json",
"cn/2": "xmrig-amd.exe --config=config.json",
"cn/xtl": "xmrig-amd.exe --config=config.json",
"cn/msr": "xmrig-amd.exe --config=config.json",
"cn/xao": "xmrig-amd.exe --config=config.json",
"cn/rto": "xmrig-amd.exe --config=config.json",
"cn-heavy/0": "xmrig-amd.exe --config=config-heavy.json",
"cn-heavy/tube": "xmrig-amd.exe --config=config-heavy.json",
"cn-heavy/xhv": "xmrig-amd.exe --config=config-heavy.json",
"cn-lite/1": "xmrig-amd.exe --config=config-lite.json"
},
"algo_perf": {
"cn": 1807,
"cn/2": 1902,
"cn/msr": 3512.2,
"cn-lite": 3674,
"cn-heavy": 1354
},
"algo_min_time": 400,
"user": "removed",
"pass": "RX480",
"log_file": "mm.log",
"watchdog": 250,
"hashrate_watchdog": 80
}

Follow up... I went through to verify all my drivers and system was updated... ironically MM became stable once I updated my Java runtime environment (only thing that needed an update... MM should be node.js base and not interact with JRE if I understand correctly... so it doesn't make sense to me but... it has been stable for 36 hours since the update when restarting...