I ran it in the debugger, maybe it's still running, as there's my 'gdb...' command still in htop.

After 10 minutes or so I got the (gdb) prompt in my console:

Reading symbols from /home/ubuntu/BitSharesX/bitshares_toolkit/programs/client/bitshares_client...done.
(gdb)

I don't know if that's because it finally crashed or not, as I said, the gdb command's still present in htop.

Not sure what to do next- I don't see the command I'm used to seeing when the daemon is running: 'bltsharesx-cli --daemon' in htop, never have yet.

Not even sure the start then crash ever happened being that I didn't see that command appear.

I don't know if it might be necessary for someone else to try to recreate the problem on a VM or something, I'm running Ubuntu 12.04 with kernel 3.13.0-37-generic.

I do know that since I got to the (gdb) prompt, mysql has crashed & won't start again. I'm hesitant to reboot since I don't know if the daemon might actually be running & I ought to wait for it to crash again to debug it right.

Please advise.

I get this from gdb:

Reading symbols from bitshares_client...(no debugging symbols found)...done.
(gdb)

...And I don't see the client process show up in htop.

But it starts if I don't use gdb before the plain 'bitshares_client' command.

Hi,

I've upgraded from 0.4.19 to the 0.4.20+a version in the Ubuntu ppa, & it still won't stay running on my box.

I tried deleting everything in the .BitSharesX directory except config.json to no avail, it'll stay running for a little while then die.

I see problems in p2p.log that seem ominous, & suspect that's the problem, but I'm no expert so I'm posting here for help.

p2p.log:

20141009T090425.968249     ntp:ntp_read_loop          request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:55
20141009T090426.216655     ntp:ntp_read_loop          request_now ] sending request to 108.61.73.243:123 ntp.cpp:59
20141009T090426.225183     ntp:ntp_read_loop            read_loop ] received ntp reply from 108.61.73.243:123 ntp.cpp:120
20141009T090426.225258     ntp:ntp_read_loop            read_loop ] ntp_delta_time updated to -71311 ntp.cpp:145
20141009T090427.205787        th_a:?unnamed?        open_database ] old database version, upgrade and re-sync chain_database.cpp:105
20141009T090430.725502        th_a:?unnamed?                 open ] loading pending trx... chain_database.cpp:1074
20141009T090438.922354   upnp:upnp::map_port           operator() ] No valid UPnP IGDs found upnp.cpp:157
20141009T090443.881835 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090443.933725   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.131.35.149:1776: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090443.935878 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090443.928942"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141009T090444.006358   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 54.77.51.177:1776: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090444.006686 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090444.005917"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141009T090444.013204   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 5.101.106.138:1777: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090444.013430 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090444.013086"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141009T090444.017498   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 178.62.157.161:1776: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090444.017694 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090444.016865"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141009T090444.151510   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 61.129.33.213:1776: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090444.151857 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090444.150642"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141009T090444.179158   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 54.79.27.224:1776: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090444.179484 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090444.179038"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141009T090445.557016 p2p:message read_loop on_closing_connectio ] Peer 180.153.142.120:1777 is disconnecting us because: I rejected your connection request (hello message) so I'm disconnecting node.cpp:2501
20141009T090445.610143 p2p:message read_loop            read_loop ] disconnected 0 exception: unspecified
Bad file descriptor
    {"message":"Bad file descriptor"}
    asio  asio.cpp:37 operator()

    {"len":16}
    p2p  stcp_socket.cpp:94 readsome message_oriented_connection.cpp:182
20141009T090445.610351 p2p:delayed_peer_deletion_task   destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":184,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"20141009T090445.610207"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nBad file descriptor \n    {\"message\":\"Bad file descriptor\"}\n    asio  asio.cpp:37 operator()\n\n    {\"len\":16}\n    p2p  stcp_socket.cpp:94 readsome"}}]} message_oriented_connection.cpp:274
20141009T090445.610453 p2p:delayed_peer_deletion_task   destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":184,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"20141009T090445.610207"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nBad file descriptor \n    {\"message\":\"Bad file descriptor\"}\n    asio  asio.cpp:37 operator()\n\n    {\"len\":16}\n    p2p  stcp_socket.cpp:94 readsome"}}]} message_oriented_connection.cpp:274
20141009T090449.919339 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Forcibly disconnecting from handshaking peer 89.187.144.203:8764 due to inactivity of at least 5 seconds node.cpp:1193
20141009T090449.919404 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1197
20141009T090449.919446 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Forcibly disconnecting from handshaking peer 188.226.195.137:60696 due to inactivity of at least 5 seconds node.cpp:1193
20141009T090449.919471 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1197
20141009T090449.920938   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 188.226.195.137:60696: 0 exception: unspecified
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141009T090449.921141 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"20141009T090449.920455"},"format":"${message} ","data":{"message":"Operation canceled"}}]}
default.log:

