You can setup a coin daemon, get it up to the top of the chain and verify that getblocktemplate is working properly. Then start up your s-nomp instance for that coin and it will connect and after that, it will allow miners to connect and start mining.
If some time after that the coin daemon becomes unavailable and getblocktemplate fails, s-nomp will reject all new connections to the pool until the problem with the coin daemon is resolved. That is the proper behavior.
Existing connections, however, are not dropped. This has the effect that if a coin daemon dies, all currently connected miners will continue to mine without any indication on their part that there is a problem.
The code should be updated to disconnect all existing miners if getblocktemplate fails.
You can setup a coin daemon, get it up to the top of the chain and verify that getblocktemplate is working properly. Then start up your s-nomp instance for that coin and it will connect and after that, it will allow miners to connect and start mining.
If some time after that the coin daemon becomes unavailable and getblocktemplate fails, s-nomp will reject all new connections to the pool until the problem with the coin daemon is resolved. That is the proper behavior.
Existing connections, however, are not dropped. This has the effect that if a coin daemon dies, all currently connected miners will continue to mine without any indication on their part that there is a problem.
The code should be updated to disconnect all existing miners if getblocktemplate fails.