ehazlett / puppet-module-graylog2

Puppet module for the Graylog2 logging server
6 stars 1 forks source link

elasticsearch is not running #3

Open hamzasa opened 11 years ago

hamzasa commented 11 years ago

hi, I pull your changes and the installation was done without problems but the elasticsearch is not running. i tried to run it manually but i got: ./elasticsearch: 3: ./elasticsearch.in.sh: Bad substitution

can you help please

ehazlett commented 11 years ago

You shouldn't run ./elasticsearch.in.sh. There should be a supervisor config: /etc/supervisor/conf.d/elasticsearch.conf. You should be able to run sudo supervisorctl status to see if it's running and sudo supervisorctl start elasticsearch. Furthermore, if you want to run manually, there will be a bin directory (I believe /opt/elasticsearch/bin) and you can run bin/elasticsearch -f.

hamzasa commented 11 years ago

Thanks for reply

I tried sudo supervisorctl status and I got:

sudo supervisorctl status

elasticsearch FATAL Exited too quickly (process log may have details)

graylog-server FATAL Exited too quickly (process log may have details)

graylog-web RUNNING pid 846, uptime 0:24:58

mongodb RUNNING pid 845, uptime 0:24:58

From: Evan Hazlett [mailto:notifications@github.com] Sent: Tuesday, February 19, 2013 7:36 PM To: ehazlett/puppet-module-graylog2 Cc: hamzasa Subject: Re: [puppet-module-graylog2] elasticsearch is not running (#3)

You shouldn't run ./elasticsearch.in.sh. There should be a supervisor config: /etc/supervisor/conf.d/elasticsearch.conf. You should be able to run sudo supervisorctl status to see if it's running and sudo supervisorctl start elasticsearch. Furthermore, if you want to run manually, there will be a bin directory (I believe /opt/elasticsearch/bin) and you can run bin/elasticsearch -f.

— Reply to this email directly or view it on GitHubhttps://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13785834.

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd, its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.

ehazlett commented 11 years ago

Can you post the output of the /var/log/supervisor/elasticsearch* files?

On Tue, Feb 19, 2013 at 12:40 PM, hamzasa notifications@github.com wrote:

Thanks for reply

I tried sudo supervisorctl status and I got:

sudo supervisorctl status

elasticsearch FATAL Exited too quickly (process log may have details)

graylog-server FATAL Exited too quickly (process log may have details)

graylog-web RUNNING pid 846, uptime 0:24:58

mongodb RUNNING pid 845, uptime 0:24:58

From: Evan Hazlett [mailto:notifications@github.com] Sent: Tuesday, February 19, 2013 7:36 PM To: ehazlett/puppet-module-graylog2 Cc: hamzasa Subject: Re: [puppet-module-graylog2] elasticsearch is not running (#3)

You shouldn't run ./elasticsearch.in.sh. There should be a supervisor config: /etc/supervisor/conf.d/elasticsearch.conf. You should be able to run sudo supervisorctl status to see if it's running and sudo supervisorctl start elasticsearch. Furthermore, if you want to run manually, there will be a bin directory (I believe /opt/elasticsearch/bin) and you can run bin/elasticsearch -f.

— Reply to this email directly or view it on GitHub< https://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13785834>.

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd, its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.

— Reply to this email directly or view it on GitHubhttps://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13786130.

hamzasa commented 11 years ago

elasticsearch-stderr---supervisor-00ppbE.log

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

elasticsearch-stdout---supervisor-zsnYgo.log is empty

From: Evan Hazlett [mailto:notifications@github.com] Sent: Tuesday, February 19, 2013 7:59 PM To: ehazlett/puppet-module-graylog2 Cc: hamzasa Subject: Re: [puppet-module-graylog2] elasticsearch is not running (#3)

Can you post the output of the /var/log/supervisor/elasticsearch* files?

On Tue, Feb 19, 2013 at 12:40 PM, hamzasa notifications@github.com wrote:

Thanks for reply

I tried sudo supervisorctl status and I got:

sudo supervisorctl status

elasticsearch FATAL Exited too quickly (process log may have details)

graylog-server FATAL Exited too quickly (process log may have details)

graylog-web RUNNING pid 846, uptime 0:24:58

mongodb RUNNING pid 845, uptime 0:24:58

From: Evan Hazlett [mailto:notifications@github.com] Sent: Tuesday, February 19, 2013 7:36 PM To: ehazlett/puppet-module-graylog2 Cc: hamzasa Subject: Re: [puppet-module-graylog2] elasticsearch is not running (#3)

You shouldn't run ./elasticsearch.in.sh. There should be a supervisor config: /etc/supervisor/conf.d/elasticsearch.conf. You should be able to run sudo supervisorctl status to see if it's running and sudo supervisorctl start elasticsearch. Furthermore, if you want to run manually, there will be a bin directory (I believe /opt/elasticsearch/bin) and you can run bin/elasticsearch -f.

— Reply to this email directly or view it on GitHub<

https://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13785834>.

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd, its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.

— Reply to this email directly or view it on GitHub< https://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13786130>.

— Reply to this email directly or view it on GitHubhttps://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13787252.

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd, its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.

hamzasa commented 11 years ago

With elasticsearch-0.18.6 it's working fine

From: Hamza Salman [mailto:hamza.salman@kenshoo.com] Sent: Wednesday, February 20, 2013 11:16 AM To: 'ehazlett/puppet-module-graylog2' Subject: RE: [puppet-module-graylog2] elasticsearch is not running (#3)

elasticsearch-stderr---supervisor-00ppbE.log

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

/opt/elasticsearch/bin/elasticsearch: 3: /opt/elasticsearch/bin/ elasticsearch.in.sh: Bad substitution

elasticsearch-stdout---supervisor-zsnYgo.log is empty

From: Evan Hazlett [mailto:notifications@github.com] Sent: Tuesday, February 19, 2013 7:59 PM To: ehazlett/puppet-module-graylog2 Cc: hamzasa Subject: Re: [puppet-module-graylog2] elasticsearch is not running (#3)

Can you post the output of the /var/log/supervisor/elasticsearch* files?

On Tue, Feb 19, 2013 at 12:40 PM, hamzasa notifications@github.com wrote:

Thanks for reply

I tried sudo supervisorctl status and I got:

sudo supervisorctl status

elasticsearch FATAL Exited too quickly (process log may have details)

graylog-server FATAL Exited too quickly (process log may have details)

graylog-web RUNNING pid 846, uptime 0:24:58

mongodb RUNNING pid 845, uptime 0:24:58

From: Evan Hazlett [mailto:notifications@github.com] Sent: Tuesday, February 19, 2013 7:36 PM To: ehazlett/puppet-module-graylog2 Cc: hamzasa Subject: Re: [puppet-module-graylog2] elasticsearch is not running (#3)

You shouldn't run ./elasticsearch.in.sh. There should be a supervisor config: /etc/supervisor/conf.d/elasticsearch.conf. You should be able to run sudo supervisorctl status to see if it's running and sudo supervisorctl start elasticsearch. Furthermore, if you want to run manually, there will be a bin directory (I believe /opt/elasticsearch/bin) and you can run bin/elasticsearch -f.

— Reply to this email directly or view it on GitHub<

https://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13785834>.

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd, its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.

— Reply to this email directly or view it on GitHub< https://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13786130>.

— Reply to this email directly or view it on GitHubhttps://github.com/ehazlett/puppet-module-graylog2/issues/3#issuecomment-13787252.

This e-mail, as well as any attached document, may contain material which is confidential and privileged and may include trademark, copyright and other intellectual property rights that are proprietary to Kenshoo Ltd, its subsidiaries or affiliates ("Kenshoo"). This e-mail and its attachments may be read, copied and used only by the addressee for the purpose(s) for which it was disclosed herein. If you have received it in error, please destroy the message and any attachment, and contact us immediately. If you are not the intended recipient, be aware that any review, reliance, disclosure, copying, distribution or use of the contents of this message without Kenshoo's express permission is strictly prohibited.