It was created about 7 days ago and I received a reward once, but when I checked the Platform Balance on https://mnowatch.org/evonodes/, it was 0.
created a dash evo according to the process, no income
- Thread starter ritech
- Start date
You are smart to check the evonodes page! It has a lot of information there! Did you check your additional details to make sure you are running the correct versions and the ports are open?
A working node should look a lot like this.
qwizzie
Well-known member
If you do these commands, what do you see ?
dashmate status
dashmate status core
dashmate status masternode
dashmate status platform
dashmate status services
Anything returning red with these commands = your Evonode having a problem that you need to look into.
Also remember each epoch has a time period of 9.125 days and Platform credits only get distributed to Evonodes at the very end of each epoch.
If you started your Evonode 7 days ago, you may have started it at the very start of epoch 1, which will end in two days (15th of September 2024). If above commands do not return anything red and everything looks good on mnowatch, then wait a few days untill epoch 1 ends and the Evonodes get their Platform credits for epoch 1.
To see with which Platform block a specific epoch started and the date of that Platform block :
https://platform-explorer.pshenmic.dev/epoch/1 (change 1 to a different number in case of future epochs) : epoch 1 started with block 2262
https://platform-explorer.com/ : search for '2262', block 2262 started 9/6/2024, 2:52:46 AM + 9.125 days --> epoch 1 will end 15th of September 2024 / around that date.
You can also use the following site to keep track of the number of proposed blocks that your Evonode already accumulated during these 7 days (1 proposed block roughly translate to 1.2 dash) :
https://platform-explorer.com/validators (search with your protx hash on 'All' tab, once it find your Evonode : bookmark that specific web page for easy access)
Last edited:
qwizzie
Well-known member
Check your Evonode here : https://mnowatch.org/evonodes/ (scroll down until you reached section 'All Evonodes' and do ctrl+F and search on your ip address or protx hash). Verify the following :
Status : should be E
Active (YNU) : should be Y
Protocol version : should be 70233
User agent : should be /Dash Core:21.1.0/
Platform ChainID : should be evo1
Platform protocol version : should be 1
DAPI version : should be 1.2.0
Drive version : should be 1.2.0
Tenderdash version : should be 1.2.1
Platform Height : should be 6034
Platform Epoch : should be 1
http port : should be green (443 - open)
p2p port : should be green (26656 - open)
Do also 'dashmate status services' once more and report back the Dashmate Helper version number (this is basically your Dashmate version).
It should show : dashpay/dashmate-helper:1.2.0
Last edited:
On the website, everything is normal except Platform Epoch :0
Service │ Container ID │ Image │ Status ║
║ Dashmate Helper │ 00a4418421cf │ dashpay/dashmate-helper:1.2.0 │ running ║
║ Core │ 1bd2f827ecab │ dashpay/dashd:21 │ running ║
║ Drive ABCI │ 3bfde55e259a │ dashpay/drive:1 │ running ║
║ Drive Tenderdash │ 25af6e41d443 │ dashpay/tenderdash:1 │ running ║
║ DAPI API │ f409ddd5cf67 │ dashpay/dapi:1 │ running ║
║ DAPI Transactions Filter Stream │ 3d1f19c32d9b │ dashpay/dapi:1 │ running ║
║ Gateway │ 23d9fa4f46c4 │ dashpay/envoy:1.30.2-impr.1 │ running ║
║ Gateway rate limiter │ 6fba9d4397ca │ envoyproxy/ratelimit:3fcc3609 │ running ║
║ Gateway rate limiter storage │ 39df69d2c90f │ redis:alpine │ running ║
Service │ Container ID │ Image │ Status ║
║ Dashmate Helper │ 00a4418421cf │ dashpay/dashmate-helper:1.2.0 │ running ║
║ Core │ 1bd2f827ecab │ dashpay/dashd:21 │ running ║
║ Drive ABCI │ 3bfde55e259a │ dashpay/drive:1 │ running ║
║ Drive Tenderdash │ 25af6e41d443 │ dashpay/tenderdash:1 │ running ║
║ DAPI API │ f409ddd5cf67 │ dashpay/dapi:1 │ running ║
║ DAPI Transactions Filter Stream │ 3d1f19c32d9b │ dashpay/dapi:1 │ running ║
║ Gateway │ 23d9fa4f46c4 │ dashpay/envoy:1.30.2-impr.1 │ running ║
║ Gateway rate limiter │ 6fba9d4397ca │ envoyproxy/ratelimit:3fcc3609 │ running ║
║ Gateway rate limiter storage │ 39df69d2c90f │ redis:alpine │ running ║
I've been trying to get everything set up for many days now... but I just can't get everything to work... then while everything is synchronizing, I'm getting rid of the ban, the problem is with port 26656. And most likely the problem is not in the port, but in the docker container. Now the kernel is still running... drive is still running... but the platform is not synchronizing and Thunderdash is still not running
qwizzie
Well-known member
@tfoto see https://github.com/dashpay/platform/issues/2100 Check if your VPS has IPv6 enabled, that could cause false reporting of close ports like 26656 in Dashmate. Check if your Evonode ip address with port 26656 is open through an online port checker. If your server has IPv6 enabled, you will need to disable it, to force all traffic to go through IPv4. Also make sure port 26656 is allowed in your ufw firewall (sudo ufw status).
With regards to dashmate_dbb2a15d_mainnet-drive_tenderdash-1 constantly restarting :
dashmate status services (copy the container id of tenderdash)
docker logs containerIDofTenderdash
Anything in that log pointing to an ERROR ? or a FAULT ?
Do not update to Dashmate v1.3.0 it is just a dev build.
Also please don't use a lot of seperate posts, just edit your original post with additional questions / remarks.
With regards to dashmate_dbb2a15d_mainnet-drive_tenderdash-1 constantly restarting :
dashmate status services (copy the container id of tenderdash)
docker logs containerIDofTenderdash
Anything in that log pointing to an ERROR ? or a FAULT ?
Do not update to Dashmate v1.3.0 it is just a dev build.
Also please don't use a lot of seperate posts, just edit your original post with additional questions / remarks.
Last edited:
maybe you are out of sync? what is your node's platform block height? could you post more status outputs?
you can also use dashmate doctor command to generate a report and send it over to the [email protected] so they can investigate
qwizzie
Well-known member
Source : https://docs.dash.org/en/stable/docs/user/masternodes/server-config.html#server-config
Above source link also contains instructions on how to disable IPv6, if its already setup on your server !!
Last edited:
qwizzie
Well-known member
If sync is in progress, then that good. Wait for full sync.
If you disabled IPv6 (as recommended by DCG) and checked through 'sudo ufw status' that port 26656 is indeed added and allowed in your ufw (firewall) and you also checked your ip address & port 26656 through an online port checker and it is indeed open, then the 'closed' port status in Dashmate is just false reporting of that port in Dashmate (which gets its data from mnowatch). You can then just ignore it, i guess.
You still need to get the logs from your tenderdash container (as i mentioned before) to see if anything is wrong with your Tenderdash, as it was stuck in status 'restarting'.
Or you can try these commands to see if your Tenderdash container will get back to running without problems :
dashmate stop --platform
dashmate reset --platform
dashmate update
dashmate start --platform
Wait a few minutes
dashmate status platform
dashmate status services
Last edited:
the port in the firewall is open. but not accessible from the outside. I tried to turn off dashmate and attach another service to this port and then the port is open. but when I started dashmate again it is closed again. yesterday the logs were like this:
node_key.json` ("/tenderdash/config/node_key.json: ERROR: failed to create node"),
node_key.json` ("/tenderdash/config/node_key.json: ERROR: failed to create node"),
qwizzie
Well-known member
Just ignore closed port status of port 26656 in Dashmate, most likely it is just incorrect port status reporting from Dashmate.
Try these commands and see if that fix your problem with Tenderdash :
dashmate stop --platform
dashmate reset --platform
dashmate update
dashmate start --platform
wait few minutes
dashmate status platform
dashmate status services
If above command do not help, try :
dashmate stop
dashmate reset --keep-data
dashmate update
dashmate start
wait few minutes
dashmate status platform
dashmate status services
If that does not help, try :
dashmate stop
dashmate reset --keep-data --hard
dashmate update
dashmate start
wait few minutes
dashmate status platform
dashmate status services
Last edited:
tried it all...didn't work..
now it's synchronizing at 25%, I'll wait until the end.
the platform may start and the port may open, but now it's closed.
can it open after syncing?
Last edited:
qwizzie
Well-known member
1 : Wait for full sync (100%) !!!
2 : dashmate status services
3 : if all services are running, you are good. If Tenderdash is restarting on command 'dashmate status services', try commands from above comment of mine --> https://www.dash.org/forum/index.ph...g-to-the-process-no-income.55290/#post-239511
4 : ignore closed port 26656 in Dashmate.