It has been strange since I haven’t been able to find what causes the miner to restart. Other than receiving a ctrl c, each of the miners in the flight sheet has no further info
I know it is just an alert, which it displays when there isn’t a value set. However, I had 140 h/s for beam and it displays that! Since the watchdog is complaining about beam, the miner doing beam was in the first slot.
I know it isn’t serious, but just annoying (both issues other than losing some minutes while the miner ramps up to speed). All the other algorithms don’t display this alert if there is a value set, only beam
Maybe there is something with the saved info for the min hashrate?
hive670 hive-watchdog[1253]: Watchdog disabled: miner is not running
hive670 hive-watchdog[1253]: Watchdog enabled
hive670 hive-watchdog[1253]: beamhashv3
hive670 hive-watchdog[1253]: beamhashv3 minimal hashrate is not set
hive670 hive-watchdog[1253]: OK LA(5m): 2.51 < 9.0, LA(1m): 3.01 < 18.0
hive670 hive-watchdog[1253]: OK beamhashv3
hive670 hive-watchdog[1253]: beamhashv3 0.13987 kHs > 0
WD_MINHASHES_ALGO has "beamhashv3":0.14