[Support] Djoss - HandBrake


Recommended Posts

  • 3 weeks later...

Hi,
I'm trying to limit the memory available to the container using --memory=4G but this results in an error: set_mempolicy: Operation not permitted and the conversion process ends prematurely.

If I try in privileged mode it resolves the error but the conversion still ends prematurely.

If i remove --memory=4G then both the error is resolved and the conversion process runs properly.

Any idea what is going on?
 

Link to comment
  • 4 weeks later...
  • 3 weeks later...
On 5/4/2023 at 7:53 PM, ApfelBirneKreis said:

Yes i did. and the dev-latest tag does not work anymore. last time it was updated is a very long time ago

 

Forgot to reply here, but nightly builds are working again.

Link to comment
23 hours ago, Djoss said:

 

Forgot to reply here, but nightly builds are working again.

So I tried the nightly build and I'm getting approximately 50% slower encodes on the nightly build compared to the latest build.  Are nightly builds of handbrake inherently slower or do you think theres an issue on my side?

 

I timed it and by a set amount of time latest was at 10.2% complete, and on the exact same file, exact same encoding settings, nightly was at 5.5% complete.  Still waiting for nightly to finish its run so I can collect the activity logs.

Link to comment
On 5/23/2023 at 9:36 AM, Gunny said:

Are nightly builds of handbrake inherently slower or do you think theres an issue on my side?

 

It's probably an issue with HandBrake itself...

Link to comment
Posted (edited)

Using v1.6.1 and while auto processing of watch queues is working to encode files, it's no longer removing them from the watch directory on successful completion. Anyone else seeing this? It's worked great for years, but this is gumming up my process now and have to delete files manually (my script won't populate a new one until it's empty). AUTOMATED_CONVERSION_KEEP_SOURCE is still set to 0.

 

I've also noticed as new items are added manually to the watch folder they are not getting processed. I have to restart the container to get it to start converting. Nothing in the logs showing any issues. Auto conversion process is pretty much dead at this point.

Edited by snowboardjoe
Link to comment
On 5/31/2023 at 8:09 AM, snowboardjoe said:

Using v1.6.1 and while auto processing of watch queues is working to encode files, it's no longer removing them from the watch directory on successful completion. Anyone else seeing this? It's worked great for years, but this is gumming up my process now and have to delete files manually (my script won't populate a new one until it's empty). AUTOMATED_CONVERSION_KEEP_SOURCE is still set to 0.

 

I've also noticed as new items are added manually to the watch folder they are not getting processed. I have to restart the container to get it to start converting. Nothing in the logs showing any issues. Auto conversion process is pretty much dead at this point.

 

This was resolved by rebooting the UNRAID host. Unknown on root cause of this. HB now completes the post processing steps after successfully auto encoding a file. The workaround (until I rebooted) was to manually clear the watch folder, stage a few file and then restart HB to have it start encoding again. Guessing this is an UNRAID OS  (v6.11.5) or Docker bug.

Link to comment
On 4/4/2023 at 3:41 AM, supawiz6991 said:

Hi,
I'm trying to limit the memory available to the container using --memory=4G but this results in an error: set_mempolicy: Operation not permitted and the conversion process ends prematurely.

If I try in privileged mode it resolves the error but the conversion still ends prematurely.

If i remove --memory=4G then both the error is resolved and the conversion process runs properly.

Any idea what is going on?
 

Still looking for a resolution to this.

Link to comment
23 hours ago, Gunny said:

Do you have multiple NUMA nodes?

I had to look up what NUMA nodes was as this as a new concept for me. I've done nothing with NUMA Nodes and running Numactl --hardware says:

available: 1 nodes (0)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11
node 0 size: 32028 MB
node 0 free: 6008 MB
node distances:
node   0
  0:  10

If I'm interpreting this correctly, then I do not have multiple NUMA Nodes.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.