-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transcoding failure: EAE watchfolder is not writable #334
Comments
Make sure config folders are set to permission 0777. Avoid using SMB for config, transcode, codecs. Use cephs if possible. See #335 |
I am using CephFS. |
@craigcabrey The fix for this is to create multiple temp folders in cepfs. Then create multiple workers with different names. constrict each worker and pms to a single replica and locked to specific nodes. Make sure your tmp folders have write permissions. Adapt to your enviroment and add appropriate volume mappings. You don't even need to do this in ceph you can do it in local volumes, because you’re constraining your containers to a specific node. This sounds counter intuitive since you’re either using K8 or swarm, but it's what I found worked. If you share tmp folders you will run into conflicts. Docker Swarm Stack - Sry I don’t use K8
|
IIRC |
Describe the bug
Intermittently seeing errors of
EAE watchfolder is not writable
in the worker logs. I'm not able to reliably reproduce it. Seems to be a potential re-occurrence of #244.Additional context
The error is misleading though, since that user can write to tmp:
The text was updated successfully, but these errors were encountered: