• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

docker masternode

europound

europound

Member
can it be run in docker container?
dashninja was showing active status for several hours then inactive
is ninja reliable?

how to check if masterrnode is working without dashmam and ninja?

Masternode information:
1000 DASH Vin (Hash-Index)
Pubkey
IP:port
Status Inactive (0%)
Port Check Status Open
Port Check Next Try 43 minutes 57 seconds
Daemon Version 0.12.2.1 (Protocol=70208)
Balance 1,000.000 DASH
Last Paid (from dashd) Never/Unknown
Last Paid (from blocks) Never/Unknown
Total Paid (Last month) 0.000 DASH (0 times / 0 missed / 0 hijacked)
Active Duration 16 hours 4 minutes 31 seconds
Last Seen 16/11/2017, 06:47:19 (9 minutes 12 seconds ago)





uc
 
Last edited:
Masternode Status Extended

Search:
Daemon ID Daemon Version Daemon Protocol Status Extended Status
dmn01 120201 70208 Inactive WATCHDOG_EXPIRED
dmn02 120201 70208 Inactive WATCHDOG_EXPIRED
dmn03 120201 70208 Inactive WATCHDOG_EXPIRED
p2pool 120201 70208 Inactive WATCHDOG_EXPIRED
 
what is sentinel for?

this is what I have in crontab
* * * * * cd /root/dashman/sentinel && venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log

and cannot find sentinel logs
root@e4658ba3ec87:~/dashman/sentinel/venv/bin# find / -name "sentinel-cron.log"
root@e4658ba3ec87:~/dashman/sentinel/venv/bin#
 
Last edited:
when I run docker exec -it masternode bash for the first time
dashman always says

masternode visible (ninja) : NO
masternode address :
masternode funding txn : -

but second try ./dashman status gives full info

why is that?

masternode@Ubuntu-1604-xenial-64-minimal:~$ docker exec -it masternode bash
dashman version 0.1.25 (37-g38fb02f) - Thu Nov 16 05:35:29 UTC 2017
gathering info, please wait... DONE!

hostname : xxxxxxxxxxxxxxxxxxxxx
host uptime/load average : 32 days, 1.19 0.66 0.55
dashd bind ip address : xxxxxxxxxxxxxxxxxxxxx
dashd version : 0.12.2.1
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 17 hours, 07 mins, 09 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 35
dashd blocks synced : YES
last block (local dashd) : 771515
(chainz) : 771515
(dash.org) : 771515
(dashwhale) : 771514
(masternode.me) : 771514 - no forks detected
dashd current difficulty : 51881777.91168378

masternode started : YES
masternode visible (local) : YES
masternode visible (ninja) : NO
masternode address :
masternode funding txn : -

masternode queue/count : 0/0
masternode mnsync state : MASTERNODE_SYNC_FINISHED
masternode network state :
masternode last payment : never
masternode balance : 1000.000000000
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : YES
Exiting.


root@:~/dashman# ./dashman status
dashman version 0.1.25 (37-g38fb02f) - Thu Nov 16 05:41:11 UTC 2017
gathering info, please wait... DONE!

hostname : xxxxxxxxxxxxxxxxxxxxx
host uptime/load average : 32 days, 0.45 0.49 0.50
dashd bind ip address : xxxxxxxxxxxxxxxxxxxxx
dashd version : 0.12.2.1
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 17 hours, 12 mins, 51 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 38
dashd blocks synced : YES
last block (local dashd) : 771517
(chainz) : 771517
(dash.org) : 771517
(dashwhale) : 771517
(masternode.me) : 771517 - no forks detected
dashd current difficulty : 45340592.73066429
masternode started : YES
masternode visible (local) : YES
masternode visible (ninja) : YES
masternode address : xxxxxxxxxxxxxxxxxxxxx
masternode funding txn : xxxxxxxxxxxxxxxxxxxxx
masternode queue/count : 3503/3959
masternode mnsync state : MASTERNODE_SYNC_FINISHED
masternode network state : ENABLED
masternode last payment : never
masternode balance : 1000.000000000
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : YES
Exiting.

root@:~/dashman#
 
root@e4658ba3ec87:~/dashman# ./dash-cli masternode debug
Masternode successfully started
root@e4658ba3ec87:~/dashman#
ed
root@e4658ba3ec87:~/dashman# ./dash-cli masternode list full | grep xxx2
"xxxxxxxxxxxxxxxxxxxxxxxxx": " ENABLED 70208 xxx 1510811869 62101 0 0 xxx:9999",
root@e4658ba3ec87:~/dashman#
 
