clightning uses all my resources, ... till I have to shutdown!

clightning uses all my resources, ... till I have to shutdown!

clightning runs for a while great. However, every second day the computer locks up,

I use docker-compose for that:

version: "3"
services:
  bitcoind:
    image: nicolasdorier/docker-bitcoin:0.16.3
    container_name: bitcoind
    environment:
      BITCOIN_EXTRA_ARGS: |
        testnet=0
        whitelist=0.0.0.0/0
        server=1
        rpcuser=*****
        rpcpassword=*****
    expose:
      - "8333"
    ports:
      - "0.0.0.0:8333:8333"
    volumes:
      - "/media/ronald/data/scratch/bitcoin/mainnet/bitcoind:/data"

  clightning_bitcoin:
    image: elementsproject/lightningd
    container_name: lightning
    command:
      - --bitcoin-rpcconnect=bitcoind
      - --bitcoin-rpcuser=****
      - --bitcoin-rpcpassword=****
      - --network=bitcoin
      - --alias=TWronald✅
      - --rgb=15C315
      - --log-level=debug
      - --announce-addr=220.133.223.206:9735
      - --bind-addr=0.0.0.0:9735
    environment:
      EXPOSE_TCP: "true"
    expose:
      - "9735"
    ports:
      - "0.0.0.0:9735:9735"
    volumes:
      - "/media/ronald/data/scratch/bitcoin/mainnet/clightning:/root/.lightning"
      - "/media/ronald/data/scratch/bitcoin/mainnet/bitcoind:/etc/bitcoin"
    links:
      - bitcoind

lightning-cli getinfo

{
  "id": "035aef5661e1a6e370db60dc0455796800afd5b51fbc12a0a8b34836b15f5d7ef6", 
  "alias": "TWronald✅", 
  "color": "15c315", 
  "num_peers": 15, 
  "num_pending_channels": 0, 
  "num_active_channels": 15, 
  "num_inactive_channels": 0, 
  "address": [
    {
      "type": "ipv4", 
      "address": "220.133.223.206", 
      "port": 9735
    }
  ], 
  "binding": [
    {
      "type": "ipv4", 
      "address": "0.0.0.0", 
      "port": 9735
    }
  ], 
  "version": "", 
  "blockheight": 560987, 
  "network": "bitcoin", 
  "msatoshi_fees_collected": 0
}

Why the version of lightning is "" ??? scratch/bitcoin/mainet/clightning/config is empty.

Currently it is running fine. ps ax |grep lightn

 7278 ?        S      0:03 /usr/bin/lightning_channeld
 8524 pts/20   S+     0:00 grep --color=auto lightn
16579 ?        S      0:06 /usr/bin/lightning_channeld
31660 ?        S      1:19 lightningd --bitcoin-rpcconnect=bitcoind --bitcoin-rpcuser=**** --bitcoin-rpcpassword=**** --network=bitcoin --alias=TWronald✅ --rgb=15C315 --log-level=debug --announce-addr=220.133.223.206:9735 --bind-addr=0.0.0.0:9735
31665 ?        Z      0:00 [lightning_chann] <defunct>
31666 ?        Z      0:00 [lightning_closi] <defunct>
31667 ?        Z      0:00 [lightning_conne] <defunct>
31668 ?        Z      0:00 [lightning_gossi] <defunct>
31669 ?        Z      0:00 [lightning_hsmd] <defunct>
31670 ?        Z      0:00 [lightning_oncha] <defunct>
31671 ?        Z      0:00 [lightning_openi] <defunct>
31675 ?        S      0:00 /usr/bin/lightning_hsmd
31677 ?        S      0:00 /usr/bin/lightning_connectd
31678 ?        S      5:45 /usr/bin/lightning_gossipd
31862 ?        S      0:00 socat TCP4-listen:9835,fork,reuseaddr UNIX-CONNECT:/root/.lightning/lightning-rpc
31868 ?        S      0:06 /usr/bin/lightning_channeld
31869 ?        S      0:09 /usr/bin/lightning_channeld
31870 ?        S      0:06 /usr/bin/lightning_channeld
31871 ?        S      0:07 /usr/bin/lightning_channeld
31872 ?        S      0:07 /usr/bin/lightning_channeld
31874 ?        S      0:10 /usr/bin/lightning_channeld
31875 ?        S      0:10 /usr/bin/lightning_channeld
31876 ?        S      0:06 /usr/bin/lightning_channeld
31879 ?        S      0:10 /usr/bin/lightning_channeld
31988 ?        S      0:06 /usr/bin/lightning_channeld
31989 ?        S      0:06 /usr/bin/lightning_channeld
31992 ?        S      0:07 /usr/bin/lightning_channeld

