Closed yoursmanish closed 3 years ago
cannot rollback to previous version as using $setWindowFields in pipeline
No connection could be made because the target machine actively refused it
The mongodb logs show PyMongo causing a segmentation fault
{"remote":"10.77.97.254:62895","client":"conn21","doc":{"driver":{"name":"PyMongo","version":"3.12.0"},"os":{"type":"Windows","name":"Windows 10","architecture":"AMD64","version":"10.0.18362-SP0"},"platform":"CPython 3.7.9.final.0"}}}
{"t":{"$date":"2021-07-28T03:52:58.639+00:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"conn20","msg":"Writing fatal message","attr":{"message":"Invalid access at address: 0x10"}}
{"t":{"$date":"2021-07-28T03:52:58.639+00:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"conn20","msg":"Writing fatal message","attr":{"message":"Got signal: 11 (Segmentation fault).\n"}}
But without something reproducible showing an issue in the way Mongo is packaged in a container then I don't think there's isn't anything we could do to alleviate this. I would try asking over at a mongo-specific resource or the Docker Community Forums, Docker Community Slack, or Stack Overflow. Since these repos aren't really a user-help forum
mongo:5.0.0 - container dies with 139 on executing aggregate on RHEL 7.6 dockerfile
docker events
MongoDB Compass
pymongo code
pymongo version $ pip list | grep pymongo pymongo 3.12.0
pymongo exception
docker logs mongodb_mongo-db_1 -f