subscribe-Connection dropped by remote peer

Questions
1 
    web3.eth.subscribe('logs',{address:"0x...",topics:"0x..."]},(error,result)=>{
        if(error){
           console.log(error)
           return
         }
        //do something here
    })

i subscribed with wss api,and it works well,but after 2 days ,a problem occurred

Error: CONNECTION ERROR: The connection got closed with the close code `1006` and the following reason string `Connection dropped by remote peer.`
    at Object.ConnectionError (/home/ec2-user/nodeCode/myProject/node_modules/web3-core-helpers/src/errors.js:72:23)
    at Object.ConnectionCloseError (/home/ec2-user/nodeCode/myProject/node_modules/web3-core-helpers/src/errors.js:55:25)
    at /home/ec2-user/nodeCode/myProject/node_modules/web3-core-requestmanager/src/index.js:128:50
    at Map.forEach (<anonymous>)
    at WebsocketProvider.close (/home/ec2-user/nodeCode/myProject/node_modules/web3-core-requestmanager/src/index.js:127:37)
    at WebsocketProvider.emit (/home/ec2-user/nodeCode/myProject/node_modules/web3-providers-ws/node_modules/eventemitter3/index.js:181:35)
    at WebsocketProvider._onClose (/home/ec2-user/nodeCode/myProject/node_modules/web3-providers-ws/src/index.js:179:10)
    at W3CWebSocket._dispatchEvent [as dispatchEvent] (/home/ec2-user/nodeCode/myProject/node_modules/yaeti/lib/EventTarget.js:115:12)
    at W3CWebSocket.onClose (/home/ec2-user/nodeCode/myProject/node_modules/websocket/lib/W3CWebSocket.js:228:10)
    at WebSocketConnection.<anonymous> (/home/ec2-user/nodeCode/myProject/node_modules/websocket/lib/W3CWebSocket.js:201:17)
    at WebSocketConnection.emit (events.js:314:20)
    at WebSocketConnection.handleSocketClose (/home/ec2-user/nodeCode/myProject/node_modules/websocket/lib/WebSocketConnection.js:389:14)
    at TLSSocket.emit (events.js:326:22)
    at net.js:673:12
    at TCP.done (_tls_wrap.js:564:7) {
  code: 1006,
  reason: 'Connection dropped by remote peer.'

is there anyway to solve this?or where can i catch this error to restart my service?

thanks

2

Have you tried either implementing reconnect logic in the event no messages are delivered based on your parameters or have a newHeads subtype on the connection? These may help manage that issue.

This thread has a good writeup of why you may be encountering the 1006 error.