i think its :okay, sorry a bit of a newbie, if you give me the full commands that would be helpful. is it dash-cli reindex
I guess payment enforcement is off currently ? (0 means off i assume, when you use command "spork show" and see a 0 behind the payment enforcement spork??)
Because Dashninja shows this :
http://184.108.40.206/~pub/Dash/Dash_Info.html still shows payment enforcement "on" by the way.
strange that miner XxKuNB5rQvMQFnTwak84c7AaBtkUmoHzEH can get away with not paying masternode fees, normally the block is thrown out then i think ?0 means on, as far as I know. The command “spork active” gives a true/false output IIRC.
strange that miner XxKuNB5rQvMQFnTwak84c7AaBtkUmoHzEH can get away with not paying masternode fees, normally the block is thrown out then i think ?
Since there is no protocol update this time (which would require a start command=pushing back at the end of the queue), I decided to update the MN without waiting for the payment. Starting the MN after the update, I'm on the same place on queue as before. So, in my case updating went really smoothly.We shouldn't wait for a payment anymore?
Don't remember exactly and don't have access right now, but it's ESXi with something like i7 4770.Server specs please?
Ok, but its more powerful than my 1 x 2.4 Ghz core and 1 Gb ram nodes.Don't remember exactly and don't have access right now, but it's ESXi with something like i7 4770.
For Dash VM - 1 core and 1Gb RAM.
That can sometimes be a bug, check elsewhere before issuing a new start or you may lose position in queue.I did not do anything, had 12.2.1 and status ENABLED, bud now suddenly i have status NEW_START_REQUIRED.
I did not change anything.
The paths seem incorrect (dash instead of dashcore), maybe someone can update it.
Also there is a typo in the linux (darsh.conf?)
Yes, i also have 25 years experience in the computer field + building and overclocking.I would advice you to upgrade to at least a dual core server, I know it cost a bit more, but it's allot cheaper than missing a payment. At any-rate running 100% CPU power especially on a single core CPU, will most-likely result in your system failing one way or the other. In fact CPU usage around 70%, is much better upper limit to have. I only speak out of my experience as professional and overclocking as a hobby, both from what I have seen and heard. Take it or leave it either way you don't even have to spend 1% of your total profits of running a MN on a dual core or better.
Memory should never be full either, because once it's full you'll have to go the SSD for extra memory, rough estimate would be that is 10x slower.
But any rate I gladly take your spot in line to receive the next masternode payment first (joke)
The protocol version changed with this update. You'll need to update your local cold wallet too and issue a start to make it work again.That can sometimes be a bug, check elsewhere before issuing a new start or you may lose position in queue.