Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies  (Read 603 times)

0 Members and 1 Guest are viewing this topic.

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
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

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12242
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #1 on: October 09, 2014, 11:25:14 AM »
1) why are you keeping the config.json? there is nothing of value in it! .. the folder "wallet" is valuable and you should always make a backup of it (or use the inapp backup function)
2) could you run the client in "gdb" so that you get a backtrace once the client crashes?
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #2 on: October 09, 2014, 12:25:01 PM »
2) could you run the client in "gdb" so that you get a backtrace once the client crashes?

What's the right way to do that?

When I do:
Code: [Select]
$sudo gdb bitshares_client --daemon...gdb complains about the unrecognized --daemon flag.

And when I do:
Code: [Select]
$sudo gdb 'bitshares_client --daemon'...It doesn't start.

Am I starting it wrong maybe?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12242
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #3 on: October 09, 2014, 12:26:30 PM »
2) could you run the client in "gdb" so that you get a backtrace once the client crashes?

What's the right way to do that?

When I do:
Code: [Select]
$sudo gdb bitshares_client --daemon...gdb complains about the unrecognized --daemon flag.

And when I do:
Code: [Select]
$sudo gdb 'bitshares_client --daemon'...It doesn't start.

Am I starting it wrong maybe?

just leave the daemon flag away ..


if there is a promt and nothing happening type "run"
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #4 on: October 09, 2014, 12:31:10 PM »
I get this from gdb:

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

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12242
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #5 on: October 09, 2014, 12:35:11 PM »
I get this from gdb:

Code: [Select]
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.
oh ... your bitshares client is "stripped" .. no debug information in it .. so that want work .. you compiled it your self?
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #6 on: October 09, 2014, 12:43:11 PM »
No, it's from the Ubuntu ppa.

Give me some time & I'll try the one from git so it'll debug.

----

I keep the config.json because I was under the impression I needed the rpc configuration set to run as a seed node. Is this not correct?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12242
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #7 on: October 09, 2014, 01:56:50 PM »
No, it's from the Ubuntu ppa.

Give me some time & I'll try the one from git so it'll debug.
https://github.com/dacsunlimited/bitsharesx/blob/master/BUILD_UBUNTU.md

Quote
I keep the config.json because I was under the impression I needed the rpc configuration set to run as a seed node. Is this not correct?
nop .. no rpc required for seed nodes .. just a running node on the default (optional) port
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #8 on: October 09, 2014, 02:29:46 PM »
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:

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

Offline dannotestein

Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #9 on: October 09, 2014, 02:44:32 PM »
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:

Code: [Select]
Reading symbols from /home/ubuntu/BitSharesX/bitshares_toolkit/programs/client/bitshares_client...done.
(gdb)

Have you typed "run" in gdb to start the process yet?
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #10 on: October 09, 2014, 02:45:29 PM »
I'm running the PPA binary on a few machines, and haven't seen this yet. You said it "still" won't stay running, did it ever work before (a different version maybe?) Do you have any other PPAs enabled? It looks like it's crashing when trying to connect to a peer, maybe one of the networking libraries is from a different PPA?
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #11 on: October 09, 2014, 03:34:43 PM »
I'm running the PPA binary on a few machines, and haven't seen this yet. You said it "still" won't stay running, did it ever work before (a different version maybe?) Do you have any other PPAs enabled? It looks like it's crashing when trying to connect to a peer, maybe one of the networking libraries is from a different PPA?
Got it to run by typing 'run'. I didn't know that needed to happen.

30 minutes or so now & it's still up, so I'm thinking you might be right about the ppa issue with libraries or something. It _did_ run back at version 0.4.18- started crashing at 0.4.19. Back then I was using kernel x-29 & I don't know if that since yesterday I'm at x-37 now that might be why. I'll test that soon.

If I have further issues, I'll just keep using github's version since it isn't crashing.

