[7.13.1] CoreCrashedError: The Tribler core has unexpectedly finished with exit code 11 and status: 1. Resource temporarily unavailable.

[sentry-for-tribler]

Sentry Issue: TRIBLER-1GX

CreationTraceback: 
  File "run_tribler.py", line 115, in <module>
  File "tribler/gui/start_gui.py", line 82, in run_gui
  File "tribler/gui/upgrade_manager.py", line 252, in on_worker_finished
  File "tribler/gui/utilities.py", line 439, in trackback_wrapper
  File "tribler/gui/core_manager.py", line 135, in start_tribler_core

CoreCrashedError: The Tribler core has unexpectedly finished with exit code 11 and status: 1.

Error message: Resource temporarily unavailable
  File "tribler/gui/utilities.py", line 442, in trackback_wrapper
  File "tribler/gui/utilities.py", line 439, in trackback_wrapper
  File "tribler/gui/core_manager.py", line 315, in on_core_finished

Last core output:

[tribler-core PID:730953] 2024-01-03 01:10:43,602 - ERROR <community:271> DHTDiscoveryCommunity.on_ping_response(): Got ping-response with unknown identifier, dropping packet
[tribler-core PID:730953] 2024-01-03 01:11:38,034 - ERROR <community:271> DHTDiscoveryCommunity.on_ping_response(): Got ping-response with unknown identifier, dropping packet
[tribler-core PID:730953] 2024-01-03 01:12:56,576 - ERROR <community:271> DHTDiscoveryCommunity.on_ping_response(): Got ping-response with unknown identifier, dr...]

[qstokkink]

We have seen the "Resource temporarily unavailable" error (see Sentry log) before. Quoting @devos50 from #4171:

Having so many open connections to others could lead to unexpected behavior. [...] It also seems that the system ran out of file descriptors: [Errno 11] Resource temporarily unavailable.

Essentially, we have too many open connections and that causes this error. The fix is easier said that done: we should throttle the number of open connections. The caveat is that these connections may be established anywhere in our code base.

[sentry-for-tribler]

Sentry issue: TRIBLER-1M2

[github-actions]

This issue has not seen activity for 60 days. It is now marked as stale. Please provide additional information or this issue may be closed in the future. We value your contribution and would love to hear more!

[qstokkink]

Now that Tribler only consists of one process, this particular error should no longer be possible.