You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SQL loader is establishing connections but not properly releasing them, resulting in exhaustion of the maximum allowed connections.
Minimum reproducible example
No response
Relevant log output
Error occurred in source. Error msg: RuntimeError: Execution failed processing function _read_sql. Error: (psycopg2.OperationalError) connection to server at "nvidia-keycloak-ha.nvidia-platform" (10.101.89.69), port 5432 failed: FATAL: remaining connection slots are reserved for non-replication superuser connections
(Background on this error at: https://sqlalche.me/e/14/e3q8)
At:
/workspace/private_examples/spear_phishing/spear_phishing/modules/email_enrichment.py(323): slot_gather_and_error_check
/workspace/private_examples/spear_phishing/spear_phishing/modules/email_enrichment.py(342): write_to_output
E20230929 22:22:24.913244 173 context.cpp:124] /main/mrc::pymrc::PythonSegmentModule::phishing_pre_inference/mrc::pymrc::PythonSegmentModule::email_enrichment/output_node; rank: 0; size: 1; tid: 139648764466752: set_exception issued; issuing kill to current runnable. Exception msg: RuntimeError: Execution failed processing function _read_sql. Error: (psycopg2.OperationalError) connection to server at "nvidia-keycloak-ha.nvidia-platform" (10.101.89.69), port 5432 failed: FATAL: remaining connection slots are reserved for non-replication superuser connections
(Background on this error at: https://sqlalche.me/e/14/e3q8)
Full env printout
No response
Other/Misc.
No response
Code of Conduct
I agree to follow Morpheus' Code of Conduct
I have searched the open bugs and have found no duplicates for this bug report
The text was updated successfully, but these errors were encountered:
Version
23.11
Which installation method(s) does this occur on?
Docker
Describe the bug.
The SQL loader is establishing connections but not properly releasing them, resulting in exhaustion of the maximum allowed connections.
Minimum reproducible example
No response
Relevant log output
Full env printout
No response
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: