Help - Peer Connection Stability

lnd 0.5.2-beta commit=v0.5.2-beta

bitcoin version v0.17.1 (release build)

running on a pi using the Raspibolt guide by Stadicus

​

INTRO:

Hello! I am having problems staying connecting with peers that I have channels open with. I am using this script to check on my channels. Learning to balance them right now, and would really like to get these problematic channels closed. Link to script made by RobClark56

​

EXPECTED RESULT:

Channels will stay "active" with peers that appear online. I am be able to reconnect to online peers that I have already established a channel with in the past.

​

ACTUAL RESULT:

After some time, even though peers show as online (on 1ml or using lncli), the channel begins to show as inactive. I am able to reconnect to a few peers using "lncli connect" or reboot. Others only stay connected temporarily, and some peers I cannot reesatblish connection with at all.

​

QUESTIONS:

1) Should I use " lncli connect pubkey@host:port " to reestablish a connection to peers? I have tried this with some success and some failure. Some peers will only reconnect for a short amount of time before their channels show as inactive with me once again.

2) Why can't I "lncli connect" with peers that show as online at 1ml.com, and that I have a channel open with?

​

ERRORS:

Anytime that I monitor my channels I notice these 3 are consistently showing inactive.

Area51, Kevenboo [LND], and reckless.coffee

Here is the output of trying to connect to these problematic peers/nodes

Area51 $ lncli connect 022c203796a43cb7cf69ddb1738b9f91a3285595581f093a339657512112bec8bf@znnlwvn7z7pj3sl5q4x7cwchkraoswq3r3n4bn66sxemavkcd7kdnwad.onion:9735 Mar 09 20:02:12 raspicat lnd[993]: 2019-03-09 20:02:12.639 [WRN] SRVR: Already have 1 persistent connection requests for 022c203796a43cb7cf69ddb1738b9f91a3285595581f093a339657512112bec8bf@znnlwvn7z7pj3sl5q4x7cwchkraoswq3r3n4bn66sxemavkcd7kdnwad.onion:9735, connecting anyway. Mar 09 20:02:24 raspicat lnd[993]: 2019-03-09 20:02:24.529 [ERR] SRVR: Unable to connect to 022c203796a43cb7cf69ddb1738b9f91a3285595581f093a339657512112bec8bf@znnlwvn7z7pj3sl5q4x7cwchkraoswq3r3n4bn66sxemavkcd7kdnwad.onion:9735: socks connect tcp 127.0.0.1:9050->znnlwvn7z7pj3sl5q4x7cwchkraoswq3r3n4bn66sxemavkcd7kdnwad.onion:9735: unknown error host unreachable Mar 09 20:02:24 raspicat lnd[993]: 2019-03-09 20:02:24.530 [ERR] RPCS: [connectpeer]: error connecting to peer: socks connect tcp 127.0.0.1:9050->znnlwvn7z7pj3sl5q4x7cwchkraoswq3r3n4bn66sxemavkcd7kdnwad.onion:9735: unknown error host unreachable

Kevenboo [LND] $ lncli connect 031e691f3704bfb31b7bb74a98d72c2c57ee4af98f2e7476d8f50e13061bcf1162@ugfpblkvdhpv2js3s7y4rmwtuefqshazjlw6uhb2cdwkzosjwmzasxyd.onion:9735 Mar 09 20:04:20 raspicat lnd[993]: 2019-03-09 20:04:20.156 [WRN] SRVR: Already have 1 persistent connection requests for 031e691f3704bfb31b7bb74a98d72c2c57ee4af98f2e7476d8f50e13061bcf1162@ugfpblkvdhpv2js3s7y4rmwtuefqshazjlw6uhb2cdwkzosjwmzasxyd.onion:9735, connecting anyway. Mar 09 20:04:33 raspicat lnd[993]: 2019-03-09 20:04:33.047 [ERR] SRVR: Unable to connect to 031e691f3704bfb31b7bb74a98d72c2c57ee4af98f2e7476d8f50e13061bcf1162@ugfpblkvdhpv2js3s7y4rmwtuefqshazjlw6uhb2cdwkzosjwmzasxyd.onion:9735: socks connect tcp 127.0.0.1:9050->ugfpblkvdhpv2js3s7y4rmwtuefqshazjlw6uhb2cdwkzosjwmzasxyd.onion:9735: unknown error host unreachable Mar 09 20:04:33 raspicat lnd[993]: 2019-03-09 20:04:33.047 [ERR] RPCS: [connectpeer]: error connecting to peer: socks connect tcp 127.0.0.1:9050->ugfpblkvdhpv2js3s7y4rmwtuefqshazjlw6uhb2cdwkzosjwmzasxyd.onion:9735: unknown error host unreachable

reckless.coffee $ lncli connect 0349fbcae322df983b6c74f65aadd1910544d2a8154a1a43a630b5a289aa3edad8@209.91.253.154:9735 Mar 09 20:05:53 raspicat lnd[993]: 2019-03-09 20:05:53.165 [WRN] SRVR: Already have 1 persistent connection requests for 0349fbcae322df983b6c74f65aadd1910544d2a8154a1a43a630b5a289aa3edad8@209.91.253.154:9735, connecting anyway. Mar 09 20:05:53 raspicat lnd[993]: 2019-03-09 20:05:53.993 [ERR] SRVR: Unable to connect to 0349fbcae322df983b6c74f65aadd1910544d2a8154a1a43a630b5a289aa3edad8@209.91.253.154:9735: socks connect tcp 127.0.0.1:9050->209.91.253.154:9735: unknown error connection refused Mar 09 20:05:53 raspicat lnd[993]: 2019-03-09 20:05:53.994 [ERR] RPCS: [connectpeer]: error connecting to peer: socks connect tcp 127.0.0.1:9050->209.91.253.154:9735: unknown error connection refused