and then dashninja is ok and sees dashd masternode :(
something is not right with docker or sentinel
what to do?

Masternode information:
1000 DASH Vin (Hash-Index) xxx
Pubkey xxxx
IP:port xxxx
Status Active (100%)
Port Check Status Open
Port Check Next Try 32 minutes 18 seconds
Daemon Version 0.12.2.1 (Protocol=70208)
Balance 1,000.000 DASH
Last Paid (from dashd) Never/Unknown
Last Paid (from blocks) Never/Unknown
Total Paid (Last month) 0.000 DASH (0 times / 0 missed / 0 hijacked)
Active Duration 17 hours 15 minutes 1 second
Last Seen 16/11/2017, 07:57:49 (11 minutes 17 seconds ago)
 
This all looks fine to me. Your masternode is clearly enabled, at full block height and moving through the payment queue. The problems are with the dashninja API. You've done everything right - just don't touch anything for ~7 days and you will be paid.
 
oh my god, i am a retard :(
in docker you have to start cron

root@e4658ba3ec87:~/dashman/sentinel# cd ..
root@e4658ba3ec87:~/dashman# cd ..
root@e4658ba3ec87:~# cd log
root@e4658ba3ec87:~/log# ls
root@e4658ba3ec87:~/log# crontab -e
crontab: installing new crontab
root@e4658ba3ec87:~/log# ls
root@e4658ba3ec87:~/log# ls -lh
total 0
root@e4658ba3ec87:~/log# crond status
bash: crond: command not found
root@e4658ba3ec87:~/log# service cron
* Usage: /etc/init.d/cron {start|stop|status|restart|reload|force-reload}
root@e4658ba3ec87:~/log# service cron status
* cron is not running
root@e4658ba3ec87:~/log# echo "Hello $(date)" >>/var/log/cron.log 2>&1
root@e4658ba3ec87:~/log# echo "Hello $(date)" >>cron.log 2>&1
root@e4658ba3ec87:~/log# ls -lh
total 4.0K
-rw-r--r-- 1 root root 35 Nov 16 15:46 cron.log
root@e4658ba3ec87:~/log# nano cron.log
root@e4658ba3ec87:~/log# nano cron.log
root@e4658ba3ec87:~/log# crontab -e
crontab: installing new crontab
root@e4658ba3ec87:~/log# apt-get install cron
Reading package lists... Done
Building dependency tree
Reading state information... Done
cron is already the newest version (3.0pl1-128ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@e4658ba3ec87:~/log# service cron status
* cron is not running
root@e4658ba3ec87:~/log# service cron start
* Starting periodic command scheduler cron [ OK ]
root@e4658ba3ec87:~/log# service cron status
* cron is running
root@e4658ba3ec87:~/log# ls -lh
total 4.0K
-rw-r--r-- 1 root root 35 Nov 16 15:46 cron.log
root@e4658ba3ec87:~/log#
total 12K
drwxrwxrwx 2 root root 4.0K Nov 16 15:49 .
drwx------ 9 root root 4.0K Nov 16 14:25 ..
-rw-r--r-- 1 root root 105 Nov 16 15:50 cron.log
root@e4658ba3ec87:~/log#
 
is this crontab correct?




# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
* * * * * echo "Hello $(date)" >>/root/log/cron.log 2>&1
* * * * * cd /root/dashman/sentinel && venv/bin/python bin/sentinel.py >> sentinel-cron.log 2>&1
* * * * * ./root/dashman/dashd & 2>&1
 
root@e4658ba3ec87:~/dashman# cd /root/dashman/sentinel && venv/bin/python bin/sentinel.py >> sentinel-cron.log 2>&1
root@e4658ba3ec87:~/dashman/sentinel# crontab -e
No modification made
root@e4658ba3ec87:~/dashman/sentinel# ./root/dashman/dashd & 2>&1
[1] 9202
root@e4658ba3ec87:~/dashman/sentinel# bash: ./root/dashman/dashd: No such file or directory

[1]+ Exit 127 ./root/dashman/dashd
root@e4658ba3ec87:~/dashman/sentinel# ./root/dashman/dashd & 2>&1
[1] 9203
root@e4658ba3ec87:~/dashman/sentinel# bash: ./root/dashman/dashd: No such file or directory
^C
[1]+ Exit 127 ./root/dashman/dashd
root@e4658ba3ec87:~/dashman/sentinel# crontab -e
No modification made
root@e4658ba3ec87:~/dashman/sentinel# ./root/dashman/dashd & 2>&1
[1] 9215
root@e4658ba3ec87:~/dashman/sentinel# bash: ./root/dashman/dashd: No such file or directory

[1]+ Exit 127 ./root/dashman/dashd
root@e4658ba3ec87:~/dashman/sentinel#



why do I get this error?
 
why sentinel.log is empty?


drwxrwxrwx 2 root root 4.0K Nov 16 16:06 .
drwx------ 9 root root 4.0K Nov 16 15:54 ..
-rw-r--r-- 1 root root 665 Nov 16 16:06 cron.log
-rw-r--r-- 1 root root 924 Nov 16 16:06 dashd.log
-rw-r--r-- 1 root root 0 Nov 16 16:03 sentinel-cron.log
root@e4658ba3ec87:~/log#


how to check if sentinel is working?
this does not help

#
# m h dom mon dow command
* * * * * echo "Hello $(date)" >>/root/log/cron.log 2>&1
* * * * * cd /root/dashman/sentinel && venv/bin/python bin/sentinel.py >>/root/log/sentinel-cron.log 2>&1
* * * * * sh -c "cd /root/dashman/ && ./dashd &" >>/root/log/dashd.log 2>&1
 
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.
Dash Core server starting
Dash Core server starting
 
Now you have put the wrong thing in your crontab. Only sentinel should be in crontab, not dashd. If you keep trying to micromanage your masternode like this, you will likely make a mistake and get knocked out of the payment list. We already confirmed it was working yesterday - just stop fiddling and you will get paid.
 
Please don't start the dashd server every minute, thats crazy! :D

Sentinel is an important part of dash - it does important things lol, so don't worry
 
You must log in or register to reply here.
Back
Top