EDIT (12 hours later): Seems that the Masternode works properly, I just received first reward
_____________________
Hi,
I have trouble with masternode.
It seems that it has issue to connect to its own IP:PORT
synx@GlassAutomatic-VM:~$ cli masternode status
{
"vin" : "CTxIn(COutPoint(abcdef1234, 1), scriptSig=)",
"service" : "104.XXX.YYY.ZZ:9999",
"status" : 9,
"pubKeyMasternode" : "Sxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"notCapableReason" : "Could not connect to 104.XXX.YYY.ZZ:9999"
}
cli masternode connect 104.XXX.YYY.ZZ:9999
error connecting
but when I try to connect from outside from my desktop control wallet it gets through
cli masternode connect 104.XXX.YYY.ZZ:9999
successfully connected
synx@GlassAutomatic-VM:~$ netstat -tlpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN 502/cli
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::22348 :::* LISTEN 502/cli
synx@GlassAutomatic-VM:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9697 (9.6 KB) TX bytes:9697 (9.6 KB)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:7654 errors:0 dropped:0 overruns:0 frame:0
TX packets:8116 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1380241 (1.3 MB) TX bytes:1871125 (1.8 MB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:104.XXX.YYY.ZZ P-t-P:104.XXX.YYY.ZZ Bcast:104.XXX.YYY.ZZ Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
I am able to open connection to the port on VPS localhost
synx@GlassAutomatic-VM:~$ nc 127.0.0.1 9999
seept��� ... (lots of binary stuff)
but the client seems issues with connecting itself.
When I run the
cli masternode list I can see my TXID ENABLED
So the question - is this cosmetic issue and the masternode is running even if it cant ping itself but the others can or I need to figure this out? Has anyone similar issue?
Using virmach.com VM
Configuration:Syndicate.conf
Masternode:
rpcuser=
rpcpassword=
rpcallowip=127.0.0.1
daemon=1
maxconnections=8
server=1
listen=1
masternode=1
logtimestamps=1
masternodeprivkey=6_masternode_key
externalip=104.XXX.YYY.ZZ:9999
bind=0.0.0.0
masternodeaddr=104.XXX.YYY.ZZ:9999
Controll wallet
rpcuser=
rpcpassword=
rpcallowip=127.0.0.1
rpcport=xxxx
#server=1
#listen=1
daemon=1
logtimestamps=1
mnconflock=0
addnode=104.XXX.YYY.ZZ
masternode.conf (control wallet only)
MN 104.XXX.YYY.ZZ:9999 MY_MASTERNODE_SECRET MY_MASTERNODE TX 1
Thanks for any help :-)