Quote from: spatula on August 22, 2016, 03:08:40 PM

Quote from: xxxgoodgirls on August 22, 2016, 03:03:41 PM

My MN is in the MN list but when it is shown as inactive. What to do?

You're probably running an older version. Upgrade to version .58 and it should fix your problem. Here is an example script I use for upgrade, modify it to your setup:

./dash-cli stop
rm dashd -fr
rm dash-cli -fr
rm rm .dash/debug.log .dash/peers.dat .dash/mncache.dat -fr
wget https://www.dashpay.io/binaries/dash-0.12.0.58-linux64.tar.gz
tar zxvf dash-0.12.0.58-linux64.tar.gz
mv dash-0.12.0/bin/dashd .
mv dash-0.12.0/bin/dash-cli .
chmod +x ./dashd
chmod +x ./dash-cli
./dashd
sleep 25
./dash-cli getinfo

Also:
./dash-cli masternode status

Your masternode is not really working until it appears both on the MN list and your MN reports back "Masternode successfully started" with the above command.
I had some MNs get on the wrong chain due to not being on version .58. It took me a while to discover the procedure to get MN activation to stick even after MNs were on the correct version and chain. Briefly:

1. Start your cold wallet. Let it load at least the masternode list and masternode winners.
2. Stop your remote MN: './dash-cli stop'
3. Start your remote MN: './dashd'
4. On the cold wallet side, use 'masternode start-alias' or 'masternode start-missing' to start the remote MN.
5. On your remote MN: './dash-cli masternode status'
6. Check the masternode list for the tx vin associated with your MN.

Do not let too much time lapse between step 3 and step 4. This is where the trouble lies. If you let an unactivated MN, also called a 'hot node', sit without being activated for too long, it won't start as a MN properly.