ndelitski / rancher-alarms

Will kick your ass if found unhealthy service in Rancher environment
85 stars 20 forks source link

ENOTFOUND error #22

Closed demarant closed 3 years ago

demarant commented 7 years ago

I tried the rancher-alarms by using the command:

# docker run -it -d -e RANCHER_ADDRESS=https://rancher.eea.europa.eu -e RANCHER_ACCESS_KEY=<my-account-key> -e RANCHER_SECRET_KEY=<my-secret-key> -e RANCHER_PROJECT_ID=1a11 -e ALARM_SLACK_WEBHOOK_URL=https://hooks.slack.com/services/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 ndelitski/rancher-alarms

We run Rancher 1.1.4 behind ngnix with basic SSL https this is our rancher docker compose

It connects and retrieves some stacks info but at certain point it crashes with the following error traceback:

...
[INFO]   2016-10-15 12:29:21:818   start polling eeabuildoutplone4/apache
[INFO]   2016-10-15 12:29:21:819   start polling eeabuildoutplone4/data
[INFO]   2016-10-15 12:29:21:819   start polling elastic-engine-demarant/esclient
[INFO]   2016-10-15 12:29:21:819   start polling elastic-engine-demarant/esmaster
[INFO]   2016-10-15 12:29:21:819   start polling elastic-engine-demarant/elastic-endpoint
[INFO]   2016-10-15 12:29:21:819   start polling elastic-engine-demarant/esworker1
[INFO]   2016-10-15 12:29:21:819   start polling elastic-engine-demarant/esworker2
[INFO]   2016-10-15 12:29:21:819   start polling elastic-app-eeasearch-demarant/elastic
[INFO]   2016-10-15 12:29:21:820   start polling elastic-app-eeasearch-demarant/reindex
[INFO]   2016-10-15 12:29:21:820   start polling elastic-app-eeasearch-demarant/eeasearch
[INFO]   2016-10-15 12:29:21:820   start polling elastic-app-eeasearch-demarant/autosync
[ERROR]  2016-10-15 12:36:52:473   [Error: RancherClientError: non-200 code response {
    "code": "ENOTFOUND",
    "errno": "ENOTFOUND",
    "syscall": "getaddrinfo",
    "hostname": "rancher.eea.europa.eu",
    "host": "rancher.eea.europa.eu",
    "port": 443
}] Error: RancherClientError: non-200 code response {
    "code": "ENOTFOUND",
    "errno": "ENOTFOUND",
    "syscall": "getaddrinfo",
    "hostname": "rancher.eea.europa.eu",
    "host": "rancher.eea.europa.eu",
    "port": 443
}
    at RancherClient._request$ (/usr/src/app/src/rancher.es6:50:13)
    at tryCatch (/usr/src/app/node_modules/babel-core/node_modules/regenerator/runtime.js:61:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/src/app/node_modules/babel-core/node_modules/regenerator/runtime.js:328:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (/usr/src/app/node_modules/babel-core/node_modules/regenerator/runtime.js:94:21)
    at GeneratorFunctionPrototype.invoke (/usr/src/app/node_modules/babel-core/node_modules/regenerator/runtime.js:136:37)
    at run (/usr/src/app/node_modules/babel-core/node_modules/core-js/modules/es6.promise.js:89:39)
    at /usr/src/app/node_modules/babel-core/node_modules/core-js/modules/es6.promise.js:100:28
    at flush (/usr/src/app/node_modules/babel-core/node_modules/core-js/modules/$.microtask.js:17:13)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickCallback (node.js:349:13)

I also tried via Rancher Stack using the examples provided... but it fails as well.

is it something we missed? thanks