On Thu, 2009-12-17 at 09:21 +0100, Ferry Toth wrote: > I am on Karmic. > > Actually if a try multiple times to connect after 3 attempts (or so) it > will connect. > > Tried the suggestion below, but Karmic also does not use libexec. I have > no idea how to start up the service on Karmic. Any suggestions?
/usr/lib/network-manager-openvpn/nm-openvpn-service or on 64-bit systems I assume it is: /usr/lib64/network-manager-openvpn/nm-openvpn-service use those with OPENVPN_DEBUG=1 for the detailed logs. Dan > Ferry > > Op woensdag 16-12-2009 om 17:27 uur [tijdzone -0800], schreef Dan > Williams: > > On Sun, 2009-12-06 at 22:55 +0100, Ferry Toth wrote: > > > I confirm this issue. > > > > > > However in my sometimes NM connects to the vpn (openvpn) without > > > problems and sometimes is doesn't. This does not depend on the openvpn > > > server as other machines work fine,as well a previous version of > > > nm-applet. > > > > > > I my case I have a CA cert, a certificate and a key cert (which does > > > not need a password). > > > > > > It may be a problem with the state machine of the networkwork manager? > > > > If you want more information about the problem, you can (as root): > > > > 1) killall -TERM nm-openvpn-service > > 2) OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service > > (or wherever it's at on your system, Debian doesn't use libexec) > > > > and then try to connect. It'll spew out a load of debugging information > > which is necessary to figure out what's going wrong. > > > > Dan > > > > > > _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list