Error
Error Code:
173
MongoDB Error 173: Transport Session Not Found
Description
Error 173, 'Transport Session Not Found', indicates that a network connection or logical session ID expected by a MongoDB instance could not be located or has become invalid. This error typically arises during communication between replica set members, sharded clusters, or between a client and the server, suggesting a disruption in the expected session state.
Error Message
Transport Session Not Found
Known Causes
4 known causesNetwork Instability or Disruption
An existing network connection or logical session between MongoDB instances or a client and server was unexpectedly terminated or lost due to network issues.
Invalid or Expired Session ID
A logical session ID provided by a client or another MongoDB server was not recognized, had expired, or was incorrectly referenced by the receiving instance.
Replica Set or Shard Configuration Mismatch
In a distributed environment, configuration inconsistencies or transient state issues can lead one member to expect a session ID that another member no longer holds.
Server Resource Exhaustion
Under heavy load, a MongoDB server might prematurely clean up sessions or fail to register new ones, leading to the 'session not found' error for ongoing operations.
Solutions
Coming SoonDetailed step-by-step solutions for this error are being prepared. In the meantime, try these general troubleshooting tips:
General Troubleshooting Tips
- Check the error message carefully for specific details
- Review recent changes that might have caused the error
- Search for the exact error code in the official documentation
- Check log files for additional context
- Try restarting the application or service