Closed urkovs closed 6 years ago
have you run the Beta Desktop before
I just downloaded it, tried to open it, got stuck on this screen. Then I closed it and reopened it. Same thing. I have not ever successfully been able to access. Though, I can still access Syscoin Core.
Sorry you didnt answer the question can you go to the #help channel in Slack
This is 1.1.0, could you try with Blockmarket 1.1.1?
This has been reported by several people, it seems to be isolated to OSX users at the moment.
this has hjappened to me on windows 10 never loads. any help out there
Having the same problem on up to date Windows 7 64-bit.
Started about 30 hours ago. About an hour ago I noticed there hadn't been any block updates in ~30 hours. I closed Blockmarket and reopened it but it got stuck on the loading page. I updated to 1.1.3 because I was still on 1.0.1 and figured that was probably the problem but no change, currently stuck on 1.1.3 loading screen. Tried changing VPN nodes, no change. Tried no VPN, no change.
This is very problematic. The hell is going on?
-edit- I tested - if I rename the %appdata%/Blockmarket folder the program starts but I have no access to my alias/wallet. I need access to my alias/wallet, guys.
-edit2- I've resolved the issue thanks to having a backup of my wallet.dat file. So I had to delete/rename the %appdata%/Blockmarket folder and resync the blockchain. This causes Blockmarket Desktop to overwrite the wallet.dat file in %appdata%/Syscoin. Putting my backup wallet.dat back in that folder fixes the problem.
I'd strongly recommend there be a pop up warning whenever Blockmarket Desktop overwrites the wallet.dat file. I got zero notification of this, it just overwrote it when I started it.
For @urkovs I'd take a backup of your wallet file, delete the blockchain, resync and restore your wallet.dat file. And always keep a backup of that wallet file.
Windows 10 here, I'm currently stuck on loading screen, followed the above post. Ended up deleting blockchain and all files from %appdata%/Syscoin and %appdata%/Blockmarket and letting it create a new wallet. Id moved my coins and deleted the backups, guess I should have made a copy like above and overwrote the new wallet with the copy, idk, still stuck...
I did notice that syscoind wants to stay running even when you close the Blockmarket client which also prevents you from deleting or moving files in the folders, thats the first issue I ran into as everytime I'd delete the wallet.dat it would continue to recreate a new one over and over until I'd realized the syscoind wasn't closing.
Bah....
It finally opened. Guess I had to let it sit there on that screen for a while.
I'm experiencing the issue now, win64
I have steps to reproduce this from a known-working state but need to test and verify, this may only be one variant of the causes:
The issue / part of the issue seems to be when BM runs syscoind in a state that introduces anything other than a standard load-up, it seems the syscoind process can become detached from the BM process. I ran into this myself and only noticed when I fell back to QT after quitting BM and it complained syscoind was still running. Sure enough:
I suspect a similar but inverted situation may occur when BM is left running for a long time (syscoind will quit, resulting in 500s from the BM side).
I'm still dealing with this issue. I can't even remember the last time I actually got the Blockmarket Desktop to open. Downloaded update after reading this update, installed, executed, and..... stuck on loading screen as usual.
Ok, after following the steps in the above link, it worked and opened, however, the only wallet file i was able to find my my old data directory was a wallet(stringofrandonnumbers).bak
Like my wallet.dat had been overwritten by the above file.
Inserted a backup of my old wallet.dat into the new data directory folder after renaming the new wallet.dat that had been created.
Executed Blockmarket again, stuck on loading screen.... Doesn't seem to want to open my original wallet.dat
Ideas?
Something not right. I've tried several syscoin wallet.dat backups and can't get any of them to open in Blockmarket, After placing them in the new syscoin data directory and executing Blockmarket, wallet doesn't load and after closing the wallet.dat backups remain unchanged with unchanged last modified date still being in 2016.
I'm just going to assume my old wallet got corrupted somehow and fortunately I haven't got any coins on there anymore so its no big deal, however I'd be disappointed if I'd still had a balance on the wallet.
If you don't have another syscoind
process already running you likely need to reindex.
A temporary workaround for this issue on OSX is to run the following commands from a Terminal window. It will trigger a reindex of the internal database which might be slow. Balances/Aliases/etc will not be accurate until the blocks have finished syncing.
# Location of the Blockmarket Desktop syscoin.conf, may be different from QT or syscoind
SYSCOIN_CONF=~/Library/Application\ Support/Blockmarket/syscoin.conf
# Use the same binaries as the desktop client
cd /Applications/Blockmarket.app/Contents/Resources/bin/darwin/
# Reindex using the appropriate conf file, make sure to include & at the end
./syscoind --conf=$SYSCOIN_CONF -reindex &
# Gracefully shutdown syscoind using the cli
./syscoin-cli --conf=$SYSCOIN_CONF stop
You should then be able to open Blockmarket.app successfully, again note that it will take some time to resync.
@dwasyluk the failure to load when another syscoind
is a similar but unrelated issue. You need to stop it with the cli via syscoin-cli stop
or if it is a rogue process that cannot be stopped killall syscoind
.
Tested on Windows 10, no problem with being stuck on loading screen.
having the same issues on OSX with Blockmarket v1.0.1
I have Mac OS Sierra on a Macbook Air. I am trying to use the Blockmarket v1.1.0. When I open it, I see the startup screen with the two gears turning around, and text displayed which says "Blockmarket Desktop Loading". However, it goes nowhere from that display. Nothing ever loads.
Is there a fix for this or is it a known bug?![screen shot 2017-11-06 at 9 18 28 am](https://user-images.githubusercontent.com/31389454/32454239-7de45e42-c2d3-11e7-8f77-3b550cc0297a.png)