Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

Why dashnode or insight sometimes is down

Discussion in 'Development Tech Discussion' started by Skrutch, Jan 14, 2018.

Tags:
  1. Skrutch

    Skrutch Guest

    Hello all, please help me 1 month more can't correctly up Dash node.

    OS: Debian 9.3 (x86_64)
    Install step-by-step https://dashpay.atlassian.net/wiki/spaces/DOC/pages/86278560/Installation+Configuration

    Code:
    [email protected]:~/.bitcore/data# netstat -tunlpn
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
    tcp        0      0 0.0.0.0:9999            0.0.0.0:*               LISTEN      3536/dashd
    tcp        0      0 127.0.0.1:28332         0.0.0.0:*               LISTEN      3536/dashd
    tcp6       0      0 :::9998                 :::*                    LISTEN      3536/dashd
    tcp6       0      0 :::9999                 :::*                    LISTEN      3536/dashd
    tcp6       0      0 :::3001                 :::*                    LISTEN      3523/bitcore
    tcp6       0      0 :::2468                 :::*                    LISTEN      622/sshd
    Here I see 9999 is Dashnode port and 9998 I think is RPC port, everythink is ok?

    Unit process debug
    Code:
    More than one instance of bitcore-lib found. Please make sure that you are not mixing instances of classes of the different versions of bitcore.
    More than one instance of bitcore-lib found. Please make sure that you are not mixing instances of classes of the different versions of bitcore.
    [2018-01-14T15:25:25.228Z] warn: Stopping existing spawned dash process with pid: 3536
    [2018-01-14T15:25:25.229Z] warn: Unclean dash process shutdown, process not found with pid: 3536
    [2018-01-14T15:25:30.241Z] warn: Loading governance cache...
    [2018-01-14T15:25:35.751Z] warn: ZMQ connection delay: tcp://127.0.0.1:28332
    Why I this is warning about bitcore-lib?

    Network is: livenet
    Sync Status: 100%

    dashd.conf
    Code:
    listen=1
    server=1
    whitelist=127.0.0.1
    txindex=1
    addressindex=1
    timestampindex=1
    spentindex=1
    zmqpubrawtx=tcp://127.0.0.1:28332
    zmqpubrawtxlock=tcp://127.0.0.1:28332
    zmqpubhashblock=tcp://127.0.0.1:28332
    rpcallowip=127.0.0.1
    rpcport=9998
    rpcuser=dash
    rpcpassword=local321
    uacomment=bitcore
    debug=1
    Thanks.

    P.S. I see interesting moments, if I try to send RPC command, and RPC connection is incorrect port after ~5 min. Dash is down.
    And netstat -tunlpn is not changes. Core is work, because address is gen, so just insight is down?
    Also didn't think my unit process problem, because I see again just warning.
     
    #1 Skrutch, Jan 14, 2018
    Last edited by a moderator: Jan 14, 2018
  2. moocowmoo

    moocowmoo Bovine Bit-flipper
    Foundation Member

    Joined:
    Jun 15, 2014
    Messages:
    483
    Likes Received:
    603
    Trophy Points:
    263
    Dash Address:
    XmoocowYfrPKUR6p6M5aJZdVntQe71irCX
    If dash is up, then down. Check free ram and swap. Sounds like it's running out of memory, but I'm just guessing.

    What does
    Code:
    free -m
    output show?
     
  3. Skrutch

    Skrutch Guest

    RAM is good
    What warning about bitcore-lib?