We have been happily writing files to our cloud when we started getting the error below. We can no longer write to aws and don't recall any updates to Talend nor aws.
Any ideas?
ERROR <timestamp> org.apache.spark.util.Utils= Aborting task java.lang.UnsatisfiedLinkError: /tmp/snappy-1.1.10-<randum_number>libsnappyjava.so: /tmp/snappy-1.1.10<randum_number>-libsnappyjava.so: failed to map segment from shared object
**Added notes after post**
The /tmp folder was mounted with noexec. But the folder has read/write. Does Talend need to get the /tmp folder remounted without the noexec option?
**Update**
I had to go into the job's Advanced settings and point to a different folder that was not mounted with the noexec option. That worked.
-Djava.io.tmpdir=<some different folder>
Does anyone know where at the project level I can make that change?
The issue was that Talend uses the /tmp folder. Lots of things use the /tmp folder! Security mounted the /tmp folder with noexec per STIGS.
So, the solution is to create a /tmpish folder somewhere else and mount it without the noexec option. Then you have to go into the Advanced tab in the Run portion of the job and add the line below.
I tried adding it to the project preferences under Talend but the job still tried the old /tmp folder.
I don't think it's a perms issue but I did check on the folder. The files are created in the /tmp folder where Talend has full access. They don't hang around and are gone after use.
The issue was that Talend uses the /tmp folder. Lots of things use the /tmp folder! Security mounted the /tmp folder with noexec per STIGS.
So, the solution is to create a /tmpish folder somewhere else and mount it without the noexec option. Then you have to go into the Advanced tab in the Run portion of the job and add the line below.
I tried adding it to the project preferences under Talend but the job still tried the old /tmp folder.
