There are many functions that return an EBUSY error without logging any information. This ticket is to investigate cases where conn->close returns EBUSY without logging. A further step will be creating documentation for the server team so they can know what to do next when encountering EBUSY on conn->close. If it's challenging to target all those cases, a recommended approach could be to first add logging to functions where EBUSY is returned.