Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Elasticsearch doesn't come up (not enough memory in VM) #16

Closed
chiefy opened this issue Oct 14, 2015 · 4 comments
Closed

Elasticsearch doesn't come up (not enough memory in VM) #16

chiefy opened this issue Oct 14, 2015 · 4 comments

Comments

@chiefy
Copy link

chiefy commented Oct 14, 2015

/var/log/supervisor/elasticsearch.log is empty, so not really sure how to troubleshoot this, I ran the command in the supervisor config for ES manually and it seemed to work fine?

[root@elk supervisor]# cat supervisord.log
2015-10-14 23:25:14,387 CRIT Supervisor running as root (no user in config file)
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/diamond.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/statsd.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/nginx.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/kibana.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/elasticsearch.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/logstash_watchdog.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/logstash.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/watchpsutil.ini" during parsing
2015-10-14 23:25:14,387 WARN Included extra file "/etc/supervisord.d/consul.ini" during parsing
2015-10-14 23:25:14,388 WARN Included extra file "/etc/supervisord.d/rsyslog.ini" during parsing
2015-10-14 23:25:14,418 INFO RPC interface 'supervisor' initialized
2015-10-14 23:25:14,419 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-10-14 23:25:14,419 INFO supervisord started with pid 12
2015-10-14 23:25:15,422 INFO spawned: 'elasticsearch' with pid 15
2015-10-14 23:25:15,424 INFO spawned: 'logstash_watchdog' with pid 16
2015-10-14 23:25:15,428 INFO spawned: 'statsd' with pid 17
2015-10-14 23:25:15,430 INFO spawned: 'diamond' with pid 18
2015-10-14 23:25:15,437 INFO spawned: 'consul' with pid 19
2015-10-14 23:25:15,451 INFO spawned: 'kibana' with pid 23
2015-10-14 23:25:15,460 INFO spawned: 'watchpsutil' with pid 26
2015-10-14 23:25:15,462 INFO spawned: 'nginx' with pid 27
2015-10-14 23:25:15,479 INFO spawned: 'rsyslog' with pid 32
2015-10-14 23:25:15,565 INFO exited: elasticsearch (exit status 1; not expected)
2015-10-14 23:25:16,474 INFO success: logstash_watchdog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,474 INFO success: statsd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,474 INFO success: diamond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,475 INFO success: kibana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,475 INFO success: watchpsutil entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,475 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,490 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-14 23:25:16,701 INFO spawned: 'elasticsearch' with pid 288
2015-10-14 23:25:16,722 INFO spawned: 'logstash' with pid 290
2015-10-14 23:25:16,771 INFO exited: elasticsearch (exit status 1; not expected)
@ChristianKniep
Copy link
Owner

Hey there,

I pulled the latest qnib/elk image and for me it works...
screen shot 2015-10-15 at 12 36 19

[root@elk opt]# cat /var/log/supervisor/supervisord.log
2015-10-15 12:20:07,881 CRIT Supervisor running as root (no user in config file)
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/statsd.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/diamond.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/nginx.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/kibana.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/elasticsearch.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/logstash_watchdog.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/logstash.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/watchpsutil.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/consul.ini" during parsing
2015-10-15 12:20:07,882 WARN Included extra file "/etc/supervisord.d/rsyslog.ini" during parsing
2015-10-15 12:20:07,911 INFO RPC interface 'supervisor' initialized
2015-10-15 12:20:07,912 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-10-15 12:20:07,912 INFO supervisord started with pid 9
2015-10-15 12:20:08,922 INFO spawned: 'elasticsearch' with pid 12
2015-10-15 12:20:08,924 INFO spawned: 'logstash_watchdog' with pid 13
2015-10-15 12:20:08,926 INFO spawned: 'statsd' with pid 14
2015-10-15 12:20:08,929 INFO spawned: 'diamond' with pid 16
2015-10-15 12:20:08,932 INFO spawned: 'consul' with pid 19
2015-10-15 12:20:08,934 INFO spawned: 'kibana' with pid 21
2015-10-15 12:20:08,936 INFO spawned: 'watchpsutil' with pid 23
2015-10-15 12:20:08,939 INFO spawned: 'nginx' with pid 25
2015-10-15 12:20:08,947 INFO spawned: 'rsyslog' with pid 30
2015-10-15 12:20:09,944 INFO success: elasticsearch entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,945 INFO success: logstash_watchdog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,945 INFO success: statsd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,945 INFO success: diamond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,945 INFO success: kibana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,945 INFO success: watchpsutil entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,945 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:09,952 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:10,121 INFO spawned: 'logstash' with pid 301
2015-10-15 12:20:11,243 INFO success: logstash entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:14,245 INFO success: consul entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2015-10-15 12:20:31,031 INFO exited: diamond (exit status 127; not expected)
2015-10-15 12:20:32,036 INFO spawned: 'diamond' with pid 535
2015-10-15 12:20:33,038 INFO success: diamond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:20:54,072 INFO exited: diamond (exit status 127; not expected)
2015-10-15 12:20:55,075 INFO spawned: 'diamond' with pid 684
2015-10-15 12:20:56,078 INFO success: diamond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:21:17,111 INFO exited: diamond (exit status 127; not expected)
2015-10-15 12:21:17,819 INFO spawned: 'diamond' with pid 826
2015-10-15 12:21:19,755 INFO success: diamond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2015-10-15 12:21:39,853 INFO exited: diamond (exit status 127; not expected)
2015-10-15 12:21:40,621 INFO spawned: 'diamond' with pid 977
2015-10-15 12:21:41,629 INFO success: diamond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

How much memory do you got on the machine? Maybe it's not enough to supply the JVM. :)

@chiefy
Copy link
Author

chiefy commented Oct 15, 2015

Ah, yeah, that was the issue. I am running docker-machine and my VM only had 1GB of RAM. I bumped it to 2GB and things are working. Thanks!

@chiefy chiefy closed this as completed Oct 15, 2015
@ChristianKniep
Copy link
Owner

My pleasure... thanks for the feedback! I guess I should add a check somehow...

@ChristianKniep
Copy link
Owner

I put it in the readme...

@chiefy chiefy changed the title Elasticsearch doesn't come up Elasticsearch doesn't come up (not enough memory in VM) Oct 15, 2015
@ChristianKniep ChristianKniep mentioned this issue Mar 5, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chiefy @ChristianKniep