Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - FuLl

Pages: [1] 2
1
Technical Support / Trying to restore old .json wallets from 2015
« on: September 11, 2019, 12:52:25 am »
I had 2 accounts back then, & still have their .json wallet files from when I ran BitSharesX. The last version I used was 0.4.23.1

If I remember correctly I also had some kind of different token from when I was running BitShares-PTS 1.0.0

I've installed BitShares2-light on Ubuntu 16.04 & none of the options I find there want my .json files.

Could use a hand.

2
Technical Support / Why is BitSharesX so memory intensive?
« on: October 31, 2014, 04:19:44 am »
I run Bitcoin, Litecoin, Namecoin, & BitSharesX clients in a VM with 3072MB RAM, & when I run these clients minus the BitSharesX client running, the box uses approximately 1950MB of RAM. When I start the BitSharesX client, it spikes up to using all 3000MB, plus all my 2048MB of swap.

I'm just curious as to what the BitSharesX client is doing that requires so much memory. And will it ever use less in future versions?

3
Hi,

I had to do the following differently during build to get past errors I encountered during the process.

1. sudo aptitude install qttools5-dev

2a. After the step: cd programs/web_wallet

2b. npm config set registry http://registry.npmjs.org/

3a. After the step: sudo npm install -g lineman

3b. sudo npm install


When I get to the step where I do: make BitSharesX

I'm doing this: sudo cp programs/qt_wallet/bin/BitSharesX /usr/local/bin/

...to install it system wide, but there's nothing in /home/full/bitsharesx/programs/qt_wallet/bin

So I guess it didn't build properly.

I'm following the instructions on the wiki to build it with the QT GUI on Ubuntu 14.04.

How do I fix it?

Thanks,
-F

4
KeyID / Transfer from Bter to wallet fails
« on: October 12, 2014, 11:30:49 pm »
Hi,

I must have misunderstood something here, because 3 out of 3 times now I've tried to withdraw my BitSharesDNS from Bter to my KeyID wallet, & after an hour or so the funds re-appear in my Bter account, never making it to the wallet.

I'm using the registered key string as my withdrawal address in my account.

What's wrong? Is there a different currency, or a different wallet, or a different value to use as my address?

Thanks,
-F

5
Technical Support / bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« on: October 09, 2014, 11:12:00 am »
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:

Code: [Select]
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:

Code: [Select]
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

6
Technical Support / bitsharesx-cli v. 0.4.19 process won't stay running
« on: October 02, 2014, 01:24:04 pm »
Hi,

My seed node is down & I need some help to get it back up.

I'm used to the client not running when it's depreciated & there's an update to be installed, but according to aptitude I have the most recent version now, & it won't stay running for more than 5 minutes.

I tried deleting everything but 'config.json' in the /root/.BitSharesX/ directory in case it wanted to start over, but still it stops running.

The following is in default.log:

Code: [Select]
20141002T130151.950001     ntp:ntp_read_loop          request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:55
20141002T130152.047217     ntp:ntp_read_loop          request_now ] sending request to 167.88.119.29:123 ntp.cpp:59
20141002T130152.067212     ntp:ntp_read_loop            read_loop ] received ntp reply from 167.88.119.29:123 ntp.cpp:120
20141002T130152.067321     ntp:ntp_read_loop            read_loop ] ntp_delta_time updated to 3158 ntp.cpp:145
20141002T130152.952717        th_a:?unnamed?        open_database ] old database version, upgrade and re-sync chain_database.cpp:105
20141002T130156.280816        th_a:?unnamed?                 open ] loading pending trx... chain_database.cpp:1074
20141002T130204.444662   upnp:upnp::map_port           operator() ] No valid UPnP IGDs found upnp.cpp:157
20141002T130209.410461 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130222.472185 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130235.641888 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130248.851634 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130301.919106 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130314.919330 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130328.013531 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130341.093474 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130354.102885 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130407.911250 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130420.911469 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130433.979763 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130447.064326 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130500.224201 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130513.305901 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130526.306273 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130539.461313 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130552.765883 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130605.818549 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130619.097398 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130632.100851 th_a:rebroadcast_pending rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1098
20141002T130645.114172 th_a:rebroadcast_pending rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1098

And this is my p2p.log:

