Elasticsearch stopped service

[mrmarkuz (Markus Neuberger)]

Elasticsearch uses a lot of RAM.

Maybe you can limit the RAM usage:

Zammad ticketing/helpdesk on Nethserver available

It may be too much memory used by elasticsearch, I tested on a VM with 8GB RAM. You could try to limit the memory usage: Don’t cross the 32 GB limit — if you have servers with a lot of memory, it is generally better to run more Elasticsearch nodes than going over the 32 GB limit for maximal heap size. In short, using -Xmx32g or higher results in the JVM using larger, 64-bit pointers that need more memory. If you don’t go over -Xmx31g , the JVM will use smaller, 32-bit pointers by using comp…

[capote (Marko)]

But this memory eating started with the update of ingest-attachment.

That doesn’t seem normal to me. Together with the faulty function, as with Andy, all this does not look healthy.

I’m not motivated to enable the service if he is unusable.

[mrmarkuz (Markus Neuberger)]

Did you already try an older elasticsearch version with according ingest-attachment?