AXA Issue - Cannot start without exec on /tmp


Article ID: 103298


Updated On:


CA App Experience Analytics


We are experiencing an issue with our AXA environment which needs to have /tmp to have exec permissions, this goes against our internal security polices and as such we need to understand why this is the case, and how we can stop it.
It appears from my investigation that the Elasticsearch component uses the /tmp directory to create a executable file on startup called with the exec on the /tmp fs this fails and the AXA startup doesn't complete.


A number of the AXA components need to use the snappy native libraries. By default the processes will try to run the library from the /tmp folder.


AXA 17.3


The attached is suggested configuration to allow the AXA product to run where /tmp is mounted with noexec by overidding the location of
Suggested folders must be created manually

This will not allow the product to be installed with /tmp as noexec so that restriction will have to be applied once the product is installed.


1558536534551AXA_noexec_temp_configuration.docx get_app