block solved by nsgminer but didn't credit to account?

[goodthebest]

@ghostlander Hi John, I tried to solo mine phoenixcoin using ngminer and correct coinbase address was given. According to nsgminer it had solved two blocks but checking phoenixcoind which is fully sync, doesn't show up any credit into account? Is there any glitch in phoenixcoin itself or nsgminer?

Could you please look into this. If you require I'll give you my pxc account. i tried to check explorer no clue there.

PS. I tried NSGminer with guncoin as well as feathercoin same result, it seems something not right with it?

[ghostlander]

phoenixcoind listtransactions

[goodthebest]

~/Phoenixcoin/phoenixcoin-lin-amd64-0.6.6.1 # ./phoenixcoind listtransactions
[
]

result is none.

In fact, I've tested nsgminer solo mine connecting with own daemons of Guncoin, Feathercoin and your own Phoenixcoin, blocks solved but they were never submitted to the daemons, therefore it doesn't result into any transaction.

There seems to be some serious bugs when it comes to solo mine with GPU NSGminer. Even in the past I discussed same issue with @Bushstar of Guncoin I think a week or so ago, he spoke to you about this issue too?

My findings are CPU NSGminer neoscrypt works fine and solves block successfully and transactions are valid, however GPU nsgminer got problem.

[ghostlander]

Have you provided a specific coin base to the miner? If so, look there. The daemon only monitors its wallet.dat addresses including reserved.

[goodthebest]

I gave the same coin base address as of daemon wallet. I have tested it on three neoscrypt coins feathercoin, guncoin and phoenixcoin, same problem. Issues lies in nsgminer GPU solo mining most probably.

What workaround do you suggest?

[goodthebest]

parameters used...

nsgminer -o http://127.0.0.1:9554 -u rpcuser -p rpcpassword --coinbase-addr=phoenixcoin_address -D --verbose

[ghostlander]

It works for me. If the miner shows a block solving share, it must be because the daemon has told so. Look at the daemon's logs.

[goodthebest]

alright I manage to find from phoenixcoin's log file, here it is that says blocked accepted but it's never credited to my account, coinbase not working? I've appended log with different parts, hopefully it will give you some clue?

02/17/18 08:43:56 ThreadRPCServer method=submitblock
02/17/18 08:43:56 ThreadRPCServer method=submitblock
02/17/18 08:44:00 connection timeout
02/17/18 08:44:00 trying connection 83.33.214.67:9555 last seen=-7.6hrs last try=-421904.7hrs
02/17/18 08:44:05 connection timeout
02/17/18 08:44:06 trying connection 71.55.211.143:9555 last seen=-2.5hrs last try=-421904.7hrs
02/17/18 08:44:10 ThreadRPCServer method=getinfo
02/17/18 08:44:10 keypool reserve 3
02/17/18 08:44:10 keypool return 3
02/17/18 08:44:11 connection timeout
02/17/18 08:44:11 trying connection 184.22.147.210:9555 last seen=-1.4hrs last try=-421904.7hrs
02/17/18 08:44:16 connection timeout
02/17/18 08:44:17 trying connection 176.212.28.93:9555 last seen=-7.5hrs last try=-421904.7hrs
02/17/18 08:44:22 connection timeout
02/17/18 08:44:22 trying connection 184.22.147.210:9555 last seen=-1.4hrs last try=-421904.7hrs
02/17/18 08:44:25 ThreadRPCServer method=getwalletinfo
02/17/18 08:44:25 received block b6da900b11e12b42473e height 1648109
02/17/18 08:44:26 SetBestChain: new best=b6da900b11e12b42473e height=1648109 work=4843927702367628 date=02/17/18 08:42:54
02/17/18 08:44:26 ProcessBlock: ACCEPTED
02/17/18 08:44:26 ProcessSyncCheckpoint: sync-checkpoint at b6da900b11e12b42473e533648b8fe45a69d3ef90aa8109b768069dc4aca111d
02/17/18 08:44:27 connection timeout
02/17/18 08:44:28 trying connection 176.212.28.80:9555 last seen=-1.5hrs last try=-421904.7hrs
02/17/18 08:44:28 getblocks 1648109 to b6da900b11e12b42473e limit 1000
02/17/18 08:44:28 getblocks stopping at 1648109 b6da900b11e12b42473e
02/17/18 08:44:28 Flushing wallet.dat
02/17/18 08:44:28 Flushed wallet.dat 27ms
02/17/18 08:44:29 getblocks -1 to 00000000000000000000 limit 1000
02/17/18 08:44:33 connection timeout
02/17/18 08:44:33 trying connection 95.121.3.218:9555 last seen=-26.5hrs last try=-421904.7hrs
02/17/18 08:44:37 getblocks 1648109 to b6da900b11e12b42473e limit 1000
02/17/18 08:44:37 getblocks stopping at 1648109 b6da900b11e12b42473e
02/17/18 08:44:37 getblocks -1 to 00000000000000000000 limit 1000
02/17/18 08:44:38 connection timeout
02/17/18 08:44:39 trying connection 198.48.139.57:9555 last seen=-3.4hrs last try=-421904.7hrs
02/17/18 08:44:43 ThreadRPCServer method=getwbalance
02/17/18 08:44:44 connection timeout
02/17/18 08:44:44 trying connection 46.18.0.108:9555 last seen=-1.1hrs last try=-421904.7hrs
02/17/18 08:44:44 connect() failed after select(): Connection refused

