Quote from: AverageCitizen on May 02, 2018, 12:22:42 AM

Quote from: Schmeckles23 on May 01, 2018, 04:47:50 PM

Quote from: AverageCitizen on May 01, 2018, 11:52:37 AM

Quote from: AverageCitizen on April 29, 2018, 10:37:49 PM

Quote from: Leafy_CK on April 29, 2018, 05:27:27 PM

Quote from: AverageCitizen on April 29, 2018, 02:29:06 PM

Hello!
I was attempting to create a new Solace coin pool cloned from Github (https://github.com/LPHuynh/cryptonote-solacecoin-pool) but keep running into an error and hoped someone with more knowledge could assist me.
Scenario: The pool is running, rpc wallet running, pool wallet open in background refresh. Miner connects and hashes, pool accepts shares. So it seems everything is working ok on the backend. Now, on the front end, when a miner connects, miner worker stats show and update, everything looks good. However, under the space where address lookup is, in red it blinks CONNECTION ERROR every few seconds. Nothing seems to be broken but I'm not a pool expert.
Could someone tell me how to fix the blasted red blinky connection error please?

Thanks and keep hashing!

AverageCitizen

I updated my github with a quick fix just now Wink

Thank you Leafy, that did the trick.

Congratulations on the coin's first donation!!!!!!

Now, back to the blasted pool lol. Apparently, I'm doing something wrong.
Scenario:

Pool hashing, everything showing ok on pool (front and back end). Miner connected for 36hrs @ 1.6 to 2 kh with no blocks found.
Daemon and wallet running on specified ports from solacecoin.json, RPC wallet synced on same port as stated in .json. Like I said, everything shows good grrrrr except no blocks found and the effort has been anywhere from 300% to 1256%. What might I have missed in configuring the pool?

Thanks for the assistance

Has the blockchain fully synced?

Yes, the blockchain has been sync'd 100 percent on mainnet. Just to be sure of anything I deleted the DB and resync'd with the same problem results. RPC says [RPC0]Expected 1 tx, got 0

Update:
I noticed the daemon reported
2018-May-02 00:35:32.067870 [P2P2][118.69.72.95:53838 INC]Sync data returned a new top block candidate: 32936 -> 16232 [Your node is 16704 blocks (11 days) ahead]
SYNCHRONIZATION started
2018-May-02 00:37:30.395813 [P2P0][118.69.72.95:53931 INC]Sync data returned a new top block candidate: 32939 -> 16232 [Your node is 16707 blocks (11 days) ahead]
SYNCHRONIZATION started

HUH?! this must be above my paygrade.

Is there any chance you can come to Discord and we will help you?