0

I have a pod which is trying to connect to Elastic search pod but it is failing. So, when I checked Elastic search pod logs, I am getting the following error.

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_syslog-ng.init...
Jan  5 20:20:02 elasticsearch-0 syslog-ng[12]: syslog-ng starting up; version='3.5.6'
Jan  5 20:20:03 elasticsearch-0 syslog-ng[12]: EOF on control channel, closing connection;
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 18
Jan  5 20:20:03 elasticsearch-0 cron[23]: (CRON) INFO (pidfile fd = 3)
Jan  5 20:20:03 elasticsearch-0 cron[23]: (CRON) INFO (Running @reboot jobs)
./run: line 62: ulimit: max locked memory: cannot modify limit: Operation not permitted
curl: (7) Failed to connect to elasticsearch-tekstack-0 port 9200: Connection refused

I have checked whether Elastic search service, endpoints are created or not. All those have been created. I am not sure why this error popping out.

David Maze
  • 130,717
  • 29
  • 175
  • 215
StackOverflow Asker
  • 167
  • 17
  • You can either disable swapping on your host or configure bootstrap.memory_lock. The details are provided in Elastic documentation here: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration-memory.html – Ayush Jan 09 '23 at 08:55

0 Answers0