You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems the /tmp/ovpnxtract can be left created, and therefore prevent the container for starting up.
Expected Behavior
There should be a check in the config to see if the directory already exists.
How have you tried to solve the problem?
Removing/Re-adding the container.
Log output
Starting container with revision: 81277fb
TRANSMISSION_HOME is currently set to: /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: OVPN
Running with VPN_CONFIG_SOURCE auto
Provider OVPN has a bundled setup script. Defaulting to internal config
Executing setup script for OVPN
creating temp folder
mkdir: cannot create directory '/tmp/ovpnxtract/': File exists
just submitted a quick fix to the dev branch for the ovpn script..please check when it has finished building on the dev branch
I'm afraid the quick fix will work once, when no folder will be present, there will be an error resulting the script to exit before completion.
something like [[ ! -d /tmp/ovpnxtract/ ]] && mkdir /tmp/ovpnxtract/ || true should fix the problem.
Yeah this is just bizarre and I didn't find an issue with my original script.
It occurs for me whenever OVPN crashes and it tries to rexonnect. Restarting the container results in this issue. I ended up just making a down detector cronjob to remove the container and readd it when it's down.
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
docker run --cap-add=NET_ADMIN -d
-v /XYZ/Transmission:/data
-v /XYZ/Transmission:/config
-e OPENVPN_PROVIDER=OVPN
-e OPENVPN_CONFIG=standard.se.stockholm.tcp.ovpn
-e OVPN_PROTOCOL=tcp
-e OVPN_COUNTRY=se
-e OVPN_CITY=stockholm
-e OVPN_CONNECTION=standard
-e OPENVPN_USERNAME=
-e OPENVPN_PASSWORD=
-e LOCAL_NETWORK=1.2.3.4/24
-e TRANSMISSION_RPC_USERNAME=
-e TRANSMISSION_RPC_PASSWORD=
-e TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true
--log-driver json-file
--log-opt max-size=10m
-p 1234:1234
haugene/transmission-openvpn
(Ports, IPs, locations, etc, have been hidden)
Current Behavior
It seems the /tmp/ovpnxtract can be left created, and therefore prevent the container for starting up.
Expected Behavior
There should be a check in the config to see if the directory already exists.
How have you tried to solve the problem?
Removing/Re-adding the container.
Log output
Starting container with revision: 81277fb
TRANSMISSION_HOME is currently set to: /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: OVPN
Running with VPN_CONFIG_SOURCE auto
Provider OVPN has a bundled setup script. Defaulting to internal config
Executing setup script for OVPN
creating temp folder
mkdir: cannot create directory '/tmp/ovpnxtract/': File exists
HW/SW Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: