Lewis John McGibbney created TIKA-3452:
------------------------------------------
Summary: java.nio.file.FileSystemException Read-only file system
in 2.0.0-BETA tika-docker
Key: TIKA-3452
URL: https://issues.apache.org/jira/browse/TIKA-3452
Project: Tika
Issue Type: Bug
Components: docker
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
Fix For: 2.0.0
The following ExecutionException is thrown when I attempt to run [tika-docker
2.0.0-BETA|https://hub.docker.com/layers/apache/tika/2.0.0-BETA-full/images/sha256-2d735f7bdf86e618a5390d92614a310697f9134d11a2b2e4c1c0cfcde1f68b1d?context=explore]
{code:bash}
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
java.util.concurrent.ExecutionException: java.nio.file.FileSystemException:
/tmp/apache-tika-server-forked-tmp-8374629799942405236: Read-only file system
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at
org.apache.tika.server.core.TikaServerCli.mainLoop(TikaServerCli.java:116)
at
org.apache.tika.server.core.TikaServerCli.execute(TikaServerCli.java:88)
at org.apache.tika.server.core.TikaServerCli.main(TikaServerCli.java:66)
Caused by: java.nio.file.FileSystemException:
/tmp/apache-tika-server-forked-tmp-8374629799942405236: Read-only file system
at
java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:100)
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.newByteChannel(UnixFileSystemProvider.java:219)
at java.base/java.nio.file.Files.newByteChannel(Files.java:375)
at java.base/java.nio.file.Files.createFile(Files.java:652)
at
java.base/java.nio.file.TempFileHelper.create(TempFileHelper.java:137)
at
java.base/java.nio.file.TempFileHelper.createTempFile(TempFileHelper.java:160)
at java.base/java.nio.file.Files.createTempFile(Files.java:917)
at
org.apache.tika.server.core.TikaServerWatchDog$ForkedProcess.<init>(TikaServerWatchDog.java:220)
at
org.apache.tika.server.core.TikaServerWatchDog$ForkedProcess.<init>(TikaServerWatchDog.java:210)
at
org.apache.tika.server.core.TikaServerWatchDog.call(TikaServerWatchDog.java:117)
at
org.apache.tika.server.core.TikaServerWatchDog.call(TikaServerWatchDog.java:50)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)
{code}
There are differences/improvements in the way the [tika-server child process is
spawned|https://cwiki.apache.org/confluence/display/TIKA/TikaServer#TikaServer-MakingTikaServerRobusttoOOMs,InfiniteLoopsandMemoryLeaks]
in the 2.0.0-BETA docker image. I am investigating a fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
