Powered by Dash
Dash Core Team
- May 9, 2014
I've always had the wallets on the servers but my MNs keep appearing/disappearing. I can see them most of the time, but for brief periods they go away.
like literally?For some odd reason, it shows in the local wallets debug window as active. =1 but on Chaeplins website it's not listed at all.
Edit: I added darkcoin.io:9999 as a node to my local config. That seems to of resolved the issue. As long as the local wallet is never shutdown, it seems to remain in the list.
I wonder if 126.96.36.199:9999 would also work maybe? I'll try
EDIT: with 23.23.131:9999 ... server sees 106 MN, and dozens of duplicates. Local sees 66
with darkcoin.io:9999 ... server sees 72 MN, local sees 80
Still can't see mine. Seems local / remote is broken. Evan!! Dont kill the beauty of this setup !!
Nope... two days at it and no success at all. With this new update it seems the local IP gets registered, not the server side. So there is no point in having like 10 local VM linux darkcoinds with 1k deposit each, pointing to individual remote server IPs, validating MN status.I have notice that if I "PAT" the 9999 port to my local wallet PC my MN stays alive (status =1). If I remove the "PAT" rule from my router the MN switch to status =0 after 10 mins or so.
So I guess the darkcoin daemon must be accessible from both the local AND the remote machine.
- Start darkcoind on your remote wallet
- Setup your (home) router so you can reach the 9999 port of your local wallet
- Start darkcoind on your local wallet machine with: "darkcoind -masternodeaddr=<remotewalletip>:9999" followed by
"darkcoind walletpassphrase <passphrase> 60" followed by
"darkcoind masternode start <passphrase>"
- Test your config by scanning the 9999 port of your local wallet machine (using your remote wallet linux): "nmap <localwalletip> -p 9999 -Pn " nmap should return something like: 9999/tcp open
I don't like it but it's better than a dead MasterNode I guess.
Hope this help!
Are you starting your darkcoind witth 'darkcoind -daemon' ?Sorry, I don't know.
I have a question. Apparently, when I start my masternode in putty, then close putty, I turn my masternode off. Previously, this didn't happen. There is a difference in behavior though. When I start my darkcoind, it freezes. I have to open another putty to do the masternode command. Previously, turning darkcoind on would not freeze in the window. I need my masternode to run when Putty is closed. My desktop isn't always on, and not reliable to be on at all times. Anybody know what's going on? I'd sure appreciate any help anyone can give! Thanks so much
host:~$ test="this is a test" host:~$ echo $test this is a test host:~$ echo "$test" this is a test host:~$ echo '$test' $test
Masternodes, please restart!
I've noticed some nodes popping in and out of the masternode lists. I'd like all of the masternodes to follow these instructions to see if the problem gets fixed
1.) stop the daemon
2.) update to 10.8.6 if you haven't
3.) add "maxconnections=200" to your configuration
4.) wait ten minutes (it MUST be ten minutes! This will allow the masternode election entry to propagate)
5.) start the daemon and turn on the masternode
Same here. And I'm seeing a lot of these error messages in the log, not sure if related:
I am having this same issue for days, like in 4 different nodes. I just went back to having only one until everything is clear. But I am glad to know I am not the only one with this issue.Same here. And I'm seeing a lot of these error messages in the log, not sure if related:
ProcessMessage(dsee, 175 bytes) FAILED
According to Evan, if you update to 10.8.6, delete peers.dat, wait 10 min & restart the client & masternode, you should be ok. The "ProcessMessage(dsee, 175 bytes) FAILED" errors are apparently due to other masternodes on the network that are still running the old version.I am having this same issue for days, like in 4 different nodes. I just went back to having only one until everything is clear. But I am glad to know I am not the only one with this issue.