Because before i saw some user have problem after upgrade to the latest version.
My question is now is the elasticsearch version 7 with with ingest-attachment plugin is compatible in zammad 2.9 or 3.1
Now our server running on elasticsearch 5.6.16 version. it is possible to update? or upgrade for zammad? if yes requesting for your kind assistance how to upgrade for zammad.
yeah its been a while, but i always monitor the latest update on zammad… and nice work zammad team…our 2.9 version runs smoothly sometimes we have an error but its solved by searchindex:rebuild or restarting all the services. i saw all new commit on GitHub and preparing for update to zammad 3.1 or wait for the 3.2 also to upgrade the elasticserch .
@MrGeneration thank you Sir for clarifications and prompt response…
After upgrading from 5.6 to 6.8 I’m getting the following error: warning: Falling back to java on path. This behavior is deprecated. Specify JAVA_HOME
Elasticsearch won’t start—did I do anything wrong?
Elasticsearch won’t start (since upgrading to 6.8), though. Any ideas?
â—Ź elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-12-13 15:01:56 CET; 6h ago
Docs: http://www.elastic.co
Process: 2075 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 2075 (code=exited, status=1/FAILURE)
Dec 13 15:01:55 portal systemd[1]: Started Elasticsearch.
Dec 13 15:01:55 portal elasticsearch[2075]: warning: Falling back to java on path. This behavior is deprecated. Specify JAVA_HOME
Dec 13 15:01:56 portal systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 15:01:56 portal systemd[1]: elasticsearch.service: Unit entered failed state.
Dec 13 15:01:56 portal systemd[1]: elasticsearch.service: Failed with result 'exit-code'.