Step #1 I started over and attempted step #1: ssh -i "C:\SSH_KEY_FOR_EC2_SP.pem" [email protected] I receive the following result: Warning: Identity file C:\SSH_KEY_FOR_EC2_SP.pem not accessible: No such file or directory. The authenticity of host 'some_prefix.us-west-2.compute.amazonaws.com (xxx.xx.xx.xxx)' can't be established. ECDSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx. Questions: Am I suppose to provide the full path to my local directory file?
Hey.... after copying the encrypted wallet.dat to masternode server, and restarting the server... how do i unlock the wallet, if wallet includes characters like ! # % & ... which give an error in bash (when using it in line: darkcoind masternode start passwordwithcharacters!"#$%&/()= )? thanks wg
Step #1 My private key is saved on my Windows machine. I used windows to configure AWS and downloaded the private key (.pem) file onto my Windows box. Question: Is step #1 really necessary? Running the Putty tool makes me think I am already authenticated when launching the cmd tool: Using username "ubuntu". Authenticating with public key "imported-openssh-key" Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.13.0-24-generic x86_64) I also attempted the following: ssh -i SSH_KEY_FOR_EC2_SP.pem [email protected] -config "..\share\openssl.cnf" Results: Warning: Identity file SSH_KEY_FOR_EC2_SP.pem not accessible: No such file or directory. Unknown cipher type 'onfig' I'm not sure what I'm doing wrong. I thought the command requires the private key file path that was downloaded onto my Windows machine.
Step #6 I am not sure how to enter the commands onto the console: Question: Do I copy and paste this onto the console's command editor as a whole? Or do I enter the commands one line at a time? I tried both and I am unsuccessful.
Wait wait!! as long as you fail to log in with SSH dont continue with the other steps! Tell me please, what is the exact name and location of the .pem file in your linux file system!?
Step #1 File Name: SSH_KEY_FOR_EC2_SP.pem Location: I do not know. I would assume that there's a default location that AWS EC2 puts the file into when the pem file gets downloaded instance configuration time. I am not familiar with how Ubuntu works. As a result, I am unsure of how to retrieve the location of the pem file. Update: If I am already authenticated then perhaps the Putty Configuration tool that I'm running on Windows does this for me on its Connection | SSH | Auth | Authentication Parameters field.
Use editor. nano, vi.... first cat /etc/default/sysstat cat /etc/cron.d/sysstat You will know waht to do.
Step #6 Question: Is the text in blue font correct when modifying the file? GNU nano 2.2.6 File: /etc/cron.d/sysstat Modified # The first element of the path is a directory where the debian-sa1 # script is located PATH=/usr/lib/sysstat:/usr/sbin:/usr/sbin:/usr/bin:/sbin:/bin # Activity reports every 10 minutes everyday 5-55/10 * * * * ---> */1 * * * * root command -v debian-sa1 > /dev/null && debi$ # Additional run at 23:59 to rotate the statistics file 59 23 * * * root command -v debian-sa1 > /dev/null && debian-sa1 60 2
Step #6 Issue: I receive a permission denied error when running this: -bash: /etc/rc.local: Permission denied I tried executing this at the root directory and I have also tried using sudo in front of the command. Any suggestions? Update: I apparently misread the instructions. I just need to edit the file and add the content in there instead of executing it on the command line.
Step #6 Code: cat > /etc/iptables << EOF #----- *filter :INPUT ACCEPT [1038:145425] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [434:87191] -A INPUT -i eth0 -p tcp -m tcp --dport 9998 -j REJECT --reject-with tcp-reset -A INPUT -i eth0 -p tcp -m tcp --dport 9999 --tcp-flags FIN,SYN,RST,ACK SYN -m connlimit --connlimit-above 8 --connlimit-mask 24 --connlimit-saddr -j REJECT --reject-with tcp-reset -A INPUT -i eth0 -p tcp -m tcp --dport 9999 --tcp-flags FIN,SYN,RST,ACK SYN -m connlimit --connlimit-above 2 --connlimit-mask 32 --connlimit-saddr -j REJECT --reject-with tcp-reset -A INPUT -i eth0 -p tcp -m conntrack --ctstate NEW -m tcp --dport 9999 -j ACCEPT -A INPUT -i eth0 -p tcp -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9999 -m conntrack --ctstate NEW -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9999 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9999 -j ACCEPT -A OUTPUT -o eth0 -j ACCEPT COMMIT #----- EOF Assumption: I do not see the file: "/etc/iptables". I assume I create this file with the provided content...
Step #11 My log file is different: Code: [email protected]:~$ tail -f ~/.darkcoin/debug.log 2014-06-06 18:32:15 dsee - Got NEW masternode entry 54.209.21.168:9999 2014-06-06 18:32:15 dsee - Rejected masternode entry 2014-06-06 18:32:15 dsee - Got NEW masternode entry 54.209.21.168:9999 2014-06-06 18:32:15 dsee - Rejected masternode entry 2014-06-06 18:32:15 dsee - Got NEW masternode entry 54.209.21.168:9999 2014-06-06 18:32:15 dsee - Rejected masternode entry 2014-06-06 18:32:15 dsee - Got NEW masternode entry 54.86.252.4:9999 2014-06-06 18:32:15 dsee - Rejected masternode entry 2014-06-06 18:32:16 dsee - Got NEW masternode entry 54.209.21.168:9999 2014-06-06 18:32:16 dsee - Rejected masternode entry Is this okay?
Step #12 Question: I'm confused. That address that is returned from "getaccountaddress 0" is not an address that is linked to my wallet. In addition, I have observed that my wallet generates new addresses that cannot be edited. This means that I cannot withdraw money in the future from that address because that address was not generated from my wallet. As a result, I am confused because I do not want to send 1000drk to an address that I do not own. I'm new to Linux and Bitcoin. So I apologize for my ignorance. Can someone please explain this to me?
Well, address returned from "getaccountaddress 0" is actually "linked" to your wallet. Try "dumpprivkey <address>" to make sure. If this command gives you private key then you can do whatever you want with coins sent to that address. Try dumpprivkey on any other DRK address you can find (try mine for example XsV4GHVKGTjQFvwB7c6mYsGV3Mxf7iser6 ) to see the difference.
Step #12 Thank you for explaining that to me. So to be clear, that address is not "linked" to my wallet yet unless your definition of "linked" is a "send-address" that my wallet keeps a record of. I say this because I am unaware of any method to take the address from "getaccountaddress 0" and "link" that address to my wallet's "receive-address" list that maintains a balance for each address within that list. In other words, how do I add that external address to my wallet? Update: My question has been resolved. The following link provides instructions on how-to add the master node address to your wallet (Windows): http://www.reddit.com/r/DRKCoin/comments/27h3v0/paper_wallet_extraction/
No, the arrow means 'from this to that'. You need to substitute '5-55/10 * * * *' for '*/1 * * * *' (without commas)
Hi I have been trying to setup my masternode with ubuntu 14.4. I am no expert in ubuntu but i am learning fast. I have a couple of issues 1. When doing step 6. (iptables) I have edited both /etc/rc.local and making /etc/iptables but when i reboot i cant seem to log back on so I haven’t rebooted this time and continued. 2. when doing step 9 install git clone https://github.com/darkcoinproject/darkcoin.git is this needed for rc3 only reason I ask is because when i do darkcoind getinfo I get "version" : 90411, "protocolversion" : 70015, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 0, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : true, "keypoololdest" : 1402250798, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } Which I think is on the wrong chain. Please can someone point me in the right direction... Many Thanks
/etc/rc.local is not new one. you can add Code: /sbin/iptables-restore < /etc/iptables to /etc/rc.local between # and 'exit 0' permission of /etc/rc.local is 755 Two file should look like this /etc/rc.local Code: #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. /sbin/iptables-restore < /etc/iptables exit 0 /etc/iptables Code: #----- *filter :INPUT ACCEPT [1038:145425] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [434:87191] -A INPUT -i eth0 -p tcp -m tcp --dport 9998 -j REJECT --reject-with tcp-reset -A INPUT -i eth0 -p tcp -m tcp --dport 9999 --tcp-flags FIN,SYN,RST,ACK SYN -m connlimit --connlimit-above 8 --connlimit-mask 24 --connlimit-saddr -j REJECT --reject-with tcp-reset -A INPUT -i eth0 -p tcp -m tcp --dport 9999 --tcp-flags FIN,SYN,RST,ACK SYN -m connlimit --connlimit-above 2 --connlimit-mask 32 --connlimit-saddr -j REJECT --reject-with tcp-reset -A INPUT -i eth0 -p tcp -m conntrack --ctstate NEW -m tcp --dport 9999 -j ACCEPT -A INPUT -i eth0 -p tcp -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9999 -m conntrack --ctstate NEW -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9999 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9999 -j ACCEPT -A OUTPUT -o eth0 -j ACCEPT COMMIT #----- Iptables in ec2 stop access to port 9998 from outside and limit number of concurent access to port 9999, and the other ports are opened. All access control is performed by ec2 security group. Don't forget to change ec2 security group. step 4 in guide 1/3 https://www.darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-1-3.240/
Thanks, Top Man Got it all working on testnet now thanks very much Is it yet possible to have wallet.dat offline on mainnet thanks again
* https://bitcointalk.org/index.php?topic=421615.msg7330382#msg7330382 comments from TanteStefana Code: [quote author=TanteStefana2 link=topic=421615.msg7330382#msg7330382 date=1402861266] It's great we have people pooling for masternodes. I hope some day we can do it with a system so trust isn't' involved, but it's great that trusted members are willing to do this for everyone! Mr. President, I'm having trouble getting on darkcoindtalk, so I'm going to quickly put my comments down here in case they're helpful. This is for chaeplin's Masternode setup guide : How dumbed down do you want to make this? LOL. If you want to make it easier for a newb like I was/am back 5 months ago, there are a few things that would help: 1. Explain that EOF means End of File, LOL, it messes things up if you include it in your file) 2. When rebooting the instance after setting the iptables rules, sometimes you can't log back into your Amazon instance. Because of that, I didn't upgrade the distribution for a long time. Then I discovered that if you reboot on the EC2 instance management page on the website, you'll be able to log back in. 3. at step 9, until the source for the masternodes is available, you need to just download the compiled version, so maybe that should be noted. Just cd /usr/bin and do sudo wget http://www.darkcoin.io/downloads/rc/darkcoind then sudo chmod +x darkcoind and finally go back to home directory cd /home/ubuntu. 4. On one machine I need to use darkcoind -daemon or else I don't get my prompt back, might be nice to list that trick. 5. we now need other info for darkcoin.conf files IF you want to run your masternode with the 1000 coins inside it: masternodeprivkey=to get this, set masternode=0, run darkcoind and run command: darkcoind getmasternodekey masternode=1 or 0, depending on if it's on or off addnode=23.23.186.131:9999 Got to go, have a great day everyone! Will be back later :D [/quote] * EOF == End Of File Code: cat >> /etc/fstab << EOF /swapfile swap swap defaults 0 0 EOF This code add lines between EOF and EOF to file /etc/fstab.
Hi, I know this is late, but in case anyone else is confused by this, not all addresses show up in the QT "receive" tab. if you do getaccountaddress 0 in darkcoind on the wallet you want to receive funds in, it will give you an address that belongs to your wallet. HOWEVER, you can always send a small amount, like .1 drk or less even, to see if it goes through ok. Once you see it went through, I'm sure you'll feel more confident to send 1000 coins. I'm not sure if you still have to unlock your wallet to start the masternode, but it used to be that you did. So I would start it (#22) like so: walletpassphrase "walletpassphrase" 60 (use quotes to designate the whole thing and the 60 designates the number of seconds the wallet is left unlocked) masternode start mylongpassphrase
Difference between commands. getaccountaddress : Code: getaccountaddress will return the same address until coins are received on that address; once coins have been received, it will generate and return a new address. listaddressgroupings : Code: Returns all addresses in the wallet and info used for coincontrol getaddressesbyaccount : Code: Use the getaddressesbyaccount method to list all addresses associated with an account. example. Code: [email protected]:~> darkcoind getaddressesbyaccount 0 [ "mgosBEJMvd27HiHcm1LLJqTekMAkaxHAvZ" ] Code: [email protected]:~> darkcoind listaddressgroupings [ [ [ "mgosBEJMvd27HiHcm1LLJqTekMAkaxHAvZ", 2032.89400000, "0" ] ] ] This one will make new address for account 0. Code: [email protected]:~> darkcoind getaccountaddress 0 muj9oHwCtoWLcrALSfV7yQS2yh1KLpbXo6 Code: [email protected]:~> darkcoind listaddressgroupings [ [ [ "mgosBEJMvd27HiHcm1LLJqTekMAkaxHAvZ", 2032.89400000, "0" ] ] ] Code: [email protected]:~> darkcoind validateaddress muj9oHwCtoWLcrALSfV7yQS2yh1KLpbXo6 { "isvalid" : true, "address" : "muj9oHwCtoWLcrALSfV7yQS2yh1KLpbXo6", "ismine" : true, "isscript" : false, "pubkey" : "02001c88f3399a1150c47f2e383762997da1f3dde2b94ecfeffac3ac31751853c7", "iscompressed" : true, "account" : "0" } Code: [email protected]:~> darkcoind getaddressesbyaccount 0 [ "muj9oHwCtoWLcrALSfV7yQS2yh1KLpbXo6", "mgosBEJMvd27HiHcm1LLJqTekMAkaxHAvZ" ]
How do I know that my RC2 to RC3 migration was successful? Log: Code: [email protected]:~/.darkcoin$ tail -f ~/.darkcoin/debug.log 2014-06-16 13:46:30 AcceptToMemoryPool: 23.23.186.131:9999 /Satoshi:0.10.9.13/ : accepted e8ac4c700f66c407adb3002da68f0ba46c80c007d991bf355286c2891f143b98 (pool sz 4) 2014-06-16 13:47:00 received block 0000000000103560b9592d97c87ebdebcfc204fb3ada8 ad455cac9190cbd4509 2014-06-16 13:47:00 Committing 15 changed transactions to coin database... 2014-06-16 13:47:00 SetBestChain: new best=0000000000103560b9592d97c87ebdebcfc20 4fb3ada8ad455cac9190cbd4509 height=86545 log2_work=58.37618 tx=382605 date=2 014-06-16 13:46:37 progress=0.999999 2014-06-16 13:47:00 ProcessBlock: ACCEPTED 2014-06-16 13:47:31 received block 0000000000090c1cf2ce93de60898791c4e34a835112a 72d4123e6c2a430982e 2014-06-16 13:47:32 Committing 1 changed transactions to coin database... 2014-06-16 13:47:32 SetBestChain: new best=0000000000090c1cf2ce93de60898791c4e34 a835112a72d4123e6c2a430982e height=86546 log2_work=58.376238 tx=382606 date= 2014-06-16 13:47:01 progress=0.999999 2014-06-16 13:47:32 ProcessBlock: ACCEPTED 2014-06-16 13:48:00 AcceptToMemoryPool: 23.23.186.131:9999 /Satoshi:0.10.9.13/ : accepted 6206726450247049ee415357d680a34f30fb8386081b9b3fec8f4752283a509d (pool sz 1) 2014-06-16 13:48:17 received block 00000000000e22e6977dc599615a57d7bc1f8b37463fdcbed9f73160f3930f8e 2014-06-16 13:48:17 Committing 3 changed transactions to coin database... 2014-06-16 13:48:17 SetBestChain: new best=00000000000e22e6977dc599615a57d7bc1f8b37463fdcbed9f73160f3930f8e height=86547 log2_work=58.376298 tx=382607 date=2014-06-16 13:47:31 progress=0.999999 2014-06-16 13:48:17 ProcessBlock: ACCEPTED 2014-06-16 13:48:21 AcceptToMemoryPool: 23.23.186.131:9999 /Satoshi:0.10.9.13/ : accepted 823c2729d41b1f3eaade6e6853199e58a0159b45035e275c4c215f963bbb910f (poolsz 2) 2014-06-16 13:48:22 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:48:33 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:49:12 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:49:14 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:49:22 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:49:26 accepted connection 49.73.35.87:61317 2014-06-16 13:49:26 send version message: version 70015, blocks=86547, us=54.186.38.217:9999, them=49.73.35.87:61317, peer=49.73.35.87:61317 2014-06-16 13:49:26 Added time data, samples 3, offset -4 (+0 minutes) 2014-06-16 13:49:26 Added 49.73.35.87:9999 from 49.73.35.87: 406 tried, 7138 new 2014-06-16 13:49:26 Moving 49.73.35.87:9999 to tried 2014-06-16 13:49:26 receive version message: /Satoshi:0.9.10.1/: version 70018, blocks=74828, us=54.186.38.217:9999, them=49.73.35.87:9999, peer=49.73.35.87:61317 2014-06-16 13:49:34 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:49:51 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:08 AcceptToMemoryPool: 23.23.186.131:9999 /Satoshi:0.10.9.13/ : accepted 56064791890f09a9e89d0c0b004f57f9e99f62f848a049b0aae7c6f6ba1dd1e5 (poolsz 3) 2014-06-16 13:50:08 AcceptToMemoryPool: 23.23.186.131:9999 /Satoshi:0.10.9.13/ : accepted 08896ef56f03b7001f4735855679db7412c3c044c4f9ce2cc4a36fe8d61bc1c0 (poolsz 4) 2014-06-16 13:50:45 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:46 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:47 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:47 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:47 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:47 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:48 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:49 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:51 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:52 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:52 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:52 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:52 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:52 ProcessMessage(dseep, 116 bytes) FAILED 2014-06-16 13:50:53 ProcessMessage(dseep, 116 bytes) FAILED
Yes! Aside from Masternodes finally getting paid, the biggest thing for RC3 is that we can have offline masternodes via remote/local setup, keeping our coins safe as possible! Probably the best and easiest way to see if you were successful is to see if you show up on the masternode list: http://tdrk.poolhash.org/blocks/masterlist.txt For Testnet and http://drk.poolhash.org/darksend.html for mainnet
Anyone got any clue as to why my debug.log's timestamp is off (backwards) by 2hrs? systemtime is correct.. :what:
Hi thanks so much for the guide! I got everything working that involve just the EC2 server My problem comes in with the local wallet. I decided to install Ubuntu 14.04 on VM on my PC, but I'm stuck at step 12/13. I tried doing step 2 to 9 on local VM but got stuck on the "time make -f makefile.unix" part. Not sure what I did wrong or result, but then tried downloading darkcoind from darkcoin.io but that would run, probably because I have 32 bit linux, on VirtualBox. Is it possible that you can explain steps 12/13 and how to correctly download darkcoind? Sorry, just a bit new to Linux and want to do it properly.
Current RC binary supports 64bit only. Code: file darkcoin* darkcoin-qt: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, not stripped darkcoind: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, not stripped
OK right, should have known. So am I right in thinking that I must follow steps 2 - 10 to install darkcoin onto local machine (if I can make a 64 bit VM)?
At home skip 4 add swap / it's for ec2 t1 micro. At linux istallation, allocate swap. at 6, skip sysstat at 6, use iptables rule in home section / If machine is VM on home computer, and network setting is NAT, you can skip this two. Use NAT for VM, do not brigde.
Hi, I have trouble with MN and cold wallet: My MN appear just for a couple of minutes and disappear on https://www.darkcoin.io/masternodes.txt and http://drk.poolhash.org/darksend.html (Everything's fine with "hot" wallet) I'm running the last version and both are sync with network: $darkcoind --help DarkCoin version v0.10.10.1-beta darkcoin.conf from MN: rpcuser=user rpcpassword=password rpcallowip=127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=200 externalip=my_external_ip masternode=1 addnode=23.23.186.131 masternodeprivkey=my_private_key_MN_cold darkcoin.conf from cold wallet: rpcuser=user rpcpassword=password rpcallowip=127.0.0.1 listen=0 server=1 daemon=1 logtimestamps=1 maxconnections=200 addnode=23.23.186.131 masternodeaddr=external_ip_of_MN:9999 masternodeprivkey=my_private_key_MN_cold masternode=1 First I launch the MN with ./darkcoind And I launch the cold wallet with ./darkcoind I wait for sync and I launch ./darkcoind masternode start "wallet_key" The debug.log file indicate: CDarkSendPool::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(xxxxxxxxxxxxxxxxxxxx, 0), scriptSig=) CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon. My MN is directly connected on internet, and my cold wallet is connected with NAT on a private network. When I relaunch the cold wallet, my MN appear again... Thanks to help me, only 3 days before a big step ;-)
