Fetch Failed with multiple instances across multiple modules (multiple config)

[WiredRacing]

MM2 in Docker, recently configured multiple instances which were working just fine.

However after a restart of the container, on one instance I have various “Error in the module. Check logs for more details.” (where name is Calendar or Newsfeed).

Over time (when refresh is triggered), the newsfeed comes online, and later the weather forecast will show up (it’s stuck at ‘loading…’ for a while.

This would be fine except the Calendar doesn’t clear this situation as I guess it doesn’t exactly refresh like the others do.

When I first view this instance in a browser, I see the calendar module list the upcoming events just fine, then I see MMM-MonthlyCalendar pop up (as it has), but then the calendar module area fades out and reports this error. I believe it’s on the attempt to broadcast.

Message is some flavor of: TypeError: fetch failed for both modules.

For example:

[2024-09-19 16:23:02.804] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/<redacted>.ics TypeError: fetch failed
    at node:internal/deps/undici/undici:12618:11
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
      _finishFlushFlag: 2,
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processImmediate (node:internal/timers:447:9) {
  cause: ConnectTimeoutError: Connect Timeout Error
      at onConnectTimeout (node:internal/deps/undici/undici:7760:28)
      at node:internal/deps/undici/undici:7716:50
      _defaultFullFlushFlag: 3,      at Immediate._onImmediate (node:internal/deps/undici/undici:7748:13)

      at process.processImmediate (node:internal/timers:476:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
  }
} 

The newsfeed one is similar.

Does this have anything to do with two instances of the server running but sharing resources? If I refresh my 2nd instance (which uses the same calendar module config), it works just fine.

Help! Not sure what changed…they were coexisting fine.

[sdetweil]

@WiredRacing I think the error recovery did not recover

restarting the container restarts and it will run fine til it fails… and may recover… or not

[karsten13]

can you provide the logs of system information?

Something like this:

[2024-09-19 21:52:27.750] [INFO]  System information:
### SYSTEM:   manufacturer: Microsoft; model: Docker Container; virtual: true
### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: x64; kernel: 5.15.153.1-microsoft-standard-WSL2
### VERSIONS: electron: undefined; used node: 22.9.0; installed node: 22.9.0; npm: 10.8.3; pm2:
### OTHER:    timeZone: UTC; ELECTRON_ENABLE_GPU: undefined

[WiredRacing]

[2024-09-19 14:43:56.866] [INFO]  System information:
### SYSTEM:   manufacturer: Gigabyte Technology Co., Ltd.; model: Docker Container; raspberry: undefined; virtual: false
### OS:       platform: linux; distro: Debian GNU/Linux; release: 11; arch: x64; kernel: 6.1.64-Unraid
### VERSIONS: electron: undefined; used node: 18.20.2; installed node: 18.20.2; npm: 10.5.0; pm2: 
### OTHER:    timeZone: America/New_York; ELECTRON_ENABLE_GPU: undefined

[sdetweil]

@WiredRacing can you upgrade the nodejs to version 20

[WiredRacing]

@sdetweil thanks. That did it!

New problem post for how to auto-run both configs on startup (right now I manually start the second one).