BitsharesX Version 0.4.7 Report

[Tuck Fheman]

if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3. 

Doh, that fixed it!

[38PTSWarrior]

ubuntu 32bit: I can see the blockcount rising with getblockcount but in the right bottom corner it says "not connected". "getconnectioncount" says 8 connections.

The little wheel with the blockcounter is also not there.

[xeroc]

my main delegate crashed ... the monitoring node (that was supposed to switch active delegates to a backup delegate) was on a fork and got stuck (wtf?)
backup delegate was running fine on main chain .. wallet locked :(

might need to modify my backup strategy :(

[bytemaster]

No attack. Likely just the crash bug.  They will be back soon.

[liondani]

All init delegates are not producing blocks right now....

Code Select Expand

 
"blockchain_average_delegate_participation": "72.66 %",

it dropped to 68% for a while...

is it related with version 0.4.7 ?
or is it some kind of an attack to our network since there are missing a few more delegates blocks right now?



graphs not looking good  :(
http://x.bitmeat.com/

[xeroc]

FYI, current code is still working single-threads (afaik) .. once BM can take the time to refactor the code we will see a huge performance increase ..

Be reminded: This is cutting edge technology ... cutting edge is supposed to be a little rough here and there :)

[38PTSWarrior]

got my wallet to sync btw.  got no crashes.  but syncing was slow, had 8 connections max.  is that normal?

It's normal.

[lucky331]

got my wallet to sync btw.  got no crashes.  but syncing was slow, had 8 connections max.  is that normal?

[lucky331]

I installed 0.4.7 and it crashed.

I deleted all folders except for the wallets folder.

Then I restarted the client and was prompted to reset the database or not, I did.

Then without prompting for a password the wallet loaded up and displayed all contents/balances, etc. (locked however). 

After attempting to sync for a few minutes it auto-logged out and then went to the password screen.

if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3. 

crashes seemed to stop when i did this.

[lucky331]

I've had three crashes so far since running 0.4.7.  When the wallet crashes, it sends a report. But then I cannot open the wallet again by double-clicking on it. I have to restart the computer to be able to run the wallet. It's currently syncing, hopefully if it completely syncs then I wont have any issues.

Also, since I imported my wallet and it hasn't completely synced yet, I am not seeing a config.json file in the appdata/roaming/Bitshares X folder   and without the config.json I cannot add the chain server. This might be an issue that needs looked at. Also some people are reporting the chain server is not working anymore.

if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3. 

crashes seemed to stop when i did this.

[Tuck Fheman]

I installed 0.4.7 and it crashed.

I deleted all folders except for the wallets folder.

Then I restarted the client and was prompted to reset the database or not, I did.

Then without prompting for a password the wallet loaded up and displayed all contents/balances, etc. (locked however). 

After attempting to sync for a few minutes it auto-logged out and then went to the password screen.

[cryptkeeper]

https://github.com/dacsunlimited/bitsharesx/releases

is downloading the new wallet off bitshares-x.info an option as well?

[vikram]

https://github.com/dacsunlimited/bitsharesx/releases

Thank you! Now someone should sticky that sucker to the top of every applicable sub-forum.  ;D

I also recommend subscribing to notifications on the BTSX import announcement thread: https://bitsharestalk.org/index.php?topic=7067.msg94189#msg94189

[Tuck Fheman]

https://github.com/dacsunlimited/bitsharesx/releases

Thank you! Now someone should sticky that sucker to the top of every applicable sub-forum.  ;D

[xeroc]

https://github.com/dacsunlimited/bitsharesx/releases

[Tuck Fheman]

Where does one find all these different versions of the client again?  There was a sticky for 0.4.5 but now I can't find it and never did find 0.4.6 and now I see there's a 0.4.7 but no readily available link posted anywhere I can find.   :-\

If would be cool if there was one easy to find sticky thread for the latest release of the client (or is there? if so, where? because it's not easy to find).

[dankeykang]

I've had three crashes so far since running 0.4.7.  When the wallet crashes, it sends a report. But then I cannot open the wallet again by double-clicking on it. I have to restart the computer to be able to run the wallet. It's currently syncing, hopefully if it completely syncs then I wont have any issues.

Also, since I imported my wallet and it hasn't completely synced yet, I am not seeing a config.json file in the appdata/roaming/Bitshares X folder   and without the config.json I cannot add the chain server. This might be an issue that needs looked at. Also some people are reporting the chain server is not working anymore.

The reason you can't reopen the wallet after some of those crashes is that there's still a BitsharesX process running in the background.  Instead of restarting, you can kill that process using the task manager and then you should be able to run it again.

Oh man, thank you! I can't believe I didnt think of that

[Troglodactyl]

I've had three crashes so far since running 0.4.7.  When the wallet crashes, it sends a report. But then I cannot open the wallet again by double-clicking on it. I have to restart the computer to be able to run the wallet. It's currently syncing, hopefully if it completely syncs then I wont have any issues.

Also, since I imported my wallet and it hasn't completely synced yet, I am not seeing a config.json file in the appdata/roaming/Bitshares X folder   and without the config.json I cannot add the chain server. This might be an issue that needs looked at. Also some people are reporting the chain server is not working anymore.

The reason you can't reopen the wallet after some of those crashes is that there's still a BitsharesX process running in the background.  Instead of restarting, you can kill that process using the task manager and then you should be able to run it again.

[dankeykang]

I've had three crashes so far since running 0.4.7.  When the wallet crashes, it sends a report. But then I cannot open the wallet again by double-clicking on it. I have to restart the computer to be able to run the wallet. It's currently syncing, hopefully if it completely syncs then I wont have any issues.

Also, since I imported my wallet and it hasn't completely synced yet, I am not seeing a config.json file in the appdata/roaming/Bitshares X folder   and without the config.json I cannot add the chain server. This might be an issue that needs looked at. Also some people are reporting the chain server is not working anymore.

[xeroc]

Figured. But just to be really sure. If I export my .json wallet, install the latest version, then import the wallet, my funds would be intact right? I'm using OS X Mavericks. Thanks.

*confirmed*

[burnourdough]

There was a hard fork with old wallet


Sent from my iPhone using Tapatalk

Figured. But just to be really sure. If I export my .json wallet, install the latest version, then import the wallet, my funds would be intact right? I'm using OS X Mavericks. Thanks.

[bitder]

I'm running the 0.4.7 client built from source on ubuntu.
It can get stuck syncing if you don't have your wallet open.

[GaltReport]

Something's wrong.  I mean really.  I cannot sync my wallet. It's really slow.  I hope the Bitshares crew are looking into it.

I have 1 new server like this.  has only 1 connection.  previously had 0 for a long time.  says 3 hours remaining.  Oh, maybe it's that chain server thing?  Saw a post by bytemaster saying if it is using chain server it will show 0 connections.

[bytemaster]

There was a hard fork with old wallet


Sent from my iPhone using Tapatalk

[burnourdough]

Something's wrong.  I mean really.  I cannot sync my wallet. It's really slow.  I hope the Bitshares crew are looking into it.

I'm still at wallet 0.3.0 and couldn't sync past block 275171. It gives up after awhile then attempts to sync again starting at 275165.

[joele]

if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3. 

crashes seemed to stop when i did this.

Awesome, thanks!  :D

[bytemaster]

if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3. 

crashes seemed to stop when i did this.

+1. 


Sent from my iPhone using Tapatalk

[lucky331]

if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3. 

crashes seemed to stop when i did this. 

[joele]

0.4.7 still keep crashing.

[lucky331]

Something's wrong.  I mean really.  I cannot sync my wallet. It's really slow.  I hope the Bitshares crew are looking into it.

[xeroc]

My nodes have already produced 215 GB of trafffic .. just this month ..

[lucky331]

ok.. so it seems when i leave it long enough it continues syncing, but super slow.  is there something wrong with the network?  ddos maybe?  or maybe a sudden influx of people dowloading the client then syncing?

[lucky331]

Ok. No crash this time, but syncing is stuck at block 87,862. 

I have also put "69.90.132.209:1375" in "chain_servers".  But i still go straight to p2p mode.  I think it's because either the chain server is down or port 1375 is close.  Please check.

Thanks.  :)