i wasn't seeing the results of the 2 dice games i played.  seemed like i was possibly forked or something.

i removed all files from .lottoshares on my debian VM, except the wallet.dat, and tried to re-download the blockchain.

now i can't connect to any peers. 

i've tried completely reinstalling the LTS wallet, and still no connections.  i've re-installed from source on github, as well as the pre-made .deb package.  no luck.

any ideas?   

i'd make a conf file with addnodes, if there were some listed somewhere.   

**edit**  still not able to connect.  when looking at the debug window in the QT, i can see the Network Connections changing from 0 to 1 and back, really quick.  just a flash of the 1, then back to 0.

here's what i get in the debug log.  i did edit out my external facing IP address, to myIP.  really don't want it advertised across the internet anymore than it already is.  if one of you devs needs that IP to see if it's been blacklisted or soemthign crazy, send me a PM.  keep in mind, wallet was connecting before i tried to resolve my Dice tx's not showing properly.

one thing i just thought is, these LTS are entirely from PTS ownership, and i guess not useable until Sept 14?  hope that didn't break my wallet.

2014-09-03 00:56:54 Loading addresses from DNS seeds (could take a while)
2014-09-03 00:56:54 addcon thread start
2014-09-03 00:56:54 dumpaddr thread start
2014-09-03 00:56:54 init message: Done loading
2014-09-03 00:56:54 refreshWallet
2014-09-03 00:56:54 2 addresses found from DNS seeds
2014-09-03 00:56:54 dnsseed thread exit
2014-09-03 00:56:55 trying connection 130.255.189.68:6042 lastseen=90.5hrs
2014-09-03 00:56:55 connected 130.255.189.68:6042
2014-09-03 00:56:55 send version message: version 70002, blocks=0, us=0.0.0.0:0, them=130.255.189.68:6042, peer=130.255.189.68:6042
2014-09-03 00:56:55 socket recv error 10054
2014-09-03 00:56:55 disconnecting node 130.255.189.68:6042
2014-09-03 00:56:55 GetMyExternalIP() received [myIP] myIP:0
2014-09-03 00:56:55 GetMyExternalIP() returned 76.219.197.62
2014-09-03 00:56:55 AddLocal(myIP:6042,4)
2014-09-03 00:56:55 trying connection 137.117.246.253:6042 lastseen=92.5hrs
2014-09-03 00:56:56 connected 137.117.246.253:6042
2014-09-03 00:56:56 send version message: version 70002, blocks=0, us=myIP:6042, them=137.117.246.253:6042, peer=137.117.246.253:6042
2014-09-03 00:56:56 socket recv error 10054
2014-09-03 00:56:56 disconnecting node 137.117.246.253:6042
2014-09-03 00:57:00 trying connection 137.117.246.253:6042 lastseen=92.5hrs
2014-09-03 00:57:00 connected 137.117.246.253:6042
2014-09-03 00:57:00 send version message: version 70002, blocks=0, us=myIP:6042, them=137.117.246.253:6042, peer=137.117.246.253:6042
2014-09-03 00:57:00 socket closed
2014-09-03 00:57:00 disconnecting node 137.117.246.253:6042
2014-09-03 00:57:02 No valid UPnP IGDs found
2014-09-03 00:57:02 upnp thread exit
2014-09-03 00:57:04 trying connection 130.255.189.68:6042 lastseen=90.5hrs
2014-09-03 00:57:04 connected 130.255.189.68:6042
2014-09-03 00:57:04 send version message: version 70002, blocks=0, us=myIP:6042, them=130.255.189.68:6042, peer=130.255.189.68:6042
2014-09-03 00:57:04 socket recv error 10053
2014-09-03 00:57:04 disconnecting node 130.255.189.68:6042

Quote from: merockstar on August 28, 2014, 12:29:52 am

update: glad Im hodling strong.

I don't really know what you were complaining about in the first place.  LottoShares was a complete surprise.