Just a s3fs-fuse ppa enabled by the way.
« Last Edit: October 09, 2014, 03:37:47 PM by FuLl »

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #12 on: October 09, 2014, 03:41:27 PM »
It just crashed using the github version. This is the output from gdb:

Code: [Select]
(wallet closed) >>> [Thread 0x7fffd0ff9700 (LWP 6502) exited]
[Thread 0x7fffd17fa700 (LWP 6501) exited]
[Thread 0x7fffd1ffb700 (LWP 6500) exited]
[Thread 0x7fffd27fc700 (LWP 6499) exited]
[Thread 0x7fffd2ffd700 (LWP 6498) exited]
[Thread 0x7fffd37fe700 (LWP 6497) exited]
[Thread 0x7fffd3fff700 (LWP 6496) exited]
[Thread 0x7fffe48f0700 (LWP 6495) exited]
[Thread 0x7fffe50f1700 (LWP 6494) exited]
[Thread 0x7fffe60ea700 (LWP 6493) exited]
[Thread 0x7fffe6ffd700 (LWP 6492) exited]
[Thread 0x7fffe77fe700 (LWP 6491) exited]
[Thread 0x7fffe7fff700 (LWP 6490) exited]
[Thread 0x7ffff4bc8700 (LWP 6489) exited]
[Thread 0x7ffff53c9700 (LWP 6488) exited]
[Thread 0x7ffff5bca700 (LWP 6487) exited]
[Thread 0x7ffff63cb700 (LWP 6486) exited]
Program terminated with signal SIGKILL, Killed.
The program no longer exists.

I didn't do that.

How do I get something useful to report for debugging?

Offline dannotestein

Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #13 on: October 09, 2014, 03:53:49 PM »
It just crashed using the github version. This is the output from gdb:

Code: [Select]
(wallet closed) >>> [Thread 0x7fffd0ff9700 (LWP 6502) exited]
[Thread 0x7fffd17fa700 (LWP 6501) exited]
[Thread 0x7fffd1ffb700 (LWP 6500) exited]
[Thread 0x7fffd27fc700 (LWP 6499) exited]
[Thread 0x7fffd2ffd700 (LWP 6498) exited]
[Thread 0x7fffd37fe700 (LWP 6497) exited]
[Thread 0x7fffd3fff700 (LWP 6496) exited]
[Thread 0x7fffe48f0700 (LWP 6495) exited]
[Thread 0x7fffe50f1700 (LWP 6494) exited]
[Thread 0x7fffe60ea700 (LWP 6493) exited]
[Thread 0x7fffe6ffd700 (LWP 6492) exited]
[Thread 0x7fffe77fe700 (LWP 6491) exited]
[Thread 0x7fffe7fff700 (LWP 6490) exited]
[Thread 0x7ffff4bc8700 (LWP 6489) exited]
[Thread 0x7ffff53c9700 (LWP 6488) exited]
[Thread 0x7ffff5bca700 (LWP 6487) exited]
[Thread 0x7ffff63cb700 (LWP 6486) exited]
Program terminated with signal SIGKILL, Killed.
The program no longer exists.

I didn't do that.

How do I get something useful to report for debugging?
Apparently the program was killed somehow, so you won't be able to get a backtrace.

I looked at your p2p log, looks like normal messages there (message about disconnections are quite common and destroying peer connection objects for those connection is normal behavior). The underlying fc library used by bitsharesx client throws exceptions to indicate a socket has been closed by the peer you're communicating with.

The interesting question is how the program was killed, maybe you're hitting a ulimit on your system that is terminating the client. Can you type "ulimit -a" and post the output of that command?
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline FuLl

  • Full Member
  • ***
  • Posts: 96
    • View Profile
Re: bitsharesx-cli v. 0.4.20+a-0ubuntu1~ppa5 process dies
« Reply #14 on: October 09, 2014, 03:56:08 PM »
Code: [Select]
ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 4523
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 4523
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

 

Google+