This repository has been archived by the owner on Oct 20, 2023. It is now read-only.
Replies: 1 comment
-
As additional info - if one of the daemons is not active the pool will not start. I removed one I thought was not working and the everything working as expected. Add a daemon that is not online and it halts start of program with this setup. Recommend validate stage for daemon to validate online and connection and proceed if at least X daemons for each required daemon per coin per pool is active. Show me where this is in code and I will try to test... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be nice to know which daemon connections are being waited on - which are dead and which are alive - during startup. In present case - only the defined "pools" "id" is displayed
e.g. [poolid] Waiting for daemones to come online ...
in case of multiple defined daemons within minigcore config.json for each coin per pool there should be an ID for each defined daemon with tag for which pool/coin associated.
JobManagerBase.cs
appears to only call the functions/methods to initialize daemons and reports waiting on daemon to come online while in dumb loop checking daemon setup correct and connected. - Please show me where these are at I cannot find the code to look at... code not documented at all and cannot find with github search...
................
protected abstract void ConfigureDaemons();
Beta Was this translation helpful? Give feedback.
All reactions