[BUG] RPC Timeout Logs

[andrewnguyen22]

Describe the bug

node1            | Oct 18 16:13:35.670 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:38824: i/o timeout
node1            | Oct 18 16:13:35.868 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:39356: i/o timeout
node1            | Oct 18 16:13:35.965 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:33586: i/o timeout
node1            | Oct 18 16:13:36.068 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:38598: i/o timeout
node1            | Oct 18 16:13:36.072 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:50386: i/o timeout
node1            | Oct 18 16:13:36.072 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:33386: i/o timeout
node1            | Oct 18 16:13:36.077 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:33436: i/o timeout
node1            | Oct 18 16:13:36.166 ERROR: [server write()] write response failed: write tcp 172.29.0.9:50002->172.29.0.1:50468: i/o timeout

it seems to be related to the block explorer and web wallet querying the json RCP through docker

Steps to reproduce

Steps to reproduce the behavior:

1. Docker Compose deployment through monitoring stck
2. Using default web wallet and block explorer
3. See log

Expected behavior

No log

Screenshot

Environment

• OS: Linux / Docker
• Software Version: Beta-0.1.13

Required Tags

• Priority: Low
• Module: RPC

[andrewnguyen22]

I believe this is a Canopy deployments level issue