IBM Support

Logstash 6.3.2 unable to start with error: Error accessing temp directory

Troubleshooting


Problem

Logstash 6.3.2 unable to start successfully. The error is:

[ERROR] [LogStash::Runner] Logstash - java.lang.IllegalStateException: Logstash stopped processing because of an error: (LoadError) Could not load FFI Provider: (NotImplementedError) FFI not available: java.lang.UnsatisfiedLinkError: /tmp/jffi1122334455667788990.so (/tmp/jffi1122334455667788990.so: failed to map segment from shared object: Operation not permitted)

 .

.

.

Error accessing temp directory: /tmp

This often occurs because the temp directory has been mounted with NOEXEC or

the Logstash user has insufficient permissions on the directory. Possible workarounds include setting the -Djava.io.tmpdir property in the jvm.options file to an alternate directory or correcting the Logstash user's permissions.

logstash not running

Cause

The temp directory that you are trying to use was mounted with NOEXEC

Diagnosing The Problem

You can run the mount command to find out whether the temp directory that you are using was mounted with NOEXEC.

Resolving The Problem

You can resolve this issue by:
1) Re-mount the temp directory as EXEC.
or
2) You can point Logstash to access an alternative directory mounted with EXEC by:

2.1) Goto your logstash-6.3.2/bin directory and edit logstash

2.2) Add the following lines in BOLD:

#  LS_JAVA_OPTS="xxx" to append extra options to the JVM options provided by logstash

LS_JAVA_OPTS="-Djava.io.tmpdir=\"<directory name>\""

where <directory name> is the new directory

2.3) Restart Logstash.

Document Location

Worldwide

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPFMY","label":"IBM Operations Analytics - Log Analysis"},"Component":"Logstash","Platform":[{"code":"PF016","label":"Linux"}],"Version":"Logstash 1.3.5.3, Logstash 6.3.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

LA

Document Information

Modified date:
07 February 2023

UID

ibm11283158