 Show Posts
|
|
Pages: « 1 [2] 3 »
|
I am on 2.5.0.1, and I can't get past "25 hours behind" when trying to load my wallet....
How many peers do you have when it is sitting at 25 hours behind? When I hover over the connections icon at the bottom right of the wallet, it says that I have 25 active connections... Is this what you were asking for? Yes. Jump on Discord and we can work through the issue online. Sorry! I was asleep when you sent that last night. I'm actually getting ready to leave for work now. I'll put a message up on there when I get back tonight and hopefully we can take a look at it. This is exactly what I was talking about the other day. I HATE updating wallets when I have masternodes online. I have never had an update go successfully. |
|
|
|
I am on 2.5.0.1, and I can't get past "25 hours behind" when trying to load my wallet....
How many peers do you have when it is sitting at 25 hours behind? When I hover over the connections icon at the bottom right of the wallet, it says that I have 25 active connections... Is this what you were asking for? |
|
|
|
|
In looking at the blockhain explorer, it appears as though the last MN reward I got was about 25 hours ago as well.....odd....
|
|
|
|
I am on 2.5.0.1, and I can't get past "25 hours behind" when trying to load my wallet....
How many peers do you have when it is sitting at 25 hours behind? I deleted all of the files instructed above (blocks, chainstate, database) about an hour ago, and reloaded the wallet. It still gets stuck at 25 hours behind |
|
|
|
I am on 2.5.0.1, and I can't get past "25 hours behind" when trying to load my wallet....
How many peers do you have when it is sitting at 25 hours behind? How do I check? |
|
|
|
VPS upgrade - Anyone using the script can use the following commands to upgrade your VPS instance, these are the steps I took: cd vps && git pull && rm -rf ./code/lasvegascoin && ./install.sh -p lasvegascoin -n 4 -u I then restarted the daemon a couple of times but the blocks were stuck at 41179 so I did the following to resync the chain, to be sure: rm -rf /var/lib/masternodes/lasvegascoin1/blocks /var/lib/masternodes/lasvegascoin1/chainstate
/usr/local/bin/lasvegascoin-cli -conf=/etc/masternodes/lasvegascoin_n1.conf stop
This worked, then I waited for the blocks value to go up past 41280. The version reported should be 2050001. /usr/local/bin/lasvegascoin-cli -conf=/etc/masternodes/lasvegascoin_n1.conf getinfo
Then I restarted the node remotely from my main wallet. Worked like a charm! Thank you!! |
|
|
|
|
I am on 2.5.0.1, and I can't get past "25 hours behind" when trying to load my wallet....
|
|
|
|
dam can't start my masternode because i was on wrong chain? i lost 9vgs gonna need to ways 1 more week to have 1000
No worries.... With the new wallet, you will ROI in 2 weeks!!! Masternode cost : only $830!! (1000 VGS @ $0.83). Weekly income $466!!Currently only 44 nodes online!!https://chainz.cryptoid.info/vgs/  it s hard to believe this , that's look fake 2 weeks roi no possible lol you making around 1000 vgs in 2 weeks with a masternode ??  it s more than 70 vgs a day with 1000coins in masternode masternod gets 1.5 and wallet 0.5 i m close to 1000 vgs and my wallet don't make 23 vgs a day it s more like 2-4 lol I think you're correct. I believe that the skewed numbers are coming from the fact that Masternodes.online is making these calculations based on their data that there are only 10 active MNs. We'll see... |
|
|
|
|
OK, guys...I am starting to get worried. I've been trying to keep up to date with all of this, but to be honest, I'm lost.
I have a masternode up and running, and am getting payouts.
My QT wallet is the latest version (v2.0.0.3-0978135-dirty (64-bit) which was posted on here either today or yesterday, I can't remember.
I have not updated the wallet on my VPS, because I am not sure exactly what to do to get it updated without risking losing my current payouts.
On my wallet, I am showing that there are 33 active MNs, but on Masternodes.online, it is showing that there are only 10 active.
Am I safe, or am I on the wrong chain, or what?
|
|
|
|
|
What is the current frequency for a MN payout? (ballpark...)
I have always gotten a few per day. Today, I got 2 payouts around 7am, but I haven't gotten one since.
When I look at the "masternodes" tab in my wallet, my MN currently shows an active time of 00:00. Nothing has changed (as far as I know) since 7am. Any ideas what may have happened?
I am not very well versed in Linux. I am wondering if maybe a reboot of the wallet on the VPS may help, but I don't know how to go about it.
|
|
|
|
|
What are the current masternode rewards, and how often do you receive? Can anyone confirm this?
|
|
|
|
<snip> when i run this command, I get the following error: ___________________________ Validating network rules No IPv6 support on the VPS but IPv6 is the setup default. Please switch to ipv4 with flag "-n 4" if you want to continue. See the following link for instructions how to add multiple ipv4 addresses on vultr: https://www.vultr.com/docs/add-secondary-ipv4-address____________________________ I am not versed in linux, so I have no idea how to go about correcting this. Any advice? Are you using IPV6 addresses? If you are, you haven't enabled support on your VPS. In Vultr this is a checkbox on the server setup page. My nodes are IPV6 enabled even though configured for IPV4. If yours are not enabled for IPV6, it might be that we need to be more specific with the update command, like: IPV4 Nodes cd vps && git pull && ./install.sh -p lasvegascoin -n 4 -u IPV6 Nodes cd vps && git pull && ./install.sh -p lasvegascoin -u Let me know if this helps. I added "-n 4" to the command shortly after sending that last message. It went through properly. a couple minutes ago, I received a MN payout, and it was still for only .5 VGS. I would like to know if everyone else is seeing .5 payouts. I'm wondering if I ought to destroy this server and start from scratch, but I don't want to waste the time doing that if this issue is across the board, you know...? |
|
|
|
Ok, I have updated the node install script to build from master of the new repo. I also made the update command remove the existing code because it was re-using old compilation files. Here is the command you can use to update your nodes (assumes logged in as root on your VPS): cd vps && git pull && ./install.sh -p lasvegascoin -u
/usr/local/bin/lasvegascoin-cli -conf=/etc/masternodes/lasvegascoin_n1.conf stop
This new version has no corresponding release in github yet, but in future if you want to update to a specific tagged version (for example v3.0.5.1) the command would be: cd vps && git pull && ./install.sh -p lasvegascoin -r "tags/v3.0.5.1" -u
when i run this command, I get the following error: ___________________________ Validating network rules No IPv6 support on the VPS but IPv6 is the setup default. Please switch to ipv4 with flag "-n 4" if you want to continue. See the following link for instructions how to add multiple ipv4 addresses on vultr: https://www.vultr.com/docs/add-secondary-ipv4-address____________________________ I am not versed in linux, so I have no idea how to go about correcting this. Any advice? |
|
|
|
If you want my advice, I will give it. Take it for what it's worth. If you need the money, sell what you have at current prices, cut the loss, and go on about your life. If the market continues to drop, then you have "made a profit". If the market rallies, wait for confirmation of an uptrend, then buy back in below $5-6 each, then you have still profited. Quite frankly, I think the market has plenty of room to drop before we see another run up. I hope I'm wrong, but I doubt I am. If you don't need the money, then just stop looking at it so much. Whenever Bitcoin rallies, altcoins will rally with it. It's not a question of if, but of when. As you wait it out, you will be receiving coins, assuming you have a masternode set up. If you don't have one set up, what are you waiting for? Theyre cheap!! This is all very cut and paste advice for anyone who got into this space fairly recently, and could probably be given to millions of others just like you. Here is something that may help you: Go back to coin exchange, and look at your trade history. See what the price was for VGS when you bought it. You will see that they don't show you how many dollars you paid for each coin. They show you the BTC value. Stop looking at your portfolio is USD value. Try to get you BTC holdings up, then when the market rally (as they always do), you will see the dollar signs that you are currently looking for. Sorry for being long winded. |
|
|
|
Again guys. I admit, I messed this up, and should have moved the fork block for 45,000. Lesson learned. At the end of the day , everything is working. Please understand the reason for the change. .5 VGS to the staker, and .5 vgs to the masternode made no sense whatsoever. I wanted to increase buying pressure through masternodes. Anyway, I shall now move forward with more promotions, the wallet is the way I want it. I will also cleanup the github.
My apologies to everyone.
Vegas
This is where I would like a little clarification if possible. Yous stated that everything is working, but I am still getting .5 rewards. Can anyone confirm 2 VGS rewards that fully confirm without turning to orphans...? After following the wallet repair; recover transactions advice, now I am ONLY showing .5 VGS payouts. All evidence of 2 VGS payouts have vanished (ie - no more orphans) I am not wanting to be a pain in the butt, but I would really like to get this thing running correctly ASAP. The idea of each payout I received today being worth 4 times as much is almost enough to salivate over! |
|
|
|
If you want to write a script to help them setup their ubuntu VPS 200 Las Vegas coins for that.
...Ahem. https://github.com/goosewobbler/vpsSo I've been helping some people out in Discord DMs with this, might as well post proper instructions here. The following sets up one node called lasvegas_node1, and assumes you know how to send yourself funds with a wallet, and can use the linux editor vim. Instructions (assumes one node called lasvegas_node1)<on master wallet><Send 1000 VGS to yourself - must be exact><Tools menu, debug console>Enter the following commands: The result of this is your MN private key. You need it later. The result of this is your MN transaction id and index in the format "{tx_id}": "{index}". You need those later. <Tools menu, open masternode configuration file>Add the following details in this file in the following format: lasvegas_node1 {VPS IP address}:60702 {MN private key} {MN transaction id} {MN transaction index}Save the file and close the wallet. Open the wallet again. <on VPS>Run the following commands to compile and install the VPS wallet: git clone https://github.com/goosewobbler/vps.git && cd vps && ./install.sh -p lasvegascoin -n 4 -c 1
Now edit the VPS wallet config file: vim /etc/masternodes/lasvegascoin_n1.conf Insert your private key and the IP address of the VPS in the appropriate places and save the file. Now activate the node locally: /usr/local/bin/activate_masternodes_lasvegascoin You will need to wait for the VPS wallet blockchain to fully sync before you can start the node remotely. Keep running this command, eventually the value of 'blocks' will stabilise: /usr/local/bin/lasvegascoin-cli -conf=/etc/masternodes/lasvegascoin_n1.conf getinfo Can someone confirm this , so I can pay the bounty? The value of 'blocks' will increase until it reaches the 'up to block' value on the block explorer: https://chainz.cryptoid.info/vgs/#When the VPS wallet is fully synced, you can start the node remotely: <on master wallet><Masternodes => My Masternodes => Start MISSING>You can verify the status of the VPS wallet and masternode with the following: <on VPS>/usr/local/bin/lasvegascoin-cli -conf=/etc/masternodes/lasvegascoin_n1.conf masternode status
- This has been tested with Vultr Ubuntu 16.04 instance ($5/month). The $2.50 instances should be fine for a single node but they are always sold out in my region.
- Don't use IPV6 addresses, I have yet to see the script work with those for any coin.
- The script supports more than one node per VPS instance but I prefer to keep mine separate so haven't tested that.
- This is not my script, but I did the LasVegasCoin integration amongst others, this should be merged upstream when Florian gets to my PR, it's been sat there a while with the others. Seems he's busy messing around with Achilles Coin
- PR for the geeks/interested:
https://github.com/masternodes/vps/pull/31
Sign up for Vultr here: https://www.vultr.com/?ref=7282546VGS address: VMATmN4BZRSTNES5dpzz34pC7EFJLnWh1F This is what I used to set up my remote MN. I am thinking that maybe this script installed an older wallet on my VPS, and this is why I'm getting orphans. Does this sound right? |
|
|
|
|
I downloaded the new wallet from the link provided.
When I to to "help", and "about VGS core", it is still showing an older wallet version.
Is this normal?
|
|
|
|
|
I'm having an issue that I'm hoping one of you can assist me with...
I have had a MN running for quite a while now with absolutely no issues whatsoever. Last night, I decided to upgrade my wallet to 2.0.0.3
This is when the trouble began.
My MN continuously goes back to a "missing" status. I made no changes to any of the files. When I "start alias", it will show enabled, with a 00m:00s status. Whenever I return my computer, it will be in a "missing" status again. It obviously stays on for a little while, because each time I've restarted it, I get one MN reward...
Does anyone have any advice as to what I could check to diagnose what is causing this, or what my next step should be...? I'm at a loss...
|
|
|
|
Is UFO dying?
Everything is dying... Not to worry, they'll all come back to life soon enough! |
|
|
|
How would one go about setting up a solo miner for GOA...? I currently solo mine FTC, but I would like to get up enough for a GOA masternode as soon as possible.
Guide for solo mining in the OP. I don't see it anywhere....maybe im missing something.....? |
|
|
|
|