IRC got who
IRC got who
IRC got who
DNS seeds: 7 addresses loaded
ThreadDNSAddressSeed exited
trying connection 70.75.217.71:9555 last seen=-16.5hrs last try=-421904.8hrs
trying connection [2a00:1768:1004::3ace:c493]:9555 last seen=-394127.0hrs last try=-421904.8hrs
connect() failed after select(): Connection refused
trying connection 162.217.249.198:9555 last seen=-394127.0hrs last try=-421904.8hrs
connected 162.217.249.198:9555
peer 162.217.249.198:9555 unknown, sending version using dual magic
sent version message to 162.217.249.198:9555, version 60004, blocks=1648109, us=195.201.8.216:9556, them=162.217.249.198:9555
Added time data, samples 2, offset -2 (+0 minutes)
received version message from 162.217.249.198:9555, version 60004, blocks=1648110, us=195.201.8.216:53852, them=162.217.249.198:9556
ResendWalletTransactions()
ProcessSyncCheckpoint: pending for sync-checkpoint 209d3c401055fbb9f80648601c57d1fab2ba83c42bc834d9fb004f3a2313025b
received block 209d3c401055fbb9f806 height 1648110
SetBestChain: new best=209d3c401055fbb9f806 height=1648110 work=4843940027517167 date=02/17/18 08:46:20
AcceptPendingSyncCheckpoint : sync-checkpoint at 209d3c401055fbb9f80648601c57d1fab2ba83c42bc834d9fb004f3a2313025b
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 24ms
connection timeout
trying connection 107.161.164.223:9555 last seen=-0.3hrs last try=-421904.8hrs
connected 107.161.164.223:9555
peer 107.161.164.223:9555 unknown, sending version using dual magic
sent version message to 107.161.164.223:9555, version 60004, blocks=1648110, us=195.201.8.216:9556, them=107.161.164.223:9555
Added time data, samples 3, offset -1 (+0 minutes)
received version message from 107.161.164.223:9555, version 60004, blocks=1648110, us=195.201.8.216:46824, them=107.161.164.223:9556
trying connection 176.212.28.80:9555 last seen=-1.6hrs last try=-421904.8hrs
connection timeout
trying connection 91.197.105.12:9555 last seen=-0.9hrs last try=-421904.8hrs
connect() failed after select(): Connection refused
trying connection 46.18.0.108:9555 last seen=-1.2hrs last try=-421904.8hrs
connect() failed after select(): Connection refused
trying connection 80.76.101.183:9555 last seen=-3.9hrs last try=-421904.8hrs
connect() failed after select(): Connection refused
trying connection 178.151.82.125:9555 last seen=-1.5hrs last try=-421904.8hrs
connection timeout

[ghostlander]

If there was a valid PoW found and sent to the daemon through RPC submitblock, a text "GBT proof-of-work found" with the coin base details had to be present in debug.log. Please note RPC submitblock had been implemented after the v0.6.6.1 release.