D4Science Infrastructure

It seems a matter of authentication and not of firewall rules, from the logs.

Please, could you add the IPs reported by Kostantinos to the MongoDB development cluster?

Roberto Cirillo wrote:

Please, could you add the IPs reported by Kostantinos to the MongoDB development cluster?

Both the IP addresses were already present on the firewall ACLs, and as I wrote earlier it's not a firewall problem. From these logs:

[PORTAL] 1402160 [cluster-ClusterId{value='5971bba5ed3c6309faeac4c6', description='null'}-mongo1-d-d4s.d4science.org:27017] INFO  org.mongodb.driver.connection  - Opened connection [connectionId{localValue:19, serverValue:122242}] to mongo1-d-d4s.d4science.org:27017
[PORTAL] 1402494 [cluster-ClusterId{value='5971bba5ed3c6309faeac4c6', description='null'}-mongo1-d-d4s.d4science.org:27017] INFO  org.mongodb.driver.cluster  - Monitor thread successfully connected to server with description ServerDescription{address=mongo1-d-d4s.d4science.org:27017, type=REPLICA_SET_ARBITER, state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 0, 8]}, minWireVersion=0, maxWireVersion=3, electionId=null, maxDocumentSize=16777216, roundTripTimeNanos=333019829, setName='storagedev', canonicalAddress=mongo1-d-d4s.d4science.org:27017, hosts=[mongo2-d-d4s.d4science.org:27017, mongo3-d-d4s.d4science.org:27017], passives=[], arbiters=[mongo1-d-d4s.d4science.org:27017], primary='mongo3-d-d4s.d4science.org:27017', tagSet=TagSet{[]}}
[PORTAL] 1403348 [Thread-39] INFO  org.mongodb.driver.connection  - Opened connection [connectionId{localValue:20, serverValue:1582110}] to mongo3-d-d4s.d4science.org:27017
com.mongodb.MongoCommandException: Command failed with error 13: 'not authorized on remotefs to execute command { createIndexes: "fs.files", indexes: [ { key: { filename: 1 }, name: "filename_1", ns: "remotefs.fs.files" } ] }' on server mongo3-d-d4s.d4science.org:27017. The full response is { "ok" : 0.0, "errmsg" : "not authorized on remotefs to execute command { createIndexes: \"fs.files\", indexes: [ { key: { filename: 1 }, name: \"filename_1\", ns: \"remotefs.fs.files\" } ] }", "code" : 13 }
        at com.mongodb.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:77)

two facts are clear:

1. the application can contact mongo, so the firewall is not blocking anything
2. the operations were not authorized

It was indeed a key problem. Thanks for pointing that out.
That was all the error stacktrace i got. No "key missing" exception occured, that's why i got a bit confused.

Thanks for your help!