Code: [Select]
20141002T130151.950001     ntp:ntp_read_loop          request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:55
20141002T130152.047217     ntp:ntp_read_loop          request_now ] sending request to 167.88.119.29:123 ntp.cpp:59
20141002T130152.067212     ntp:ntp_read_loop            read_loop ] received ntp reply from 167.88.119.29:123 ntp.cpp:120
20141002T130152.067321     ntp:ntp_read_loop            read_loop ] ntp_delta_time updated to 3158 ntp.cpp:145
20141002T130152.952717        th_a:?unnamed?        open_database ] old database version, upgrade and re-sync chain_database.cpp:105
20141002T130156.280816        th_a:?unnamed?                 open ] loading pending trx... chain_database.cpp:1074
20141002T130204.444662   upnp:upnp::map_port           operator() ] No valid UPnP IGDs found upnp.cpp:157
20141002T130209.410461 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130209.530186   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 188.226.195.137:60696: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141002T130209.531980 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":"20141002T130209.525050"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141002T130209.536157   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
20141002T130209.536384 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":"20141002T130209.535021"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141002T130209.537471   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
20141002T130209.537755 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":"20141002T130209.534222"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141002T130209.765031   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
20141002T130209.765255 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":"20141002T130209.764907"},"format":"${message} ","data":{"message":"Connection refused"}}]} peer_connection.cpp:107
20141002T130210.129586 p2p:message read_loop on_closing_connectio ] Peer 80.240.133.79:1777 is disconnecting us because: I rejected your connection request (hello message) so I'm disconnecting node.cpp:2501
20141002T130210.131960 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
20141002T130210.132229 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":"20141002T130210.132011"},"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
20141002T130210.132328 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":"20141002T130210.132011"},"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
20141002T130211.486805 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
20141002T130211.487708 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
20141002T130211.487875 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":"20141002T130211.487755"},"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
20141002T130211.487971 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":"20141002T130211.487755"},"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
20141002T130215.439055 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
20141002T130215.439123 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1197
20141002T130215.439169 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Forcibly disconnecting from handshaking peer 95.85.33.16:8764 due to inactivity of at least 5 seconds node.cpp:1193
20141002T130215.439195 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1197
20141002T130215.439824   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 89.187.144.203:8764: 0 exception: unspecified
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:59 error_handler peer_connection.cpp:204
20141002T130215.440073 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":"20141002T130215.439370"},"format":"${message} ","data":{"message":"Operation canceled"}}]} peer_connection.cpp:107
20141002T130215.440456   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 95.85.33.16:8764: 0 exception: unspecified
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:37 operator() peer_connection.cpp:204
20141002T130215.440624 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":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"20141002T130215.439472"},"format":"${message} ","data":{"message":"Operation canceled"}}]} peer_connection.cpp:107
20141002T130221.516458 p2p:message read_loop            read_loop ] disconnected 0 exception: unspecified
Connection reset by peer
    {"message":"Connection reset by peer"}
    asio  asio.cpp:37 operator()

    {"len":16}
    p2p  stcp_socket.cpp:94 readsome message_oriented_connection.cpp:182
20141002T130221.516735 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 54.79.27.224:1776 because they didn't respond to my request for sync item ids after 0000000000000000000000000000000000000000 node.cpp:1240
20141002T130221.516986 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":"20141002T130221.516517"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nConnection reset by peer \n    {\"message\":\"Connection reset by peer\"}\n    asio  asio.cpp:37 operator()\n\n    {\"len\":16}\n    p2p  stcp_socket.cpp:94 readsome"}}]} message_oriented_connection.cpp:274
20141002T130221.517090 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":"20141002T130221.516517"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nConnection reset by peer \n    {\"message\":\"Connection reset by peer\"}\n    asio  asio.cpp:37 operator()\n\n    {\"len\":16}\n    p2p  stcp_socket.cpp:94 readsome"}}]} message_oriented_connection.cpp:274
20141002T130221.517388 p2p:message read_loop            read_loop ] disconnected 0 exception: unspecified
Operation canceled
    {"message":"Operation canceled"}
    asio  asio.cpp:37 operator()

    {"len":16}
    p2p  stcp_socket.cpp:94 readsome message_oriented_connection.cpp:182
