# No-Response / Disconnect of DB2
**URL:** https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929
**Category:** Dashboard
**Tags:** docker, dashboard-2
**Created:** [1 August 2024 03:08 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929 "2024-08-01T03:08:39Z")
**Posts on this page:** 15
**Page:** 2
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [4 August 2024 10:12 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/21 "2024-08-04T10:12:23Z")
> [@xx\_Nexus\_xx](#):
>
> Could there be any issue with my websocket config or network setup for Node-Red. As said my system is
No, that one is normal. You can see that it has a response code of 101 which means that it was an http(s) connection upgraded to ws(s) which is correct. Once that happens, the connection stays open for comms.
What you are looking for are either odd long gaps or oddly long responses in the timings of the other various resources being loaded.
If you look at the summary, I can see that the main page is taking around 2s to fully load. Which is reasonably long. There should also be a summary showing the overall stats:
> [@xx\_Nexus\_xx](#):
>
> Could there be any issue with my websocket config or network setup for Node-Red
I think there is indeed a problem. But I can't tell whether it is network or device problem. You appear to either have 5 connected clients there or the timeouts are causing [Socket.IO](http://Socket.IO) to re-connect the single client with new socket id's (which I think is more likely).
You should never really be getting [socket.io](http://socket.io) ping timeouts. It shows that either the [socket.io](http://socket.io) server or the network cannot deal with the traffic. You might legitimately get transport errors if the client device or browser tab goes to sleep since that will make the client go away temporarily. When it wakes up, it will re-connect with a new socket id.
> [@xx\_Nexus\_xx](#):
>
> over time (~2 days) the system becomes worse with the UI and I need to restart the docker container
Which implies a memory leak probably. The server seems more than powerful enough, it is more powerful than my home server. Though you could try temporarily turning off the unifi controller if that is what you have running. That shouldn't affect your WiFi.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [4 August 2024 10:15 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/22 "2024-08-04T10:15:47Z")
What is `catcher.js`? I don't see that on my example D2 page. It appears to be controlling the websocket. It is triggered from `injector.js` which I also don't see.
Please check what those js resources are and what they are doing.
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [4 August 2024 23:59 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/23 "2024-08-04T23:59:15Z")
> [@TotallyInformation](#):
>
> You should never really be getting [socket.io](http://socket.io) ping timeouts. It shows that either the [socket.io](http://socket.io) server or the network cannot deal with the traffic.
How can I influence or configure the [socket.io](http://socket.io) server as my (1GB) network is having lots of available capacity (I easily can stream several 4k videos at same time) and have as well done test with OpenSpeedTest and other bandwith tools.
> [@TotallyInformation](#):
>
> I think there is indeed a problem. But I can't tell whether it is network or device problem. You appear to either have 5 connected clients there or the timeouts are causing [Socket.IO](http://Socket.IO) to re-connect the single client with new socket id's (which I think is more likely).
I'm currently only running 1 browser to connect to this NR docker container and it is 1GB wired setup (no wifi) and dont understand why there should be 5 connects, so yes I think my single client is trying to reconnect
I have checked and connected the same broweser to another NR docker (with DB1) on same server but I do not see any [socket.io](http://socket.io) issues ... there are as well no disconnect or unresponsive sessions with this NR docker and DB1
> [@TotallyInformation](#):
>
> Though you could try temporarily turning off the unifi controller if that is what you have running. That shouldn't affect your WiFi.
I'm not using wifi but wired 1gb network connect to connect to the NR docker with DB (but have done for testing purpose with same results
> [@TotallyInformation](#):
>
> What is `catcher.js`? I don't see that on my example D2 page. It appears to be controlling the websocket. It is triggered from `injector.js` which I also don't see.
I dont know where those resulting from as I'm using the normal NR nodes and not aware which one is using catcher.js
thanks for all your help and responses
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [5 August 2024 00:07 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/24 "2024-08-05T00:07:38Z")
You are correct ... bad coding practice not to clean-up your code when it evolves 😉 from static pictures to dynamic 🙂
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [5 August 2024 10:06 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/25 "2024-08-05T10:06:26Z")
> [@xx\_Nexus\_xx](#):
>
> How can I influence or configure the [socket.io](http://socket.io) server as my (1GB) network is having lots of available capacity (I easily can stream several 4k videos at same time) and have as well done test with OpenSpeedTest and other bandwith tools.
Well generally, the only thing you want to change on [socket.io](http://socket.io) is the max message size. But for D2, I'm afraid that I think it has any way to change settings on [Socket.IO](http://Socket.IO) other than the max buffer/message size and connection middleware.
> **[Settings | Node-RED Dashboard 2.0](https://dashboard.flowfuse.com/user/settings.html)**
>
> Customize your Node-RED Dashboard 2.0 experience with detailed settings for optimal dashboard performance and appearance.
> [@xx\_Nexus\_xx](#):
>
> > [@TotallyInformation](#):
> >
> > What is `catcher.js`? I don't see that on my example D2 page. It appears to be controlling the websocket. It is triggered from `injector.js` which I also don't see.
>
> I dont know where those resulting from as I'm using the normal NR nodes and not aware which one is using catcher.js
Right, you need to track down what those are. Any clues from the js files themselves? And where is that injector.js coming from? The network tab isn't showing it - if you click on that line and go to the resulting "Initiator" tab, it should show the thread of scripts that loaded it.
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [6 August 2024 00:33 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/26 "2024-08-06T00:33:45Z")
I checked the catcher.js:197 and it is always selecting the "_**send.apply(this,arguments)**_"
I will check my code for the send command
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [6 August 2024 10:27 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/27 "2024-08-06T10:27:21Z")
> [@xx\_Nexus\_xx](#):
>
> I checked the catcher.js:197 and it is always selecting the "_**send.apply(this,arguments)**_"
That appears to be a browser extension rather than something core. Can you try a different browser or use an in-private browsing session?
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [6 August 2024 21:39 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/28 "2024-08-06T21:39:15Z")
I tried with MS Edge and it has the same [socket.io](http://socket.io) elements with the JS code. However in this it is not called catcher ... but highlighting a similar "SEND" command (this is for all [socket.io](http://socket.io) events)
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [7 August 2024 08:00 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/29 "2024-08-07T08:00:21Z")
Right, that confirms it then. Your other browser has something that intercepts your page scripts.
So are you getting the same issues on Edge?
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [7 August 2024 09:00 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/30 "2024-08-07T09:00:07Z")
yes same symptoms on EDGE ... and from my mac with safari
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [7 August 2024 09:07 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/31 "2024-08-07T09:07:29Z")
OK, well at least we've eliminated that as an issue.
I'm afraid that I'm stumped now though.
You're server seems more than capable enough and I assume you continue to monitor for memory, network and CPU issues. We've shown that it happens on different clients. So really, I think that leaves something in your ui\_template code?
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [7 August 2024 09:27 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/32 "2024-08-07T09:27:54Z")
As an experiment, could you remove all input wires to all charts please and see if that affects it? I am concerned about the 86400 points you have on each chart. Even when it is not on screen the server still has to handle that data, though I don't see why that would particularly affect the loading of other pages. I still think it would be a worthwhile experiment. I am surprised the charts do not clobber the browser when they are on screen. Restart node-red so the charts are emptied.
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [7 August 2024 23:41 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/33 "2024-08-07T23:41:09Z")
Hi Colin,
i have disbaled all my chart-nodes, executed a full deploy and container-restart.
It is noe running for a few hours without any disconnect/deay or unresponsiveness but I will keep it running without any further change for at least 24h and report back
---
### Author:  [@xx\_Nexus\_xx](https://discourse.nodered.org/u/xx_Nexus_xx)
#### Post date: [9 August 2024 06:33 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/34 "2024-08-09T06:33:26Z")
Hi Colin,
looks like you were absolutely right and the issue was related to the chart-node and amount of points I had gathered.
After disabling all chart nodes and restarting my system, I have not experienced any issues/disconnects/unresponsiveness with DB2 elements.
thx a lot for all your help
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [23 August 2024 06:33 UTC](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929/35 "2024-08-23T06:33:29Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
[Previous page](https://discourse.nodered.org/t/no-response-disconnect-of-db2/89929.md?page=1)