Help with Chaeplin's guide - masternode works then sleeps

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
Hi,

I'm being brave :) and having a go at setting up a masternode using Chaeplin's guide.

As far as I am concerned, everything went perfectly however after 4 hours of looking like it was ok I am now getting port 9999 closed and daemon version denied when I check its status. Debug.log looked like the masternode was doing what a masternode should be doing.

https://drk.mn/masternodes.html#XghNBzUP6zJnB5Q6UYj4HEWoSRcvxGcByK

Any ideas what is wrong? I saw no error messages whilst I followed the guide and have retraced my steps so many times now that I am getting lost and confused. I don't mind admitting that I didn't understand every step of the guide...the biggest knowledge gap (I think) for me with Linux is accounts and permissions. When I finished the set up and I got a successful message with the local wallet I simply closed the terminal window...perhaps my terminal session had elevated permissions and timed out?

Shameless chaeplin namedrop.

Thanks,

Stonehedge
 
Last edited by a moderator:

karisu

Member
Jun 30, 2014
70
26
58
how have you started your darkcoind daemon on the remote server? If you check if the debug.log of the remote and local what are the last timestamps?
If you are new to linux these commands will help a lot
tail -f <path to debug.log> ( gives you like a continuos flow of the last lines in the log file )
byobu ( starts a new terminal, use F2 key to create a new one, do several things in differnt terminal, press F6 to leave that screen, when you log in the server and start byobu again everything is like when you left )
 
  • Like
Reactions: stonehedge

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
I have to run the following commands before even seeing the darkcoin files:

sudo passwd -l root
sudo su -
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
Last entries in remote debug.log:

Code:
2014-08-29 18:00:11 net thread interrupt
2014-08-29 18:00:11 Flushed 10113 addresses to peers.dat  50ms
2014-08-29 18:00:11 Committing 806 changed transactions to coin database...
2014-08-29 18:00:11 Flush(true)
2014-08-29 18:00:11 wallet.dat refcount=0
2014-08-29 18:00:11 wallet.dat checkpoint
2014-08-29 18:00:11 wallet.dat detach
2014-08-29 18:00:11 wallet.dat closed
2014-08-29 18:00:11 DBFlush(true) ended              17ms
2014-08-29 18:00:11 Shutdown : done
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
Code:
2014-08-29 18:00:05 dsee - Got NEW masternode entry 31.210.52.213:9999
2014-08-29 18:00:05 dsee - Rejected masternode entry
2014-08-29 18:00:05 dsee - Got NEW masternode entry 54.183.200.153:9999
2014-08-29 18:00:05 dsee - Rejected masternode entry
2014-08-29 18:00:05 dsee - Got NEW masternode entry 31.210.52.213:9999
2014-08-29 18:00:05 dsee - Rejected masternode entry
2014-08-29 18:00:05 dsee - Got NEW masternode entry 31.210.52.213:9999
2014-08-29 18:00:05 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:06 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:06 dsee - Rejected masternode entry
2014-08-29 18:00:07 dsee - Got NEW masternode entry 108.61.198.205:9999
2014-08-29 18:00:07 dsee - Rejected masternode entry
2014-08-29 18:00:11 Shutdown : In progress...
2014-08-29 18:00:11 Flush(false)
2014-08-29 18:00:11 wallet.dat refcount=0
2014-08-29 18:00:11 wallet.dat checkpoint
2014-08-29 18:00:11 wallet.dat detach
2014-08-29 18:00:11 addcon thread interrupt
2014-08-29 18:00:11 dumpaddr thread stop
2014-08-29 18:00:11 opencon thread interrupt
2014-08-29 18:00:11 msghand thread interrupt
2014-08-29 18:00:11 wallet.dat closed
2014-08-29 18:00:11 DBFlush(false) ended              21ms
2014-08-29 18:00:11 StopNode()
Shutdown in progress??
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
This is very annoying. I have no idea what I have done wrong. I thought i had followed Chaeplin's guide to the letter and the node started locally with no problems at all. For several hours it was coming up green across the board on drk.mn. I'm assuming the times will be in UTC which is even weirder because drk.mn is still showing this node as running although with port 9999 closed.

Yidakee is on holiday. Anybody fancy helping me build a node for DRK? This is so frustrating...I have finally managed to get the third of my first three running fine and I was hoping that I could get number 4 up and running with the knowledge I have picked up on the way.
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
Code:
Chain INPUT (policy ACCEPT)
target     prot opt source               destination        
REJECT     tcp  --  anywhere             anywhere             tcp dpt:9998 reject-with tcp-reset
REJECT     tcp  --  anywhere             anywhere             tcp dpt:9999 flags:FIN,SYN,RST,ACK/SYN #conn src/24 > 8 reject-with tcp-reset
REJECT     tcp  --  anywhere             anywhere             tcp dpt:9999 flags:FIN,SYN,RST,ACK/SYN #conn src/32 > 2 reject-with tcp-reset
ACCEPT     tcp  --  anywhere             anywhere             ctstate NEW tcp dpt:9999
ACCEPT     tcp  --  anywhere             anywhere           

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination        

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:9999 ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp spt:9999
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:9999
ACCEPT     all  --  anywhere             anywhere
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
Fixed. It was really obvious. I installed darkcoind on remote as root rather than ubuntu user. I've tided that up now.