-
-
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
Container stopping without any warning #55
Comments
After some research, I figured that this is coming from openvpn, it looks like if dns is not set (as in the case with Container Station), openvpn just closes without warning. |
Hey. Haven't seen this before. There are no errors anywhere? You're running the container with the --dns flag? You could maybe try to add some more logging using the OPENVPN_OPTS option. |
Closing this for inactivity. Please reopen it if you have more info or questions. |
I am getting this when I run the container:
...
Sun Mar 13 05:41:26 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]93.114.44.187:1194
Sun Mar 13 05:41:28 2016 TUN/TAP device tun0 opened
Sun Mar 13 05:41:28 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sun Mar 13 05:41:28 2016 /sbin/ip link set dev tun0 up mtu 1500
Sun Mar 13 05:41:28 2016 /sbin/ip addr add dev tun0 local 10.126.1.6 peer 10.126.1.5
Sun Mar 13 05:41:28 2016 /etc/transmission/start.sh tun0 1500 1542 10.126.1.6 10.126.1.5 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to tun0 ip: 10.126.1.6
Generating transmission settings.json from env variables
INFO: /dev/random not found - symlink to /dev/urandom
STARTING TRANSMISSION
STARTING PORT UPDATER
Transmission startup script complete.
Sun Mar 13 05:41:29 2016 Initialization Sequence Completed
And then nothing, the container just stops. Any ideas?
I am running it in privilege mode with Google DNS on QNAP Container Station.
I was able to run the previous version (1.6) on a previous QNAP Container Station (1.3) without problem.
Any ideas? Thanks.
The text was updated successfully, but these errors were encountered: