BitShares Forum
Main => Technical Support => Topic started by: yellowecho on January 03, 2014, 06:24:32 am
-
Every time I try to launch the client, I get a prompt that says "ProtoShares-Qt quit unexpectedly". This occurs while it says its verifying blocks. I've reinstalled the app several times without success.
Can anyone help me with this? It's very frustrating since I couldn't move my PTS from Cryptsy for the MMC release and I'm scared I'm going to miss it for Bitshares and Keyhotee :-[
-
Welcome to the forum yellowecho,
Have you tried the solution (https://bitsharestalk.org/index.php?topic=1902.msg21883#msg21883) mentioned by toast. This is also an OSX client which keeps crashing.
If you have not done this. Make sure to keep a backup of the wallet.
-
I get the same "ProtoShares-Qt quit unexpectedly" alert prompt followed by the following displayed in the terminal:
Assertion failed: (pfork != NULL), function SetBestChain, file src/main.cpp, line 1826.
Abort trap: 6
-
I found two possible fixes online.
One is to try running the client with -reindex
The other is described here:
https://bitcointalk.org/index.php?topic=154516.msg1665186#msg1665186
But I'm not sure what script he's referring to
-
I found two possible fixes online.
One is to try running the client with -reindex
The other is described here:
https://bitcointalk.org/index.php?topic=154516.msg1665186#msg1665186
But I'm not sure what script he's referring to
How do I run the client with -reindex? What's that mean?
I'm a n00b so this is quite confusing.
-
in terminal type
/Applications/ProtoShares-Qt-0.2.0.app/Contents/MacOS/ProtoShares-Qt -reindex
-
We're getting closer!
The client opened but it's not loading the blockchain. It says "No block source available" in the lower left and shows no active connections on the network in the lower left.
-
Yep, really close!
In the pts client, go to help->debug window and then click console. Then type
addnode 162.243.197.231 add
It should find some nodes within a few minutes.
Let me know if you connect, if you don't it should be a matter of finding some other good nodes. The newest version of the client has good nodes baked in but I'm not sure if it's on the website yet.
edit: A few more nodes to try, just type that same line with each of these if it isn't able to connect
175.42.27.186
169.237.74.213
183.8.183.73
222.174.212.250
-
That worked! I'm seeing active connections and its loading the blockchain. Thank you so much!
-
Happy to help! =D