Last active
January 26, 2018 01:31
-
-
Save dance2die/b7e815a3a4e3be3f46dbc92299e7d1c7 to your computer and use it in GitHub Desktop.
Checking the status of ElasticSearch by running "systemctl status elasticsearch"
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
root@ip-xxx:/etc/elasticsearch# systemctl status elasticsearch | |
● elasticsearch.service - Elasticsearch | |
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled) | |
Active: failed (Result: exit-code) since Fri 2018-01-26 01:25:00 UTC; 7s ago | |
Docs: http://www.elastic.co | |
Process: 11163 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FA Main PID: 11163 (code=exited, status=1/FAILURE) | |
Jan 26 01:24:59 ip-xxx systemd[1]: Started Elasticsearch. | |
Jan 26 01:25:00 ip-xxx elasticsearch[11163]: OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000c5330000, 98Jan 26 01:25:00 ip-xxx elasticsearch[11163]: # | |
Jan 26 01:25:00 ip-xxx systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE | |
Jan 26 01:25:00 ip-xxx systemd[1]: elasticsearch.service: Unit entered failed state. | |
Jan 26 01:25:00 ip-xxx systemd[1]: elasticsearch.service: Failed with result 'exit-code'. | |
root@ip-xxx:/etc/elasticsearch# |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment