Masternode not showing up anywhere.

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
Hi, I got 10 masternodes.
9 of them work fine and as expected. I used the same scripts for all of them to configure them.
1 of them is just not showing up anywhere, neither on https://elbzo.net/masternodes.html nor on darkcoind masternode list of the own instance.

Getinfo:
Code:
0 ✓ [email protected] ~ $ darkcoind getinfo
{
    "version" : 101001,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 1000.00000000,
    "blocks" : 88562,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 4863.38805289,
    "testnet" : false,
    "keypoololdest" : 1399464037,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
IP:
Code:
0 ✓ [email protected] ~ $ GET http://169.254.169.254/latest/meta-data/public-ipv4; echo
54.79.94.248
Masternode:
Code:
0 ✓ [email protected] ~ $ darkcoind masternode count
306
0 ✓ [email protected] ~ $ darkcoind masternode debug
successfully started masternode
0 ✓ [email protected] ~ $ darkcoind masternode list | grep 54.79.94.248
1 ✗ [email protected] ~ $
Public list:
Code:
0 ✓ [email protected] ~ $ lynx -dump https://elbzo.net/masternodes.html | grep -A3 "54.79.94.248"
1 ✗ [email protected] ~ $
Any idea what else I could try?
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Dirty fix in stop local and remote, revert back to masternode=0, generate new remote IP & masternodeprivkey, and fire it all up again.
Not an elegant solution, but it basically creates a new Masternode in the eyes of the network.
 

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
Dirty fix in stop local and remote, revert back to masternode=0, generate new remote IP & masternodeprivkey, and fire it all up again.
Not an elegant solution, but it basically creates a new Masternode in the eyes of the network.
I tried that, created a new masternode with new private key and and new external IP. Now the IP is 54.79.18.229 and the behaviour is the same.