theotherp / nzbhydra2

Usenet meta search
Other
1.23k stars 75 forks source link

Issue with docker container crashing any version after v4.3.0 at startup #838

Open nranasin opened 1 year ago

nranasin commented 1 year ago

I've had issues with starting up the latest linuxserver images the log file shows the following:

Logging wrapper output to /config/logs/wrapper.log

2023-01-30 09:36:01,531 INFO - Determined release type: native

2023-01-30 09:36:01,533 INFO - Starting NZBHydra main process with command line: ./core -Xmx512M -DfromWrapper=true -DinternalApiKey=vygqoiulhtzidrcqwvrj -Dspring.output.ansi.enabled=ALWAYS --nobrowser --datafolder /config in folder /app/nzbhydra2

java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached

at com.oracle.svm.core.thread.PlatformThreads.startThread(PlatformThreads.java:741)

at java.lang.Thread.start0(Thread.java:386)

at java.lang.Thread.start(Thread.java:802)

at com.oracle.svm.core.heap.ReferenceHandlerThread.start(ReferenceHandlerThread.java:54)

at com.oracle.svm.core.graal.snippets.CEntryPointSnippets.initializeIsolate(CEntryPointSnippets.java:292)

at com.oracle.svm.core.JavaMainWrapper$EnterCreateIsolateWithCArgumentsPrologue.enter(JavaMainWrapper.java:383)

2023-01-30 09:36:02,615 WARNING - Unable to read control ID from /config/control.id: [Errno 2] No such file or directory: '/config/control.id'. Falling back to process return code 99

2023-01-30 09:36:02,617 INFO - NZBHydra main process has terminated for shutdown

Rolling back to v4.3.0 always fixes the issue.

theotherp commented 1 year ago

Please post the full nzbhydra2.log.

nranasin commented 1 year ago

Hi,

I don't seem to be generating a nzbhydra2.log file, only the wrapper.log which is attached.

Thanks!

wrapper.log

theotherp commented 1 year ago

Try giving the container more ram, at least until it has started successfully once.

nranasin commented 1 year ago

I increased the xmx to 12288 and it is still crashing:

2023-01-30 12:24:21,597 INFO - Determined release type: native 2023-01-30 12:24:21,598 INFO - Starting NZBHydra main process with command line: ./core -Xmx12288M -DfromWrapper=true -DinternalApiKey=bcfkqdrnfkdsyetjpvsz -Dspring.output.ansi.enabled=ALWAYS --nobrowser --datafolder /config in folder /app/nzbhydra2 2023-01-30 12:24:22,382 WARNING - Unable to read control ID from /config/control.id: [Errno 2] No such file or directory: '/config/control.id'. Falling back to process return code 99 2023-01-30 12:24:22,383 INFO - NZBHydra main process has terminated for shutdown

theotherp commented 1 year ago

Hmm wtf. That's the whole output of the container?

theotherp commented 1 year ago

You didn't limit the memory of the container?

nranasin commented 1 year ago

Yup, its really weird. The only additional info i see not in the wrapper.log is what comes up in Portainer:

java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached

at com.oracle.svm.core.thread.PlatformThreads.startThread(PlatformThreads.java:741)

at java.lang.Thread.start0(Thread.java:386)

at java.lang.Thread.start(Thread.java:802)

at com.oracle.svm.core.heap.ReferenceHandlerThread.start(ReferenceHandlerThread.java:54)

at com.oracle.svm.core.graal.snippets.CEntryPointSnippets.initializeIsolate(CEntryPointSnippets.java:292)

at com.oracle.svm.core.JavaMainWrapper$EnterCreateIsolateWithCArgumentsPrologue.enter(JavaMainWrapper.java:383)
nranasin commented 1 year ago

You didn't limit the memory of the container?

No I didn't. I'm not sure how to check that.

nranasin commented 1 year ago

When checking docker stats: CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 8024e15b6bf4 hydra 86.27% 140.1MiB / 15.5GiB 0.88% 7.32kB / 0B 0B / 7.14MB 15

theotherp commented 1 year ago

I'll look around but I'm kinda at a loss right now.

nranasin commented 1 year ago

Hi @theotherp just wanted to check in and see if you had any advice on this?

theotherp commented 1 year ago

Sorry, no. I'm still checking every once in a while if others have the same problem. The technology I use for these native builds has reached public availability just a short time ago so not many people use it. Therefore experiences with it are limited.

EZEDSEA commented 1 year ago

Seeing the same problem with the latest docker images. Are there any updates on this issue?

theotherp commented 1 year ago

Docker images are not affected. This should be a different issue.

Sorry, I confused the issue. I'm currently moving to another city and don't have time to check this. I'll try to find out more when I'm done.

nranasin commented 1 year ago

Hi @theotherp,

I decided to run a fresh container and still see the same errors. Have you had any chance to take look at this issue?

Many Thanks!

theotherp commented 1 year ago

I found this: https://stackoverflow.com/questions/63214760/uncaught-exception-java-lang-outofmemoryerror-unable-to-create-native-thread-er and https://stackoverflow.com/questions/16789288/java-lang-outofmemoryerror-unable-to-create-new-native-thread

It seems to be a problem on your OS level which is why using a fresh container won't fix it.

nranasin commented 1 year ago

Thank you, I will check into this.

On Mon, Jul 24, 2023 at 10:00 AM theotherp @.***> wrote:

I found this: https://stackoverflow.com/questions/63214760/uncaught-exception-java-lang-outofmemoryerror-unable-to-create-native-thread-er and https://stackoverflow.com/questions/16789288/java-lang-outofmemoryerror-unable-to-create-new-native-thread

It seems to be a problem on your OS level which is why using a fresh container won't fix it.

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/838#issuecomment-1647975925, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5RZDBJGCJWE7I7Y2HLHYDTXRZ5WBANCNFSM6AAAAAAULHRTFE . You are receiving this because you authored the thread.Message ID: @.***>

--

Regards,

Nadeepa Ranasinghe