URGENT: Node wont start again, mncache.dat file missing?

[kiahmed]

I was running latest dash in testnet mode over few weeks . Everything was great, no body touched the server or anything . I just found out today dash stopped running and wont ever start gain with the following errors. It is not a masternode or never ran in production, it was only running in testnet for development purpose. Any idea, why the file kept deleting or whats happening ?

2018-03-01 18:49:09 Using masternode config file /root/.dashcore/testnet3/masternode.conf 2018-03-01 18:49:09 fLiteMode 0 2018-03-01 18:49:09 nInstantSendDepth 5 2018-03-01 18:49:09 PrivateSend rounds 2 2018-03-01 18:49:09 PrivateSend amount 1000 2018-03-01 18:49:09 init message: Loading masternode cache... 2018-03-01 18:49:09 Reading info from mncache.dat... 2018-03-01 18:49:09 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file 2018-03-01 18:49:09 Error reading mncache.dat: Load: File format is unknown or invalid, please fix it manually 2018-03-01 18:49:09 Error: Failed to load masternode cache from /root/.dashcore/testnet3/mncache.dat Error: Failed to load masternode cache from /root/.dashcore/testnet3/mncache.dat 2018-03-01 18:49:09 PrepareShutdown: In progress... 2018-03-01 18:49:09 scheduler thread interrupt 2018-03-01 18:49:09 Verifying mncache.dat format... 2018-03-01 18:49:09 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file 2018-03-01 18:49:09 Error reading mncache.dat: Dump: File format is unknown or invalid, please fix it manually 2018-03-01 18:49:09 Verifying mnpayments.dat format... 2018-03-01 18:49:09 Loaded info from mnpayments.dat 0ms 2018-03-01 18:49:09 Votes: 0, Blocks: 0 2018-03-01 18:49:09 Writing info to mnpayments.dat... 2018-03-01 18:49:09 Written info to mnpayments.dat 0ms 2018-03-01 18:49:09 Votes: 0, Blocks: 0 2018-03-01 18:49:09 mnpayments.dat dump finished 0ms 2018-03-01 18:49:09 Verifying governance.dat format... 2018-03-01 18:49:09 Loaded info from governance.dat 0ms 2018-03-01 18:49:09 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Erased: 0), Votes: 0 2018-03-01 18:49:09 Writing info to governance.dat... 2018-03-01 18:49:09 Written info to governance.dat 0ms 2018-03-01 18:49:09 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Erased: 0), Votes: 0 2018-03-01 18:49:09 governance.dat dump finished 0ms 2018-03-01 18:49:09 Verifying netfulfilled.dat format... 2018-03-01 18:49:09 Loaded info from netfulfilled.dat 0ms 2018-03-01 18:49:09 Nodes with fulfilled requests: 0 2018-03-01 18:49:09 Writing info to netfulfilled.dat... 2018-03-01 18:49:09 Written info to netfulfilled.dat 0ms 2018-03-01 18:49:09 Nodes with fulfilled requests: 0 2018-03-01 18:49:09 netfulfilled.dat dump finished 0ms 2018-03-01 18:49:09 Shutdown: done

[UdjinM6]

Just stop your node, remove /root/.dashcore/testnet3/mncache.dat and start your node again.

[kiahmed]