20141009T090425.968249     ntp:ntp_read_loop          request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:55
20141009T090426.216655     ntp:ntp_read_loop          request_now ] sending request to 108.61.73.243:123 ntp.cpp:59
20141009T090426.225183     ntp:ntp_read_loop            read_loop ] received ntp reply from 108.61.73.243:123 ntp.cpp:120
20141009T090426.225258     ntp:ntp_read_loop            read_loop ] ntp_delta_time updated to -71311 ntp.cpp:145
20141009T090427.205787        th_a:?unnamed?        open_database ] old database version, upgrade and re-sync chain_database.cpp:105
20141009T090430.725502        th_a:?unnamed?                 open ] loading pending trx... chain_database.cpp:1074
20141009T090438.922354   upnp:upnp::map_port           operator() ] No valid UPnP IGDs found upnp.cpp:157
20141009T090443.881835 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090456.885002 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090509.892257 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090522.892461 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090535.894387 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090548.895160 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090601.897461 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090614.897692 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090627.901372 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090640.903119 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141009T090653.903355 th_a:rebroadcast_pending rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1098
20141009T090706.904391 th_a:rebroadcast_pending rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1098
20141009T090719.924230 th_a:rebroadcast_pending rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1098
20141009T090733.227063 th_a:rebroadcast_pending rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1098

Would someone kindly interpret this for me & provide some guidance?

Thanks,

-F

known issues with 0.4.19

https://bitsharestalk.org/index.php?topic=9564.new#new

Bummer, thanks for letting me know.

Good luck & godspeed to the devs working on the fix. :-)

Hi,

Being that backups containing more than 1 account don't restore properly, I was thinking I could copy 'wallet a' directory contents to a staging folder, start the client & have a new wallet with zero accounts in to create a new account in 'wallet b'. I wanted to be able to switch back & forth between the 2 to access the different accounts by simply copying the default wallet directory contents in & out of the default wallet folder.

But apparently it doesn't work that way. I emptied the default wallet folder, started the client, & it asks for a password which isn't the original password from 'wallet a', and which I don't know.

How can I set this up the way I'm aiming to? I want more than 1 account, but I don't want to lose the ability to restore from backups.

Thanks,
-F

PTS may fall after a snap shot(see Stan's blog post: Watch for falling PTS), and your gains on investment may only be realized when BTS music is up and running weeks or months later..

Who's Stan, & where's his blog?

I had the same idea that 'music' might take awhile to gain value. So maybe that won't be part of what I do.

Right now the money I have in PTS was what I had in mind to use to incorporate a business I want to start. I might still want to do that, & I'm hoping I can make $100 or so on the PTS spike, if it materializes.

...Always on the lookout for a side job.

Since this is the first snapshot I'll be a part of, I'm not sure what to expect, so I'd like to learn from those of you who've been through this before.

While I'm not particularly interested in holding Songshares, I do see a potentially profitable situation on the horizon with the Snapshot coming up. What I don't know are the historical details necessary to realistically formulate a profitable strategy.

I see that PTS rallied when the Snapshot was announced, & I have, along with apparently many others, spent some BTC on PTS since the announcement. I don't know however, if I'd be better off holding my PTS through the Snapshot so I would receive some Songshares, or if I would make more by selling my PTS just before the Snapshot, assuming its price will be at its highest say, on the 9th of October.

A) Where can I look at pricing data of BTSX, PTS, & DAC's being Snapshottted for time periods during previous Snapshots?

B) How exactly are the allotted Songshares redeemed after the Snapshot?

C) Will I have to wait at all between the time of the Snapshot & the time I'm able to have Songshares to sell?

D) When is the price of PTS expected to peak?

E) Is there maybe some counterintuitive dip that happens say, 6 hours before the Snapshot when everyone who's going to buy into it already has?

F) When is the value of the alotted Songshares expected to be high?

G) How much is the value of PTS expected to drop immediately following the Snapshot?

H) Might the value of my new Songshares plus the value of my PTS provide a healthy ROI such that I'll want to sell both sometime after the Snapshot?

I) Do newly Snapshotted/allotted DACs peak right after a Snapshot?

J) How long might I want to hold my Songshares before selling them should I be seeking to recoup what I spent on PTS?

K) Might I be able at some point to sell my Songshares at such a price that I'm able to recoup my PTS investment within a relatively short period of time, while keeping my PTS holdings intact in anticipation of a future Snapshot?

L) What strategies are others employing aside from indefinite buy & hold?

And one last question, I may as well ask because it does cross my mind not knowing...

M) Is the profit potential of this Music DAC Snapshot sure enough that it might be worthwhile for me to allocate my October's rent to it, assuming I'd be able to make enough of a profit that I could sell it, get my money back with enough left over to cover my late fees & then some?


Thanks in advance for your feedback.

-F