ConnectionPoolExpired error - Dropping all pooled connections

Ops and Admin
1

Hi.

On one of our MongoDB servers I’m seeing this error every ~2 days is logs:

{"t":{"$date":"2023-01-03T06:03:26.735+01:00"},"s":"I", "c":"CONNPOOL", "id":22576, "ctx":"CurlConnPool-195","msg":"Connecting","attr":{"hostAndPort":"ocsp.<host>:80"}}

{"t":{"$date":"2023-01-03T06:05:26.763+01:00"},"s":"I", "c":"CONNPOOL", "id":22572, "ctx":"CurlConnPool-198","msg":"Dropping all pooled connections","attr":{"hostAndPort":"ocsp.<host>:80","error":"ConnectionPoolExpired: Pool for ocsp.<host>:80 has expired."}}

Is this something that we should worry about? What might be causing these errors?

3

Hello @AM_88 ,

Welcome to The MongoDB Community Forums! :wave:

As this is an informational message hence I don’t think this should interfere with any other ongoing operations. Are you facing any other issues or just wanted to know more about this log message? If you are, please share below details:

  • Any events in the deployment that you can trace back to the appearance of these messages, e.g. a secondary went offline, or similar events?
  • Are you seeing any other events pre and post this log message?
  • What is the MongoDB version you are using?
  • What is your deployment topology?

Regards,
Tarun