-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
When userSetup.sh
Permission Setting takes too long the Container will infinitely restart
#2532
Comments
Any reason why this would take so long? I can’t replicate this, it occurs instantaneous nearly in my setup |
A slow drive, which is slowed down additionally by a copy-on-write filesystem, which takes too many hardware resources, compared to the hardware provided. I debugged this by opening a clean container, slowly applying all my settings step by step. If you want to replicate it, just mount an SSHFS file system to a remote target with lots of small files in it. For example, extract an Ubuntu DVD onto the remote folder, which is mounted locally & then use this as the data folder for this repository's stack. |
I have also experienced issues similar to this, but did not report because I am sub–one year into Docker and presumed user error. I am using Docker Swarm across nine single-board computers, but have one of those nine nodes dedicated to this container. The web UI freaks out with each automatic refresh if I run the image across multiple nodes in the swarm. The application files are running on the node's SD card and download folder is an NFS drive on the same internal network. I've found that the Below is my
|
For those of you dealing with a similar issue, I can expand upon the workaround discovered by @theAkito.
This fixed the issue for me, but your mileage may vary. Hope this helps someone else; big thanks for @theAkito for the initial report. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still relevant. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I just faced this same issue recently, the transmission UI won't come up and I was unable I'm running an EXT4 FS on a healthy HDD over NFS and this had been working with no issues for over 2 years. |
Would like to add that this is still an ongoing issue. Took me forever to debug as well because it's not apparent what is causing the timing out. |
how can I fix this in unraid? |
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
Undisclosed
Current Behavior
When setting the permissions here
docker-transmission-openvpn/transmission/userSetup.sh
Lines 49 to 72 in f9cb4de
takes longer, than 120 seconds, then OpenVPN will get a ping-restart after the permission job finished & the container will restart.
Expected Behavior
No OpenVPN issue should happen, when setting permissions takes longer than 120 seconds.
Or at least provide a useful error message. The current messages are extremely cryptic & basically don't say anything about what actually is not working.
How have you tried to solve the problem?
Workaround
Set
GLOBAL_APPLY_PERMISSIONS=false
as an environment variable to the container. It will skip setting the permissions.Log output
HW/SW Environment
Anything else?
I am currently using the workaround provided. It's good enough for now. However, it would be great, to fix the issue, or at least provide a useful error message in the logs. The current error messages are extremely generic & do not help at all in debugging the issue.
The text was updated successfully, but these errors were encountered: