You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everybody, I have an error then I try to start wrapper via service utility under freeBSD 9.0 x64
My steps are:
clone service directory to /opt/elasticsearch/bin/
cd /opt/elasticsearch/bin/service
ee ./elasticsearch.conf
set.default.ES_HOME=/opt/elasticsearch
./elasticsearch install
cd / (for clean experiment)
service elasticsearch start
and I have this:
Starting ElasticSearch...
Waiting for ElasticSearch........................
WARNING: ElasticSearch may have failed to start.
but if I make this:
/opt/elasticsearch/bin/service/elasticsearch start
Starting ElasticSearch...
Waiting for ElasticSearch.......
running: PID:1838
everything is fine. But I need working service way, for autostarting in boot time
PS: Sorry for me English...
The text was updated successfully, but these errors were encountered:
hi
elasticsearch use bash in start script, and in freeBSD bash path different with Debian distribution.
To solve this problem make a link to correct path of bash in FreeBSD. To this purpose run this command in termianl:
root@bsd:~# ln -sf /usr/local/bin/bash /bin/bash
other solution i guess for your problem Elasticsearch will not start if ${prompt.text} or ${prompt.secret} is used in the settings and the process is run as a service or in the background.
Hello everybody, I have an error then I try to start wrapper via service utility under freeBSD 9.0 x64
My steps are:
and I have this:
Starting ElasticSearch...
Waiting for ElasticSearch........................
WARNING: ElasticSearch may have failed to start.
but if I make this:
/opt/elasticsearch/bin/service/elasticsearch start
Starting ElasticSearch...
Waiting for ElasticSearch.......
running: PID:1838
everything is fine. But I need working service way, for autostarting in boot time
PS: Sorry for me English...
The text was updated successfully, but these errors were encountered: