Hi Priya,
the container you trying to interactivily executing a command with is no
longer running. It is not possible to execute command with stopped
containers.
The logger issues might be related to missing file system permissions.
But thats a wild guess. Is there a "Caused by" part in the
Hi All,
When i am trying to execute bash command inside manifoldcf container
getting error.
[image: image.png]
And when checking logs Sudo docker logs
2019-12-19 18:09:05,848 Job start thread ERROR Unable to write to stream
logs/manifoldcf.log for appender MyFile
2019-12-19 18:09:05,848 Seeding
Hi Markus,
Many thanks for your reply!!.
I tried this approach to reproduce the scenario in a different environment,
but the case where I listed the error above is when I am crawling INTRANET
sites which can be accessible over a remote server. Also I have used
Transformation connectors:-Allow
Hi Priya,
in my experience, i would focus on the OutOfMemoryError (OOME).
8 Gigs can be enough, but they don't have to.
At first i would check if the jvm is really getting the desired heap
size. The dockered environment make that a little harder find find out,
since you need to get access to the
Hi Markus ,
Heap size defined is 8GB. Manifoldcf start-options-unix file Xmx etc
parameters is defined to have memory 8192mb.
It seems to be an issue with memory also, and also when manifoldcf tries to
communicate to Database. Do you explicitly define somewhere connection
timer when to
Hi Priya,
your manifoldcf JVM suffers from high garbage collection pressure:
java.lang.OutOfMemoryError: GC overhead limit exceeded
What is your current heap size?
Without knowing that, i suggest to increase the heap size. (java -Xmx...)
Cheers,
Markus
Am 20.12.2019 um 09:02 schrieb Priya
