bitcore Bitcore Node connects/disconnects error to LTC node

I get these endless messages

{"message":"2021-10-14 21:07:39.152 UTC | Connected to peer: 172.31.22.93:19333 | Chain: LTC | Network: mainnet","level":"info"}
{"message":"2021-10-14 21:08:09.155 UTC | Not connected to peer: 172.31.22.93:19333 | Chain: LTC | Network: mainnet","level":"warn"}

$ nvm use v8.17.0 
Now using node v8.17.0 (npm v6.13.4)

$ cat bitcore.config.json 
{
  "bitcoreNode": {
    "modules": ["./litecoin"],
    "services": {
      "api": {
        "wallets": {
          "allowCreationBeforeCompleteSync": true
        }
      }
    },
    "chains": {
      "LTC": {
        "mainnet": {
          "chainSource": "p2p",
          "trustedPeers": [
            {
              "host": "172.31.22.93",
              "port": 19333
            }
          ],
          "rpc": {
            "host": "172.31.22.93",
            "port": 19333,
            "username": "<user>",
            "password": "<pass>"
          }
        }
      }
    }
  }
}

# cat /home/litecoin/.litecoin/litecoin.conf                                                                                                                                                                               
 # litecoin.conf configuration file. Lines beginning with # are comments.                                                                                                                                                                     
                                                                                                                                                                                                                                              
                                                                                                                                                                                                                                              
 # Network-related settings:                                                                                                                                                                                                                  
                                                                                                                                                                                                                                              
 # Run on the test network instead of the real litecoin network.                                                                                                                                                                              
 #testnet=1                                                                                                                                                                                                                                   
                                                                                                                                                                                                                                              
 # Connect via a socks4 proxy                                                                                                                                                                                                                 
 #proxy=127.0.0.1:9050                                                                                                 
                                                                                                                       
 ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##            
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##        
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##    
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
  
 # Use as many addnode= settings as you like to connect to specific peers
 #addnode=69.164.218.197
 #addnode=10.0.0.2:9333
                                                                                                                       
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=10.0.0.1:9333
                                                                                                                      
  
 # Maximum number of inbound+outbound connections.
 #maxconnections=
  
  
 # JSON-RPC options (for controlling a running Litecoin/litecoind process)
  
 # server=1 tells Litecoin-QT to accept JSON-RPC commands.
 server=1
  
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=<user>
 rpcpassword=<pass>
  
 # How many seconds litecoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established. 
 #rpctimeout=30
  
 # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character). 
 # NOTE: opening up the RPC port to hosts outside your local
 # trusted network is NOT RECOMMENDED, because the rpcpassword
 # is transmitted over the network unencrypted.
 rpcallowip=0.0.0.0/0
 #rpcallowip=192.168.1.*
  
 # Listen for RPC connections on this TCP port:
 rpcport=19333
  
 # You can use Litecoin or litecoind to send commands to Litecoin/litecoind
 # running on another host using this option:
 #rpcconnect=127.0.0.1
  
 # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Litecoin -server or litecoind
 #rpcssl=1
  
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
  
  
 # Miscellaneous options
  
 # Set gen=1 to attempt to generate litecoins
 #gen=0
   
 # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 #keypool=100
  
 # Pay an optional transaction fee every time you send litecoins.  Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
  
 # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
  
 # Allows litecoind to operate with the BDB wallet disabled.
 #disablewallet=1
  
 # User interface options
  
 # Start Litecoin minimized
 #min=1
  
 # Minimize to the system tray
 #minimizetotray=1
txindex=1
zmqpubrawblock=tcp://0.0.0.0:29000 
zmqpubrawtx=tcp://0.0.0.0:29000 
zmqpubhashtx=tcp://0.0.0.0:29000 
zmqpubhashblock=tcp://0.0.0.0:29000