- Yan Zhao-
- Sandeep Puthanveetil Satheesan - absent
- Luigi Marini - absent
- Shannon Bradley -
- Mark Fredricksen -
- Rob Kooper - absent
- Kenton McHenry - absent
- Gregory Jansen - absent
- Dukyun Nam - absent
- Deren Kudeki
Troubleshooting mongo connection from transformations catalog. The catalog is sending data to the mongo server, which appears to be responding. I have verified that I can connect to the mongo database from my laptop using the mongo command line, but the transformation catalog and compass still fail to connect. Checking to see if there are known issues with pymongo, and ways to get more information about where the failure is occurring in the transformations catalog.
The error seems to only come in when trying to connect to the BROWNDOG replica set, no matter giving the IP or server name, giving the following error even when giving only a single node or using the server name ending in ncsa.illinois.edu:
pymongo.errors.ServerSelectionTimeoutError: bd-mongo-3.os.ncsa.edu:27017: [Errno 8] nodename nor servname provided, or not known,bd-mongo-2.os.ncsa.edu:27017: [Errno 8] nodename nor servname provided, or not known,bd-mongo-1.os.ncsa.edu:27017: [Errno 8] nodename nor servname provided, or not known
This can be fixed with entries in /etc/hosts for bd-mongo-#.os.ncsa.edu.
I have been dealing with a server and netapp filer migration from one datacenter to another. The physical move of hardware was straightforward and fun, like snapping together a model airplane. The network configuration was another matter. The network upstream is supposed to be identical, but nonetheless my old network configuration is toast. I've been working to restore a fully functioning cluster since Wednesday.