TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
November 16, 2014, 05:34:11 AM |
|
Well, last resort, I'm changing my ip addresses and wallets, getting a new masternode key and hopefully this will work. Damn I hate to do it, but it may be the only hope I have
|
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d
|
|
|
ddink7
Legendary
Offline
Activity: 1120
Merit: 1000
|
|
November 16, 2014, 05:55:14 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
Perhaps this will help: (Based on https://darkcointalk.org/threads/50-dark-bounty-for-masternode-guide-update.2721/) Create masternode.conf in your Darkcoin working directory and put in the IP address of your MNs and their privkeys, like below: 192.168.0.1:9999 7qspZZJD3wsPifSzxZGnzo4HhR5Pd9MN2X9kGk4gPZi4LMJSvrE 192.168.0.2:9999 7rDDK21opuSHuu7eV2LdmBAunXWRUhVU3ZVek3frqYisnF4HyJL Move DRK into your wallet in 1000 DRK increments. Then go to the console and use: masternode start-many <password>
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
November 16, 2014, 05:59:49 AM |
|
Yup, one shows Sunday's date and the other shows Saturday's date (it's still Saturday here)
Make date -u (in case you are on diferent time zone on your server) Yes maybe this ... look : 2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2 I remember installing ntp on my remotes, I don't think it's on my local. I'm slow, and working on this. I will update if this helps, sorry for the time span!!! But thanks so far, it's my best bet! Yes sure it's the remote. I see 4 min less on your remote and the message say : too far into the past Just put 4 min more on your remote. Or as root on both : ntpdate ntp.online.net Well, I was pretty slow putting the info up, LOL. That could account for it, but now they are both using ntp and I've changed the IP address and the masternode private key, and yet, I still get "not a capable masternode. I'm at my wit's end.
|
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d
|
|
|
oblox
Legendary
Offline
Activity: 1442
Merit: 1018
|
|
November 16, 2014, 06:42:45 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below: ip address of remote masternode:9999 MASTERNODE_GEN_KEY ip address of remote masternode2:9999 MASTERNODE_GEN_KEY Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue: masternode start-many PASSPHRASE Not sure it can get any more detailed then that.
|
|
|
|
DiCE1904
Legendary
Offline
Activity: 1118
Merit: 1002
|
|
November 16, 2014, 06:45:06 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in, import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Create a masternode.conf file in the darkcoin data folder with the format below: ip address of remote masternode:9999 MASTERNODE_GEN_KEY ip address of remote masternode2:9999 MASTERNODE_GEN_KEY and so on and so forth. Then load the new wallet, go to the debug command prompt and issue masternode start-many PASSPHRASE. If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
Perhaps this will help: (Based on https://darkcointalk.org/threads/50-dark-bounty-for-masternode-guide-update.2721/) Create masternode.conf in your Darkcoin working directory and put in the IP address of your MNs and their privkeys, like below: 192.168.0.1:9999 7qspZZJD3wsPifSzxZGnzo4HhR5Pd9MN2X9kGk4gPZi4LMJSvrE 192.168.0.2:9999 7rDDK21opuSHuu7eV2LdmBAunXWRUhVU3ZVek3frqYisnF4HyJL Move DRK into your wallet in 1000 DRK increments. Then go to the console and use: masternode start-many <password> Thanks to both of you, ill give it a shot tomorrow and see how it works out.
|
|
|
|
Dave5
Member
Offline
Activity: 109
Merit: 10
|
|
November 16, 2014, 07:01:25 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below: ip address of remote masternode:9999 MASTERNODE_GEN_KEY ip address of remote masternode2:9999 MASTERNODE_GEN_KEY Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue: masternode start-many PASSPHRASE Not sure it can get any more detailed then that. MASTERNODE_GEN_KEY it that the key from remote or local? do i still need to enter a key also in the darkcoin.conf? what do i have to put in the darkcoin.conf for that seup? Thanks!
|
|
|
|
jiggytom
Legendary
Offline
Activity: 1068
Merit: 1020
|
|
November 16, 2014, 07:12:05 AM |
|
masternode.conf is the darkcoin.conf...I believe.
|
BTC: 174MGp3R5prNbuen31Kx5G5XuyuAXu9jye LBC: bWYN8NXGKWsgEAd6tQnJ5YRo2Z4r6PjxBH
|
|
|
oblox
Legendary
Offline
Activity: 1442
Merit: 1018
|
|
November 16, 2014, 07:18:41 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below: ip address of remote masternode:9999 MASTERNODE_GEN_KEY ip address of remote masternode2:9999 MASTERNODE_GEN_KEY Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue: masternode start-many PASSPHRASE Not sure it can get any more detailed then that. MASTERNODE_GEN_KEY it that the key from remote or local? do i still need to enter a key also in the darkcoin.conf? what do i have to put in the darkcoin.conf for that seup? Thanks! You still need to enter it in the remote darkcoin.conf. That masternode gen key is what you generate at the beginning with "masternode genkey". It's the same private key that would go in the darkcoin.conf file on both remote and local the old way. This masternode.conf file is your new local conf in addition to your existing darkcoin.conf with the masternode=1 setting.
|
|
|
|
oaxaca
|
|
November 16, 2014, 08:03:25 AM |
|
"not a capable masternode."
Isn't that the error message when you "break" the masternode by touching the 1000 DRK at the original address? Have you looked in coin control?
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
November 16, 2014, 08:34:17 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below: ip address of remote masternode:9999 MASTERNODE_GEN_KEY ip address of remote masternode2:9999 MASTERNODE_GEN_KEY Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue: masternode start-many PASSPHRASE Not sure it can get any more detailed then that. MASTERNODE_GEN_KEY it that the key from remote or local? do i still need to enter a key also in the darkcoin.conf? what do i have to put in the darkcoin.conf for that seup? Thanks! You still need to enter it in the remote darkcoin.conf. That masternode gen key is what you generate at the beginning with "masternode genkey". It's the same private key that would go in the darkcoin.conf file on both remote and local the old way. This masternode.conf file is your new local conf in addition to your existing darkcoin.conf with the masternode=1 setting. Hi, yes, I did do that, but it didn't help. I put it in my conf file for both. I really think it's something else because I can get other versions to work fine. I'm surprised though that I'm the only one with the problem??
|
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
November 16, 2014, 08:36:16 AM |
|
"not a capable masternode."
Isn't that the error message when you "break" the masternode by touching the 1000 DRK at the original address? Have you looked in coin control? Yes, it's all still in one chunk in the same address, but tomorrow I think I'll set up an entirely new server, new wallets, etc.... and maybe that'll work. I'm a bit tipsy now, but feeling better, LOL Besides though, I've never even had to have the local "on" before doing masternode debug on the remote server before. I always got to that point before even touching the local masternode. So it shouldn't have to know anything about the original masternode??? Oh heck, I'm going to try this all over again. I can't sleep with this undone!
|
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d
|
|
|
oblox
Legendary
Offline
Activity: 1442
Merit: 1018
|
|
November 16, 2014, 08:39:01 AM |
|
If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.
If you already have masternode wallets, dump the private keys for each one (dumpprivkey MASTERNODE_ADDRESS). Then on the wallet you want to have all the masternode in (make sure it is encrypted), import the private keys (importprivkey PRIVATE_KEY) for each masternode addressed dumped. Close the client. Create a masternode.conf file in the darkcoin data folder with the format below: ip address of remote masternode:9999 MASTERNODE_GEN_KEY ip address of remote masternode2:9999 MASTERNODE_GEN_KEY Then load the new wallet with all the masternode addresses in there, go to the debug command prompt and issue: masternode start-many PASSPHRASE Not sure it can get any more detailed then that. MASTERNODE_GEN_KEY it that the key from remote or local? do i still need to enter a key also in the darkcoin.conf? what do i have to put in the darkcoin.conf for that seup? Thanks! You still need to enter it in the remote darkcoin.conf. That masternode gen key is what you generate at the beginning with "masternode genkey". It's the same private key that would go in the darkcoin.conf file on both remote and local the old way. This masternode.conf file is your new local conf in addition to your existing darkcoin.conf with the masternode=1 setting. Please give an example of the CONF file ty Local darkcoin.conf: rpcuser=LONG-RANDOM-STRING-fisjfijsfisjfsdwesdfsfdsfsfsdfhis_you_should_change_this rpcpassword=LONGER-RANDOM-STRINGfisdfisfisjfijsfisjfsdwesdfsfdsfsfsdft_you_should_change_this rpcallowip=127.0.0.1 listen=0 server=1 daemon=1 logtimestamps=1 addnode=23.23.186.131 masternode=1
Remote darkcoin.conf: rpcuser=enter-new-LONG-RANDOM-STRING-fisjfijyou_should_change_this rpcpassword=enter-new-LONGER-RANDOM-STRING-fissjfijyou_should_change_this rpcallowip=127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 masternode=1 masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX addnode=23.23.186.131 Local masternode.conf: 10.10.10.1:9999 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Every masternode would have its own line in the masternode.conf file with the ip address, port, and masternode genkey.
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
November 16, 2014, 09:01:54 AM |
|
Aw heck, I set masternode=0 in config, started wallet, and sent myself (to new address in same wallet) 1000 coins, but it won't confirm! It's like in limbo! UGH! What a day!
|
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d
|
|
|
|
dihydrogenmonoxide
|
|
November 16, 2014, 09:44:02 AM |
|
drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night
|
"The best way to convince a fool that he is wrong is to let him have his own way." - Josh Billings
|
|
|
qwizzie
Legendary
Offline
Activity: 2548
Merit: 1245
|
|
November 16, 2014, 09:45:45 AM |
|
drk.mn portchecker/versionchecker does not work properly at the moment. My nodes are all on v0.10.16.11, yet still reported as v0.10.15.21 - but they were all paid during the night but which site do you monitor then ? https://drk.mn/masternodes.html ?? or https://drk.mn/masternodes-v15.html ?
|
Learn from the past, set detailed and vivid goals for the future and live in the only moment of time over which you have any control : now
|
|
|
dihydrogenmonoxide
|
|
November 16, 2014, 09:48:35 AM |
|
https://drk.mn/masternodes.html - it's showing the v16 network, ignore the reported version for the moment.
|
"The best way to convince a fool that he is wrong is to let him have his own way." - Josh Billings
|
|
|
qwizzie
Legendary
Offline
Activity: 2548
Merit: 1245
|
|
November 16, 2014, 09:49:37 AM |
|
okay thanks.. here is hoping my MN stays on that site... pfff
|
Learn from the past, set detailed and vivid goals for the future and live in the only moment of time over which you have any control : now
|
|
|
|
dihydrogenmonoxide
|
|
November 16, 2014, 09:50:32 AM |
|
okay thanks.. here is hoping my MN stays on that site... pfff It will Best regards, flare
|
"The best way to convince a fool that he is wrong is to let him have his own way." - Josh Billings
|
|
|
|