Skip to content

ezaai calculate issue: temp directories being created read only, java errors out when temp files can't be deleted #21

@sam-grinstead

Description

@sam-grinstead

I've been trying to run this software on a test dataset. I can convert my protein sequence files to ezaai databases, no trouble. But when I try to actually calculate the AAI :
java -jar ~/Downloads/EzAAI.jar calculate -t 64 -i EzAAI_dbs/CP040925.1_NCHU2014.db -j EzAAI_dbs/CP097207.1_PR08.db -o EzAAI_test_output

I get:
[MAR 07 14:42:18] EzAAI |: EzAAI - v1.2.3 [Feb. 2024] [MAR 07 14:42:18] EzAAI |: Calculating AAI... [Task 1/1] org.apache.commons.io.IOExceptionList: /tmp/ezaai/b72f86d85f7e7f28_tmp at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:331) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1192) at leb.process.ProcCalcPairwiseAAI.pairwiseMmseqs(ProcCalcPairwiseAAI.java:399) at leb.process.ProcCalcPairwiseAAI.calculateProteomePairWithDetails(ProcCalcPairwiseAAI.java:67) at leb.main.EzAAI.runCalculate(EzAAI.java:511) at leb.main.EzAAI.run(EzAAI.java:689) at leb.main.EzAAI.main(EzAAI.java:725) Caused by: java.io.IOException: Cannot delete file: /tmp/ezaai/b72f86d85f7e7f28_tmp/9614918276263326714 at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1344) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:324) ... 6 more Caused by: java.nio.file.AccessDeniedException: /tmp/ezaai/b72f86d85f7e7f28_tmp/9614918276263326714/pref_0.dbtype at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:90) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) at java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:249) at java.base/sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:110) at java.base/java.nio.file.Files.deleteIfExists(Files.java:1181) at org.apache.commons.io.file.DeletingPathVisitor.visitFile(DeletingPathVisitor.java:161) at org.apache.commons.io.file.DeletingPathVisitor.visitFile(DeletingPathVisitor.java:37) at java.base/java.nio.file.Files.walkFileTree(Files.java:2725) at java.base/java.nio.file.Files.walkFileTree(Files.java:2797) at org.apache.commons.io.file.PathUtils.visitFileTree(PathUtils.java:971) at org.apache.commons.io.file.PathUtils.deleteDirectory(PathUtils.java:434) at org.apache.commons.io.file.PathUtils.delete(PathUtils.java:391) at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1341)

Checking the /tmp directory, the directory created (/tmp/ezaai/b72f86d85f7e7f28_tmp/9614918276263326714 in this case) has permissions:
dr-xr-xr-x. 2 myusername myusername 260 Mar 7 14:42 9614918276263326714

So readable and executable, but not writeable, which extends to the files it contains. The folder containing this folder has write permissions just fine, as does the other folder active when the software errors out (the _faa folder). Any ideas?

OS is RockyLinux 9.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions