Announcement

Collapse
No announcement yet.

ES-Client-1 and ES-Data-Node-* fail to start in Rancher

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • ES-Client-1 and ES-Data-Node-* fail to start in Rancher

    Hello,

    I have been following this guide: https://dyzz9obi78pm5.cloudfront.net...-guide-v21.pdf and used the Rancher Catalog: https://github.com/siemonster/v3-final.git On Rancher v.1.6.18.

    The whole stack comes up OK, except for the 3 containers: ES-Client-1, ES-Data-Node-1 and ES-Data-Node-2

    Looking in the logs they have the error: (paste bin link): https://pastebin.com/raw/0vazAWDQ

    Which seems strange considering they use rancher volumes as far as I can tell.

    Have you seen this issue before? Any ideas on how to resolve?

    Thanks



  • #2
    Tailing /var/log/messages on one of the host I see the above (pastebin) error plus:

    2018-06-08T05:55:11.142673+00:00 wa-knsg-elkdev2 journal: Running curl -L -s --fail -H "Accept: application/json" -H "Content-Type: application/json" -X GET -k http://admin:s13M0nSterV3@localhost:...er/preferences
    2018-06-08T05:55:11.211207+00:00 wa-knsg-elkdev2 journal: t=2018-06-08T05:55:11+0000 lvl=eror msg="Invalid username or password" logger=context error="Invalid Username or Password"
    2018-06-08T05:55:11.211945+00:00 wa-knsg-elkdev2 journal: t=2018-06-08T05:55:11+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/api/user/preferences status=401 remote_addr=[::1] time_ms=51 size=42 referer=

    Considering that I used the default catalog with default passwords I find this strange....

    Comment

    Working...
    X