yeah it was!!  i sent my PTS  to an exchange to sell, at block 65970.  Yep, that's 11 blocks befroe the snapshot for LottoShares was taken.  Snapshot for LottoShares was taken at block 65959.  I had to double check everything, since the date for LTS snapshot was 5/31 and that's the same date i sent the PTS from my wallet. 

complete dumb luck on my part, considering i just found out about the LTS snapshot about 2 days ago.

as for return on investment, the big return so far has been BTSX.  from nearly 6 PTS, i got 3624 BTSX, with a current value of .21 BTC.   that's more than i paid for my PTS, plus i got BTC back when i sold them.  win win

  i ended up losing some BTC on the PTS tx's, but more than made up for it with the BTSX distribution. 

when i got my BTSX, i sold half, and put that BTC back into PTS, so i would be ready for the snapshot on Aug 21.  This time i'll just hold the PTS.  don't want to mess around and end up losing out on any surprise DAC releases.

Quote from: stanno on August 28, 2014, 08:45:09 pm

you can go here http://dacsunlimited.com/binaries/wallet/  and get any version you like.

i'm thinking my current sync issues may be due to my need to upgrade from 4.8 to 4.9.  waiting for an answer to my sync question before i go that route.

No the old version are not working because of the hard fork. You should install version 0.4.9-a this is the one working. Also I suggest to do a clean installation too : https://bitsharestalk.org/index.php?topic=7849.msg103955#msg103955

i figured that was the issue, since my wallet stopped updating at an even numbered block.  340800.  some random network issue or whatever would have a very small chance of stopping the sync at such an even number.

i just installed over the top, and it's working just fine.  maybe i'll do a clean install on the next upgrade...

that's weird.  you must have something else going on with your computer.   I just upgraded to the latest version, 4.9, and my wallet synced right up.  no problems at all.

anyone else "stuck" at block 340800?  wallet has been trying to sync for the last 35 minutes. 

here's my installation info:

wallet version 0.4.8-a

bitshares_toolkit_revision    f9612af57c24b5831936bbd2c7d155d4eb2d8af8
bitshares_toolkit_revision_age    69 hours ago
compile_date    compiled on Aug 25 2014 at 17:10:24
fc_revision    198d858d590f9f968f554a6036275cbbd7f78907
fc_revision_age    4 days ago

  "version": 109,
  "db_version": 129,

looks like i had some connection issues on 8/19, during the initial setup of the wallet.  one log was .5GB.  couple of others on 8/19 and 8/20 were .2 to .4GB.   after i got my account registered and the PTS wallet imported, the log size shrunk considerably, with largest being 24MB.   most are in the 6-9MB range.

had the same pattern when i upgraded to the latest wallet version.  I was on v3 something, and it stopped syncing.  4.08 fixed everything.

still working on the Linux wallet installation though.  On ubuntu 14.04, i got the wallet to where it opens on the test network.  I'm thinking i just need to copy the config.json file, and probably the rest of files from the %appdata%/BitsharesX folder from my windows installation, over to the linux VM.  That sound like it will work?

One thing i've noticed about the Ubuntu installation instructions:  there is a README in every directory below the top level BitsharesX directory.  They have conflicting/incomplete installation instructions.  Once i finally found the one with the complete and accurate instructions, i was finally able to get the wallet installed correctly.  The source on github needs a bit of cleaning.  consistency across all of the readme's, or removal of all but the 1 that works would be awesome, and probably save many others the headaches i ran into.  something to do in your spare time, of course.  lol

well.....  after a painfilled day of trying to get bitsharesx wallet installed on my Debian 7.6 VM, i threw in the towel.

On the bright side, no issues whatsoever installing BTSX wallet to the new Ubuntu 14.04 VM i just built. 

Ubuntu has more recent versions of boost and cmake, which fixed all of the Path and version issues i was having with Debian. 

i'm only about a year into my linux expedition, and apparently still have a lot to learn. 

go figure.