20141002T130221.517624 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":"20141002T130221.517429"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nOperation canceled \n    {\"message\":\"Operation canceled\"}\n    asio  asio.cpp:37 operator()\n\n    {\"len\":16}\n    p2p  stcp_socket.cpp:94 readsome"}}]} message_oriented_connection.cpp:274
20141002T130221.517714 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":"20141002T130221.517429"},"format":"disconnected: ${e}","data":{"e":"0 exception: unspecified\nOperation canceled \n    {\"message\":\"Operation canceled\"}\n    asio  asio.cpp:37 operator()\n\n    {\"len\":16}\n    p2p  stcp_socket.cpp:94 readsome"}}]} message_oriented_connection.cpp:274
20141002T130222.472185 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130235.641888 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130239.603366 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 721710us, longer than our target maximum of 500ms node.cpp:325
20141002T130239.603439 p2p:message read_loop ~call_statistics_col ] Actual execution took 6us, with a 234391us delay before the delegate thread started executing the method, and a 487313us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130239.957645 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1310667us, longer than our target maximum of 500ms node.cpp:325
20141002T130239.957739 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 469099us delay before the delegate thread started executing the method, and a 841564us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130239.961153 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1078444us, longer than our target maximum of 500ms node.cpp:325
20141002T130239.961193 p2p:message read_loop ~call_statistics_col ] Actual execution took 3us, with a 233396us delay before the delegate thread started executing the method, and a 845045us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130248.851634 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130301.919106 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130303.604058 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_synopsis took 593311us, longer than our target maximum of 500ms node.cpp:325
20141002T130303.604149 p2p:message read_loop ~call_statistics_col ] Actual execution took 8us, with a 228908us delay before the delegate thread started executing the method, and a 364395us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130307.517473 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 598848us, longer than our target maximum of 500ms node.cpp:325
20141002T130307.517548 p2p:message read_loop ~call_statistics_col ] Actual execution took 6us, with a 114313us delay before the delegate thread started executing the method, and a 484529us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130307.993191 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1078129us, longer than our target maximum of 500ms node.cpp:325
20141002T130307.993263 p2p:message read_loop ~call_statistics_col ] Actual execution took 5us, with a 117901us delay before the delegate thread started executing the method, and a 960223us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130308.000349 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1086240us, longer than our target maximum of 500ms node.cpp:325
20141002T130308.000403 p2p:message read_loop ~call_statistics_col ] Actual execution took 5us, with a 118838us delay before the delegate thread started executing the method, and a 967397us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130308.353182 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1434050us, longer than our target maximum of 500ms node.cpp:325
20141002T130308.353255 p2p:message read_loop ~call_statistics_col ] Actual execution took 5us, with a 113869us delay before the delegate thread started executing the method, and a 1320176us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130314.919330 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130328.013531 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130341.093474 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130354.102885 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130407.911250 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130420.911469 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130431.357727 p2p:message read_loop            read_loop ] disconnected 11 eof_exception: End Of File
End of file
    {"message":"End of file"}
    asio  asio.cpp:35 operator()

    {"len":16}
    p2p  stcp_socket.cpp:94 readsome message_oriented_connection.cpp:177
20141002T130433.979763 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130447.064326 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130500.224201 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130513.305901 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130526.306273 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130539.461313 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130543.312503 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 601010us, longer than our target maximum of 500ms node.cpp:325
20141002T130543.312587 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 236479us delay before the delegate thread started executing the method, and a 364527us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130543.549222 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 842417us, longer than our target maximum of 500ms node.cpp:325
20141002T130543.549294 p2p:message read_loop ~call_statistics_col ] Actual execution took 5us, with a 235857us delay before the delegate thread started executing the method, and a 606555us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130543.782593 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1079636us, longer than our target maximum of 500ms node.cpp:325
20141002T130543.782664 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 239672us delay before the delegate thread started executing the method, and a 839960us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130543.905264 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::sync_status took 1195870us, longer than our target maximum of 500ms node.cpp:325
20141002T130543.905330 p2p:message read_loop ~call_statistics_col ] Actual execution took 5us, with a 233199us delay before the delegate thread started executing the method, and a 962666us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130544.028671 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1323721us, longer than our target maximum of 500ms node.cpp:325
20141002T130544.028742 p2p:message read_loop ~call_statistics_col ] Actual execution took 5us, with a 237665us delay before the delegate thread started executing the method, and a 1086051us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130544.384023 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::sync_status took 1674542us, longer than our target maximum of 500ms node.cpp:325
20141002T130544.384094 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 233125us delay before the delegate thread started executing the method, and a 1441413us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130544.509254 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1800775us, longer than our target maximum of 500ms node.cpp:325
20141002T130544.509326 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 234171us delay before the delegate thread started executing the method, and a 1566600us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130552.765883 th_a:rebroadcast_pending rebroadcast_pending_ ]  rebroadcasting... client.cpp:1102
20141002T130554.936176 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 718539us, longer than our target maximum of 500ms node.cpp:325
20141002T130554.936250 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 112592us delay before the delegate thread started executing the method, and a 605943us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130555.649384 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1432421us, longer than our target maximum of 500ms node.cpp:325
20141002T130555.649458 p2p:message read_loop ~call_statistics_col ] Actual execution took 3us, with a 113233us delay before the delegate thread started executing the method, and a 1319185us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130555.892557 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1677065us, longer than our target maximum of 500ms node.cpp:325
20141002T130555.892629 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 114725us delay before the delegate thread started executing the method, and a 1562336us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130556.133611 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 1917302us, longer than our target maximum of 500ms node.cpp:325
20141002T130556.133682 p2p:message read_loop ~call_statistics_col ] Actual execution took 4us, with a 113931us delay before the delegate thread started executing the method, and a 1803367us delay after it finished before the p2p thread started processing the response node.cpp:330
20141002T130556.259397 p2p:message read_loop ~call_statistics_col ] Call to method node_delegate::get_blockchain_now took 2040895us, longer than our target maximum of 500ms node.cpp:325
20141002T130556.259468 p2p:message read_loop ~call_statistics_col ] Actual execution took 6us, with a 111669us delay before the delegate thread started executing the method, and a 1929220us delay after it finished before the p2p thread started processing the response

