Uncaught error when network issue

[michnovka]

What happened?

The API container has crashed (without restarting) when I experienced network issues

Steps to Reproduce

1. spin up docker-compose
2. use iptables to remove all DOCKER rules, or otherwise make network unstable
3. see container crash

What browsers are you seeing the problem on?

No response

Relevant log output

superuser@SuperTower:~$ docker logs librechat-api

> [email protected] backend
> cross-env NODE_ENV=production node api/server/index.js

2024-09-10 17:51:48 info: [Optional] Redis not initialized. Note: Redis support is experimental.
2024-09-10 17:51:50 info: Connected to MongoDB
2024-09-10 17:51:50 info: Custom config file loaded:
2024-09-10 17:51:50 info: {
  "version": "1.1.5",
  "cache": true,
  "interface": {
    "privacyPolicy": {
      "externalUrl": "https://librechat.ai/privacy-policy",
      "openNewTab": true
    },
    "termsOfService": {
      "externalUrl": "https://librechat.ai/tos",
      "openNewTab": true
    }
  },
  "registration": {
    "socialLogins": [
      "github",
      "google",
      "discord",
      "openid",
      "facebook"
    ]
  },
  "endpoints": {
    "custom": [
      {
        "name": "Ollama",
        "apiKey": "ollama",
        "baseURL": "http://ollama:11434/v1/chat/completions",
        "models": {
          "default": [
            "llama3.1:8b"
          ],
          "fetch": false
        },
        "titleConvo": true,
        "titleModel": "current_model",
        "summarize": false,
        "summaryModel": "current_model",
        "forcePrompt": false,
        "modelDisplayLabel": "Ollama"
      }
    ]
  }
}
2024-09-10 17:51:50 info: RAG API is running and reachable at http://rag_api:8000.
2024-09-10 17:51:50 info: No changes needed for 'USER' role permissions
2024-09-10 17:51:50 info: No changes needed for 'ADMIN' role permissions
2024-09-10 17:51:50 info: 
Outdated Config version: 1.1.5
Latest version: 1.1.7

      Check out the Config changelogs for the latest options and features added.

      https://www.librechat.ai/changelog


2024-09-10 17:51:50 info: Server listening on all interfaces at port 3080. Use http://localhost:3080 to access it
2024-09-10 18:34:36 error: [refreshController] Refresh token: XXXXXXXX.XXXXXXXXXXfQ.XXXXXXXX-XXXXXXXXX-Du_NE connection timed out
2024-09-10 18:34:41 error: [refreshController] Refresh token: XXXXXXXX.XXXXXXXXXXfQ.XXXXXXXX-XXXXXXXXX-Du_NE connection timed out
2024-09-10 18:35:12 error: There was an uncaught error: connection timed out
npm notice
npm notice New patch version of npm available! 10.8.2 -> 10.8.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3
npm notice To update run: npm install -g [email protected]
npm notice

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[michnovka]

I have my system behind iptables firewall. To reproduce it, I just have to do systemctl restart iptables which removes docker rules (to fix docker rules I have to systemctl restart docker)
This causes those refreshController errors and then the crash

[danny-avila]

This is an unusual edge case, and seems to be triggered outside of the app, so I moved this to Discussions.

Could you provide the error logs for this?

2024-09-10 18:34:36 error: [refreshController] Refresh token: XXXXXXXX.XXXXXXXXXXfQ.XXXXXXXX-XXXXXXXXX-Du_NE connection timed out
2024-09-10 18:34:41 error: [refreshController] Refresh token: XXXXXXXX.XXXXXXXXXXfQ.XXXXXXXX-XXXXXXXXX-Du_NE connection timed out

They would contain the stack trace to more gracefully handle the errors.

The logs can be found in the ./logs directory of project root

[michnovka]

The logs/debug-2024-09-10.log file has only these lines, nothing else

[michnovka]

Ok, I found it in errors log:

{"level":"error","message":"[refreshController] Refresh token: XXXX connection timed out","reason":{"commonWireVersion":0,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"logicalSessionTimeoutMinutes":null,"maxElectionId":null,"maxSetVersion":null,"servers":{},"setName":null,"stale":false,"type":"Single"},"stack":"MongoServerSelectionError: connection timed out\n    at Timeout._onTimeout (/app/node_modules/mongoose/node_modules/mongodb/lib/sdam/topology.js:278:38)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)"}
{"level":"error","message":"[refreshController] Refresh token: XXXX connection timed out","reason":{"commonWireVersion":0,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"logicalSessionTimeoutMinutes":null,"maxElectionId":null,"maxSetVersion":null,"servers":{},"setName":null,"stale":false,"type":"Single"},"stack":"MongoServerSelectionError: connection timed out\n    at Timeout._onTimeout (/app/node_modules/mongoose/node_modules/mongodb/lib/sdam/topology.js:278:38)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)"}
{"level":"error","message":"There was an uncaught error: connection timed out","reason":{"commonWireVersion":0,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"logicalSessionTimeoutMinutes":null,"maxElectionId":null,"maxSetVersion":null,"servers":{},"setName":null,"stale":false,"type":"Single"},"stack":"MongoServerSelectionError: connection timed out\n    at Timeout._onTimeout (/app/node_modules/mongoose/node_modules/mongodb/lib/sdam/topology.js:278:38)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)"}