... but still some Zombies.

When it grinds to a hold, it uses most with gossip.

Can you spot some changes I should make to improve my system?

http://bit.ly/2WAM6aj

Comments

Post a Comment

Popular posts from this blog

The Importance Of Owning Crypto

Image
The Importance Of Owning Crypto 😀 Thank You For Watching! :D 🚩 Remember to subscribe and hit the bell "🔔" icon! ►Need certified & professional help with your crypto taxes? Taxbit is here to help! Use this link to receive 10% off of their services: https://ift.tt/2GUy4uv ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SUPPORT THE CHANNEL ► Patreon Sponsors (Private Telegram Group) - https://goo.gl/vpX5sW ► YouTube Sponsors - https://www.youtube.com/channel/UCdUSSt-IEUg2eq46rD7lu_g/join -~-~~-~~~-~~-~- 💓Crypto Donations Are Really Appreciated!💓 💎►Donate Ether and Ethereum-Based Tokens: 0x1466032B4F0F13910DA35B16371807428CB40714 💎►Donate Bitcoin: 3JKQycXHdD5yqSRTf5VabM28Ff9AfXYcJD 💎►Donate Bitcoin Cash: qrsq45lsrumctyu98mgjgc0qjaleng2jdgau3qz90x 💎►Donate Dash Xn1sUfFDkZAwArJ6mtJUYVLndnmXctxA1L 💎►Donate Monero 463EDu2cqU4ASxLVVKYkVMbk1Nz6TQyy9Wt8b3D5CdJjZh9JukZNGUyLvbJnXoJNRXTN98cSpLSRVN2bYoDTmsxkJSUKtmy 💎►Donate Using Paypal: https://goo.gl/7m1X4Z -~-~~-~~~-~~-~- MUS...
Read more

Activation of SegWit v1

Activation of SegWit v1 The segregated witness soft fork of August 2017 included a versioning field which would allow for future incrementation. Anthony Towns has recently posted an early draft of the proposal for the SegWit v1 upgrade to the mailing list . Although the devil is of course in the details, how could such an upgrade process look like? What are the different upgrade mechanism for the major [v1 - v16] and minor [v1.0 - v1.127] version changes? How is the soft fork signaled? How is the consensus change enforced? Is the v1 change as "contentious" and time consuming as v0 was? What are the tasks of node operators and miners? Thank you in advance for the answer! https://ift.tt/2VrPDpG
Read more

Nonce usage in ECDSA signing algorithm

Nonce usage in ECDSA signing algorithm I'm trying to understand the signing function secp256k1_ecdsa_sig_sign(), and I'm curious about the nonce usage here. static int secp256k1_ecdsa_sig_sign(const secp256k1_ecmult_gen_context *ctx, secp256k1_scalar *sigr, secp256k1_scalar *sigs, const secp256k1_scalar *seckey, const secp256k1_scalar *message, const secp256k1_scalar *nonce, int *recid) { unsigned char b[32]; secp256k1_gej rp; secp256k1_ge r; secp256k1_scalar n; int overflow = 0; secp256k1_ecmult_gen(ctx, &rp, nonce); secp256k1_ge_set_gej(&r, &rp); secp256k1_fe_normalize(&r.x); secp256k1_fe_normalize(&r.y); secp256k1_fe_get_b32(b, &r.x); secp256k1_scalar_set_b32(sigr, b, &overflow); /* These two conditions should be checked before calling */ VERIFY_CHECK(!secp256k1_scalar_is_zero(sigr)); VERIFY_CHECK(overflow == 0); if (recid) { /* The overflow condition is cryptographically unreachable as hitting it requires f...
Read more