Both blockchain.log & rpc.log are empty.

Can someone determine the problem from these logs? I'm not sure what to make of them.

Thanks.

-F

7
Technical Support / How to have separate wallets with 1 account each
« on: September 28, 2014, 02:35:25 pm »
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

8
Technical Support / How to profit from Music DAC Snapshot
« on: September 27, 2014, 09:52:01 pm »
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

9
Technical Support / How to monitor seed node with Zabbix
« on: September 26, 2014, 11:23:56 pm »
Hi,

I'm running Zabbix for server monitoring, & would like to know how I can monitor the 'bitshares-cli' daemon with it.

Is it possible to create a template which reports the number of connections it's got, & the traffic on each?

Please advise.

Thanks,
-F

10
Technical Support / Problems with BitSharesX daemon initscripting
« on: September 22, 2014, 04:43:56 am »
Hi,

When I try to start the client in daemon mode using:
Code: [Select]
$BitSharesX --daemonI get the following error:
Code: [Select]
QXcbConnection: Could not connect to display
Aborted

Of course it happens without the --daemon flag as well, but I expect that as XOrg isn't installed.

OS is Debian Wheezy, client is installed via Ubuntu ppa, using Debian Sid dependencies.

How do I get past this?

Please advise.

Thanks,
-F

11
Technical Support / Renaming accounts
« on: September 19, 2014, 08:22:57 am »
Hi,

I'd like to know if when I change the name on my account, it changes everywhere in the system, or if it only changes the label in the client?

Would I be better off starting a new account with the new name, so that it's created properly with the new name?

Please advise.

Thanks,
-F

12
Technical Support / Make an old account a sub-account of a new account?
« on: September 18, 2014, 03:24:50 pm »
Hi,

In my infinite wisdom being new to this, I created an account on my desktop box as a delegate. Now I learn that delegate accounts are best as sub-accounts of a main account.

So my question is: Is it possible for me to create a new, non-delegate account, & set the delegate account as a sub-account of the new account? And if so, how?

If not, what are the pros & cons of running as a delegate on an entirely separate account?

Please advise.

Thanks,
-F

13
Hi,

I read that currently there's an issue with restoring wallet backups which contain more than 1 account, & thus I'm holding off on creating additional accounts & sticking to my primary project alone. But I do see the advantage to having more than 1, & would like to do so as soon as the aforementioned issue is ironed out.

Where can I monitor the project's development so I can get an idea as to when I can both have multiple accounts, & know my wallet is safely backed up such that it can be properly restored to its original state should a recovery be necessary?

Another question which comes to mind is, if I were to create additional accounts with a separate wallet for each now while it's impossible to properly restore wallets containing multiple accounts, would it be possible to one day consolidate those accounts into a single wallet file once the backup restoration issue is resolved?

Lastly, should it be the case that this problem isn't a priority with the development team, is there a way to maybe vote for which todo items get proiritized? I imagine I could post a bounty to get it completed by foo date if it's on the back burner, but if it's going to be fixed within a reasonable amount of time anyway, I'd rather save my BTSX/PTS.

-F

14
General Discussion / I want to run a seed node
« on: September 17, 2014, 05:46:52 am »
Hi,

In the near future, I'll have 2 servers each with their own static IP address, unused CPU cycles, & plenty of bandwidth. I would like to help the network by running a seed node on each.

I'm not clear on whether just running the bitsharesx client constitutes a seed node. I gather that it's separate from a delegate node, & can be helpful without having to be voted into the top 101.

What software would I have to install, & where can I find a download link with installation instructions?

One server runs Debian, & the other will run Lunar linux, so I'll need to build them from source. I assume that's available.

If it's the same software as a delegate node requires, I'll need some help, as I'm having trouble building it, but that's for another thread that's over in 'Technical Support'.

If someone would be kind enough to point me in the right direction, I'm happy to help the project this way.

Thanks,
-F

EDIT:
An afterthought, I probably should have posted this in the 'Newbies' section- sorry. Please feel free to move it should forum admins agree.

15
Hi,

Most every time my Acronis TrueImage backup starts every night, it completely freezes my computer & requires me to press & hold the power button to shut it down & restart it. It only happens if the BitSharesX client is running when the backup starts.

I can have Acronis run a batch file before the task starts, & I'd like to know how to close the client that way so this doesn't keep happening.

Is there a command to shut it down cleanly?

Please advise.

Thanks,
-F

Pages: [1] 2