Quote from: HashStatz on September 08, 2015, 09:29:41 PM

Quote from: murderouskirk on September 08, 2015, 08:27:49 PM

Quote from: HashStatz on September 08, 2015, 03:30:36 PM

Quote from: murderouskirk on September 07, 2015, 10:45:51 PM

Quote from: HashStatz on September 07, 2015, 09:03:45 PM

Quote from: murderouskirk on September 07, 2015, 07:18:51 PM

Quote from: HashStatz on September 07, 2015, 12:33:22 AM

Quote from: murderouskirk on September 06, 2015, 07:02:38 PM

Here's a peers.dat from 9/6/15 2:57PM EST with 14 connections. Just do the initial startup to get your base files, close the wallet (backup your wallet.dat if neccessary), replace peers.dat, and start the wallet back up. You should get more connections faster. If you wait too long from the time of upload it may not work as well but I can always get you a fresh copy.

https://mega.nz/#!fZBWkI7T!0FbVukLFRcxl6jc3ieiWvN0A98VSIK2cgfxLOV8brLY

I have a fresh wallet compiled and ready to fire up, ~~murderouskirk I should be online for the next 5 hours if your available to post an updated copy of your peers.dat i will try again~~.

murderouskirk i should be popping online every hour or so all day so if your available to post an updated copy of your peers.dat i will try again (not really sure if thats the issue though as i have lots of connections).

Thanks for the help.

Sorry HashStatz I was away from my pc. Did you try it with the uploaded peers.dat?

On a similar note, if anyone wants to spin up Swing on a serer and share the IP we can put it as an addnode in the example config for better network connections.

Ya i tryed your peer file, but still got stuck at block 3004 with 36 connections. I am running this on a VPS and would be happy to setup as a node if i can get everything working correctly.

Try setting debug=1 in your conf file. You might be able to get some info out of it in the file it makes.

So i created a debug file like you suggested and after combing through it i found what seems to me where the error occurs starting at block 3005 and repeating every block after. Hopfuly this help give you an idea as to what my problem maybe caused by.

Code:

received: block (256 bytes)
received block 0000000000001a29c94c
ComputeNextStakeModifier: prev modifier=0xd05348b890b66422 time=2015-09-03 12:11:50 UTC
ERROR: ConnectBlock() : coinbase reward exceeded (actual=1200000 vs calculated=1199999)
InvalidChainFound: invalid block=0000000000001a29c94c height=3005 trust=14496107994403525608 blocktrust=1995525199418564 date=09/03/15 12:15:22
InvalidChainFound: current best=bf08d8b87f952089955b height=3004 trust=14494112469204107044 blocktrust=6179704 date=09/03/15 12:14:31
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

I've been trying to replicate this error without success. I tried downloading the chain both with and without a config file multiple times and was able to with my only connection being the seed node. I'm still looking into it some but:

What does your Swing.conf file look like?

Did you compile your own wallet?

When you try to download the chain, be sure you're doing the following:

1: Close the swing wallet

2: Go to C:\Users\Username\AppData\Roaming\Swing

3: Backup your wallet.dat if there are stored coins on your pc

4: Delete all the files in the swing folder

5: Start the swing wallet and let it get a connection & download.

If it fails, you might want to consider trying the wallet on a different PC or vm. You said you were running on a vm yes? It's possible that's causing some sort of conflict but that's just me going out on a limb to take additional guesses. You can also try downloading with and without your config file.

Yes i complied my own wallet, and am running the Swingd from the command line. All this is running on a Ubuntu 14.04 x86 OpenVZ container VPS.

I am going to trying installing this wallet on a different and fresh OpenVZ container on a VPS i am going to be retiring in a month or so. I will let you know how that goes later tonight.

Thanks for you help.

Ok cool. Please note that in a linux build you still have the same swing folder that needs deletion to redownload the chain.

(I'm guessing you know this since you enabled debug but just touching all bases I can think of)

You can probably find it at:

root/.Swing

or

cd ~
cd .Swing

It should be found in the same directory as the Swing folder and can be seen with 'ls -al'.