Quote from: Honest Tim on February 01, 2016, 07:23:10 PM

Quote from: dihydrogenmonoxide on February 01, 2016, 06:57:42 PM

Quote from: Honest Tim on February 01, 2016, 06:39:36 PM

Quote from: GhostPlayer on February 01, 2016, 01:41:50 PM

Quote from: Honest Tim on February 01, 2016, 01:07:55 PM

Yeah, been running for almost a year now. 768Meg, never had any probs before. Nothing has changed.

HDD ? How long since you've dumped the debug.log? Also, keep in mind Dashninja may have it's quirks from time to time. If Elb is working the backend, some funky info may result from it.

Did you try list | grep xx.xx.xx.xx ?

hmmm. Is there a way to search by IP address now?? It appears you need to search by Vin (Hash-Index), now that we use "dash-cli" Huh

Unless theres a switch somewhere??

This gives me hope..... but also a headache!

root@vultr:~/.dash# ./dash-cli masternodelist help
error: {"code":-1,"message":"masternodelist ( \"mode\" \"filter\" )\nGet a list of masternodes in different modes\n\nArguments:\n1. \"mode\" (string, optional/required to use filter, defaults = status) The mode to run list in\n2. \"filter\" (string, optional) Filter results. Partial match by IP by default in all modes,\n additional matches in some modes are also available\n\nAvailable modes:\n activeseconds - Print number of seconds masternode recognized by the network as enabled\n (since latest issued \"masternode start/start-many/start-alias\")\n addr - Print ip address associated with a masternode (can be additionally filtered, partial match)\n full - Print info in format 'status protocol pubkey IP lastseen activeseconds lastpaid'\n (can be additionally filtered, partial match)\n lastseen - Print timestamp of when a masternode was last seen on the network\n lastpaid - The last time a node was paid on the network\n protocol - Print protocol of a masternode (can be additionally filtered, exact match))\n pubkey - Print public key associated with a masternode (can be additionally filtered,\n partial match)\n rank - Print rank of a masternode based on current block\n status - Print masternode status: ENABLED / EXPIRED / VIN_SPENT / REMOVE / POS_ERROR\n (can be additionally filtered, partial match)\n"}

The answer is in the output you provided

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full

or to filter by specific IP

Code:

root@vultr:~/.dash# ./dash-cli masternodelist full 127.0.1.47

Thank you Sir. I just didn't know how to go that final step with the syntax.

Anyway, this proves that this particular masternode is not live, which is very irritating as it's still simply "falling off" the dash ninja radar.

maybe put both cold and hot wallet on latest version (.56) as that has some bug fixes and give it a restart from cold wallet just to be sure ?
followed by ./dash-cli masternodelist full | grep -e IPADDRESS to make sure its enabled ? (just thinking outloud here...)

edit : and maybe delete your peers.dat before the restart...
edit : and check if your debug.log on the hot wallet (server) has not grown too large..
edit : and check if both your wallets are in total sync with the blockchain before restart from cold wallet (you can check here for example : https://chainz.cryptoid.info/dash/)