When `userSetup.sh` Permission Setting takes too long the Container will infinitely restart

[theAkito]

Is there a pinned issue for this?

• [X] I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

• [X] I have searched the existing issues
• [X] I have searched the existing discussions

Is there any comment in the documentation for this?

• [X] I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

• [X] I have checked the provider repo for issues
• [X] My issue is NOT related to a provider

Are you using the latest release?

• [X] I am using the latest release

Have you tried using the dev branch latest?

• [ ] I have tried using dev branch

Docker run config used

Undisclosed

Current Behavior

When setting the permissions here

https://github.com/haugene/docker-transmission-openvpn/blob/f9cb4dea2da1a3aa63bd3945e0162c9b8a9789a4/transmission/userSetup.sh#L49-L72

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

[Secure-Server] Peer Connection Initiated with .....
...
...
...
Initialization Sequence Completed
...
...
...
resolv.conf was restored
Sending kill signal to transmission-daemon
/etc/transmission/stop.sh: line 16: kill: `': not a pid or valid job spec
Successfuly closed transmission-daemon
...
...
...
SIGTERM[hard,] received, process exiting

HW/SW Environment

Not related

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.