API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 11th, 2019
375
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.25 KB | None | 0 0
raw download clone embed print report
  1. $ kube logs mongos-router-0
  2. 2019-03-11T14:00:22.456+0000 I NETWORK [main] getaddrinfo("mongod-configdb-1.mongodb-configdb-service.default.svc.cluster.local") failed: Name or service not known
  3. 2019-03-11T14:00:22.499+0000 I NETWORK [main] getaddrinfo("mongod-configdb-2.mongodb-configdb-service.default.svc.cluster.local") failed: Name or service not known
  4. 2019-03-11T14:00:22.500+0000 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
  5. 2019-03-11T14:00:22.506+0000 I CONTROL [main]
  6. 2019-03-11T14:00:22.506+0000 I CONTROL [main] ** WARNING: Access control is not enabled for the database.
  7. 2019-03-11T14:00:22.506+0000 I CONTROL [main] ** Read and write access to data and configuration is unrestricted.
  8. 2019-03-11T14:00:22.506+0000 I CONTROL [main] ** WARNING: You are running this process as the root user, which is not recommended.
  9. 2019-03-11T14:00:22.506+0000 I CONTROL [main]
  10. 2019-03-11T14:00:22.506+0000 I SHARDING [mongosMain] mongos version v4.0.6
  11. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] git version: caa42a1f75a56c7643d0b68d3880444375ec42e3
  12. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
  13. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] allocator: tcmalloc
  14. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] modules: none
  15. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] build environment:
  16. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] distmod: ubuntu1604
  17. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] distarch: x86_64
  18. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] target_arch: x86_64
  19. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] db version v4.0.6
  20. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] git version: caa42a1f75a56c7643d0b68d3880444375ec42e3
  21. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
  22. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] allocator: tcmalloc
  23. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] modules: none
  24. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] build environment:
  25. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] distmod: ubuntu1604
  26. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] distarch: x86_64
  27. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] target_arch: x86_64
  28. 2019-03-11T14:00:22.506+0000 I CONTROL [mongosMain] options: { net: { bindIp: "0.0.0.0", port: 27017 }, sharding: { configDB: "ConfigDBRepSet/mongod-configdb-0.mongodb-configdb-service.default.svc.cluster.local:27017,mongod-configdb-1.mongodb-configdb-service.default.svc.clust..." } }
  29. 2019-03-11T14:00:22.507+0000 I NETWORK [mongosMain] Starting new replica set monitor for ConfigDBRepSet/mongod-configdb-0.mongodb-configdb-service.default.svc.cluster.local:27017,mongod-configdb-1.mongodb-configdb-service.default.svc.cluster.local:27017,mongod-configdb-2.mongodb-configdb-service.default.svc.cluster.local:27017
  30. 2019-03-11T14:00:22.508+0000 I SHARDING [thread1] creating distributed lock ping thread for process mongos-router-0:27017:1552312822:6740860393040674588 (sleeping for 30000ms)
  31. 2019-03-11T14:00:22.511+0000 I NETWORK [replSetDistLockPinger] Successfully connected to mongod-configdb-0.mongodb-configdb-service.default.svc.cluster.local:27017 (1 connections now open to mongod-configdb-0.mongodb-configdb-service.default.svc.cluster.local:27017 with a 5 second timeout)
  32. 2019-03-11T14:00:22.553+0000 W NETWORK [mongosMain] Unable to reach primary for set ConfigDBRepSet
  33. 2019-03-11T14:00:22.553+0000 I NETWORK [mongosMain] Cannot reach any nodes for set ConfigDBRepSet. Please check network connectivity and the status of the set. This has happened for 1 checks in a row.
  34. 2019-03-11T14:00:23.086+0000 W NETWORK [mongosMain] Unable to reach primary for set ConfigDBRepSet
  35. 2019-03-11T14:00:23.086+0000 I NETWORK [mongosMain] Cannot reach any nodes for set ConfigDBRepSet. Please check network connectivity and the status of the set. This has happened for 2 checks in a row.
  36. 2019-03-11T14:00:23.592+0000 W NETWORK [shard registry reload] Unable to reach primary for set ConfigDBRepSet
  37. 2019-03-11T14:00:23.592+0000 I NETWORK [shard registry reload] Cannot reach any nodes for set ConfigDBRepSet. Please check network connectivity and the status of the set. This has happened for 3 checks in a row.
  38. 2019-03-11T14:00:24.098+0000 W NETWORK [monitoring keys for HMAC] Unable to reach primary for set ConfigDBRepSet
  39. 2019-03-11T14:00:24.098+0000 I NETWORK [monitoring keys for HMAC] Cannot reach any nodes for set ConfigDBRepSet. Please check network connectivity and the status of the set. This has happened for 4 checks in a row.
  40. 2019-03-11T14:00:24.605+0000 I NETWORK [monitoring keys for HMAC] Successfully connected to mongod-configdb-1.mongodb-configdb-service.default.svc.cluster.local:27017 (1 connections now open to mongod-configdb-1.mongodb-configdb-service.default.svc.cluster.local:27017 with a 5 second timeout)
  41.  
  42. [...]
  43.  
  44. 2019-03-11T14:17:24.462+0000 W SHARDING [replSetDistLockPinger] pinging failed for distributed lock pinger :: caused by :: FailedToSatisfyReadPreference: Could not find host matching read preference { mode: "primary" } for set ConfigDBRepSet
  45. 2019-03-11T14:17:24.463+0000 I SHARDING [shard registry reload] Periodic reload of shard registry failed :: caused by :: FailedToSatisfyReadPreference: could not get updated shard list from config server :: caused by :: Could not find host matching read preference { mode: "nearest" } for set ConfigDBRepSet; will retry after 30s
  46. 2019-03-11T14:17:24.908+0000 W NETWORK [mongosMain] Unable to reach primary for set ConfigDBRepSet
  47. 2019-03-11T14:17:24.913+0000 W NETWORK [monitoring keys for HMAC] Unable to reach primary for set ConfigDBRepSet
  48. 2019-03-11T14:17:25.409+0000 W NETWORK [mongosMain] Unable to reach primary for set ConfigDBRepSet
  49. 2019-03-11T14:17:25.414+0000 W NETWORK [monitoring keys for HMAC] Unable to reach primary for set ConfigDBRepSet
  50. 2019-03-11T14:17:25.912+0000 W NETWORK [mongosMain] Unable to reach primary for set ConfigDBRepSet
  51. 2019-03-11T14:17:25.916+0000 W NETWORK [monitoring keys for HMAC] Unable to reach primary for set ConfigDBRepSet
  52. 2019-03-11T14:17:26.414+0000 W NETWORK [mongosMain] Unable to reach primary for set ConfigDBRepSet
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!