that did it, but now getting lots of MN related connection refuse in the log . Do I have to manually add any seed nodes for testnet? CMasternodePayments::CheckAndRemove -- Votes: 26353, Blocks: 5011 2018-03-01 21:46:43 CInstantSend::CheckAndRemove -- Lock Candidates: 0, Votes 0 2018-03-01 21:46:43 ThreadSocketHandler -- removing node: peer=46 addr=52.73.56.126:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:46:43 ThreadSocketHandler -- removing node: peer=47 addr=52.201.23.129:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:46:43 ThreadSocketHandler -- removing node: peer=48 addr=108.61.192.47:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:46:43 ThreadSocketHandler -- removing node: peer=49 addr=138.68.234.187:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:46:43 ThreadSocketHandler -- removing node: peer=50 addr=145.239.235.18:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:46:47 connect() to 50.254.73.147:20021 failed after select(): No route to host (113) 2018-03-01 21:46:48 ERROR: Requesting unset send version for node: 51. Using 209 2018-03-01 21:46:48 ThreadSocketHandler -- removing node: peer=51 addr=83.1.99.2:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:46:49 ERROR: Requesting unset send version for node: 52. Using 209 2018-03-01 21:46:49 receive version message: /Dash Core:0.12.3/: version 70208, blocks=83985, us=35.199.39.129:40828, peer=52 2018-03-01 21:46:50 ERROR: Requesting unset send version for node: 53. Using 209 2018-03-01 21:46:50 receive version message: /Dash Core:0.12.3/: version 70208, blocks=83985, us=35.199.39.129:43438, peer=53 2018-03-01 21:46:51 ERROR: Requesting unset send version for node: 54. Using 209 2018-03-01 21:46:51 receive version message: /Dash Core:0.12.3/: version 70208, blocks=83985, us=35.199.39.129:49606, peer=54 2018-03-01 21:46:52 ERROR: Requesting unset send version for node: 55. Using 209 2018-03-01 21:46:52 receive version message: /Dash Core:0.12.3/: version 70208, blocks=83985, us=35.199.39.129:44134, peer=55 2018-03-01 21:46:53 connect() to 155.94.181.165:19999 failed after select(): Connection refused (111) 2018-03-01 21:46:55 ERROR: Requesting unset send version for node: 56. Using 209 2018-03-01 21:46:55 receive version message: /Dash Core:0.12.2.3/: version 70208, blocks=83985, us=35.199.39.129:45516, peer=56 2018-03-01 21:46:56 connect() to 217.182.229.151:19999 failed after select(): Connection refused (111) 2018-03-01 21:46:57 connect() to 217.182.229.154:19999 failed after select(): Connection refused (111) 2018-03-01 21:47:43 Closing Masternode connection: peer=52, addr=145.239.235.17:39999 2018-03-01 21:47:43 Closing Masternode connection: peer=53, addr=145.239.235.22:29999 2018-03-01 21:47:43 Closing Masternode connection: peer=54, addr=145.239.235.29:19999 2018-03-01 21:47:43 Closing Masternode connection: peer=55, addr=145.239.235.30:19999 2018-03-01 21:47:43 Closing Masternode connection: peer=56, addr=183.60.231.12:19999 2018-03-01 21:47:43 CMasternodeMan::CheckAndRemove 2018-03-01 21:47:43 CMasternodeMan::CheckAndRemove -- Masternodes: 146, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 6, entries in Masternode list we asked for: 0, nDsqCount: 9 2018-03-01 21:47:43 CMasternodePayments::CheckAndRemove -- Votes: 26353, Blocks: 5011 2018-03-01 21:47:43 CInstantSend::CheckAndRemove -- Lock Candidates: 0, Votes 0 2018-03-01 21:47:43 CGovernanceManager::UpdateCachesAndClean -- Governance Objects: 32 (Proposals: 10, Triggers: 22, Watchdogs: 0/0, Other: 0; Erased: 0), Votes: 1225 2018-03-01 21:47:43 ThreadSocketHandler -- removing node: peer=52 addr=145.239.235.17:39999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:47:43 ThreadSocketHandler -- removing node: peer=53 addr=145.239.235.22:29999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:47:43 ThreadSocketHandler -- removing node: peer=54 addr=145.239.235.29:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:47:43 ThreadSocketHandler -- removing node: peer=55 addr=145.239.235.30:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:47:43 ThreadSocketHandler -- removing node: peer=56 addr=183.60.231.12:19999 nRefCount=2 fNetworkNode=1 fInbound=0 fMasternode=1 2018-03-01 21:48:12 UpdateTip: new best=0000000008c0a9ce7c384c03c3d64ed464a6b1b8ecff92bc09363b86fd2206d4 height=83986 log2_work=53.102284 tx=4846012 date=2018-03-01 21:47:55 progress=1.000000 cache=3.1MiB(21497txo) 2018-03-01 21:48:12 ProcessNewBlock : ACCEPTED 2018-03-01 21:48:43 CMasternodeMan::CheckAndRemove 2018-03-01 21:48:43 CMasternodeMan::CheckAndRemove -- Masternodes: 146, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 6, entries in Masternode list we asked for: 0, nDsqCount: 10 2018-03-01 21:48:43 CMasternodePayments::CheckAndRemove -- Votes: 26354, Blocks: 5011 2018-03-01 21:48:43 CInstantSend::CheckAndRemove -- Lock Candidates: 0, Votes 0 2018-03-01 21:49:43 CMasternodeMan::CheckAndRemove 2018-03-01 21:49:43 CMasternodeMan::CheckAndRemove -- Masternodes: 146, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 6, entries in Masternode list we asked for: 0, nDsqCount: 11

[thephez]

It looks like you have at least one connection because you received a new block. I only see a few refuse/error messages. There are a number of things that run periodically and generate some of these messages. The log looks fairly normal to me - is something not working?

[UdjinM6]

Testnet is fragmented, so it's ok that some nodes reject connections, some nodes forked off etc. Your node can connect to multiple masternodes, it received a correct block http://testnet-insight.dashevo.org/insight/block/0000000008c0a9ce7c384c03c3d64ed464a6b1b8ecff92bc09363b86fd2206d4 - I don't see any issues in this log, everything seems to work as designed.

[kiahmed]

ok..thanks