Open cron2 opened 1 week ago
(technically this is not quite likely "an OpenVPN" issue but "lwipovpn", but I put it in here because I'm looking at this from the OpenVPN testing point of view...)
strace.log attached. Tested with https://github.com/mattock/openvpn/blob/lwip_debug/tests/lwip.sh except that client was launched like this:
strace -o /tmp/strace.log -f ../src/openvpn/openvpn --client --nobind --remote-cert-tls server --persist-tun --verb 3 --resolv-retry infinite --connect-retry-max 3 --server-poll-timeout 5 --explicit-exit-notify 3 --script-security 2 --dev null --dev-node unix:lwipovpnbuild/lwipovpn --up ./null_client_up.sh --ca ./../sample/sample-keys/ca.crt --cert ./../sample/sample-keys/client.crt --key ./../sample/sample-keys/client.key --tls-auth ./../sample/sample-keys/ta.key 1 --remote 127.0.0.1 1194 udp --proto udp --writepid lwip_client.pid --setenv pid lwip_client.pid --log lwip_client.log </dev/null
So, t_client test with lwipovpn. Works great if run from the CLI, log file visible.
Running with stdin (only!) redirected
leads to
so, lwipovpn seems to die/crash right away. This is on FreeBSD 13.3, but @mattock seems to experience the same thing on Linux.
Running truss...
this is a bit inconclusive (there is no actual error, and I can't see "what other threads do") - and then
truss
just exits?! - so "something inlwipovpn
acts up if stdin is not a tty? (</tmp/somefile.txt
has the same effect).Maybe strace on Linux is more helpful here? Or just stare-at-code ;-)