Hi, On Fri, Feb 12, 2016 at 09:29:39AM -0500, Selva Nair wrote: > > Since we know where we're sending the log file to, some enhancement to > > the GUI to just go read that file in case the management interface fails > > to connect (after <x> seconds?) would be good for troubleshooting. > > > > This is tricky..First, if the config is not readable, log file is not set > at that time and log goes to stdout (mapped to "/dev/null" by the GUI). > Even otherwise parsing the log to figure out what went wrong is not always > an easy task for a program.
I'm not sure this description is fully correct - doesn't the GUI (via
service) pass the log file before --config with the remaining options?
"--log" is effective immediately, so a non-readable config file should
be in there. At least on linux:
gert@blue:/tmp > touch openvpn.conf
gert@blue:/tmp > chmod 000 openvpn.conf
gert@blue:/tmp > openvpn --log mylog.txt --config openvpn.conf
gert@blue:/tmp > tail mylog.txt
Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn.conf
Use --help for more information.
... the log file has useful information (well, it could log the reason
why opening wasn't possible, but at least something is there)
> However, the GUI does timeout after 10 seconds or so, if the management
> interface doesn't come up. But the log will be empty if openvpn exited
> before stdout was redirected.
Yes, the GUI times out, and the user has no idea what went wrong. Especially
for config file errors. This needs improvement.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
