Aside from having those lines in terracoin.conf file and restarting client to get it running in server mode, you should set Coinotron or BitcoinReactor
as secondary pool. That way you will leech long-polling data from them, which will make your Terracoin server update block as soon as one of those
pools detect the change, but more importantly, it will update data your miner is working on. Unless there is long-polling info from somewhere, your
miner could be working on old block for up to scantime seconds, which is 60 by default! Any block solution submitted by miner in such scenario will
be rejected by Terracoin server. Also, check if your miner is set to failover-only disabled mode = enabled mode is bugged and might make miner lag
around 25 seconds behind block change even with long-polling data received!
+1 for the advise given here. Never thought of that and never knew could do such things. Thank you very much for this information. Have put this into test and will report back. Seems that the long pool is updating with new blocks found so must be working and updating. Thank you for the info.
