Tunnelblick freezes when no internet and multiple connections at time used #505
Comments
|
Here is video |
|
@JulyIghor - The Issue Template (the instructions for posting an Issue) asks for the diagnostic info but you did not provide it. I have asked you for the diagnostic information at least six times in #503 and #504. One last time: Please post or attach the diagnostic info obtained by following the instructions at Read Before You Post. |
|
I sent diagnostic here #504 (comment) |
|
This #504 (comment) doesn't help at least in current issue. *Tunnelblick: OS X 10.14.0; Tunnelblick 3.7.7 (build 5150); prior version 3.7.6a (build 5080) 2018-11-15 09:18:43 OpenVPN 2.4.6 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Sep 29 2018 *Tunnelblick: OS X 10.14.0; Tunnelblick 3.7.7 (build 5150); prior version 3.7.6a (build 5080) 2018-11-15 09:18:43 OpenVPN 2.4.6 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Sep 29 2018 |
|
Can confirm the same bug. Pretty annoying. Practically blocks my Macbook. I have to Force Quit Tunnelblick and restart it to get going again. Anything I could help with? |
|
@JulyIghor , @dandaka : Tunnelblick 3.7.9beta02 contains several changes to the way Tunnelblick handles the situation of not having a network connection. Please see if it helps. |
|
@jkbullard Same story. How to reproduce:
|
|
@dandaka - Thanks for your simple instructions. But following them does not freeze Tunnelblick for me. (At least, Tunnelblick doesn't freeze when I connect one VPN. Does it require multiple VPNs to be connected for the problem to happen? That's what the original post described.) You could help by: (A) Getting the diagnostic info for a successful connect/disconnect sequence by following the instructions at Before You Post. Paste the Clipboard into a file to save it for emailing as an attachment (see step 7. below). and (B) Getting a "spin dump" while Tunnelblick is frozen:
Thanks in advance! |
|
Same issue on latest High Sierra with beta2. Happens when moving from one WiFi network to another. Usually after closing my MBP's lid (sleep?) and then physically moving to a new location where I have had a previous connection - usually from home (with VPN connected) and then to work. Or vica versa. So to reproduce, ensure two known WiFi locations then:
|
|
@JulyIghor @dandaka, @darrenmhill, and anyone else having this problem should try two things:
|
|
I'll give those settings a try... |
|
Just to note, I use the OpenVPN client on iOS and have zero issues. Same client settings file. |
|
Just changed to these settings. Restarted my MBP, made a Wifi/VPN connection, then closed the lid. Moved home to a new Wifi/Router connection and now it's just failing again to reconnect ("Making TCP connection", then "Reconnecting"). It's really not liking going from one Wifi connection to another via sleep. The only way to resolve is to restart the Mac and make a new connection. I think the openvpn processes are not resetting/restarting correctly. This is pretty fundamental for a VPN client and it's just not playing ball. I'll wait for the next beta, otherwise I'll be looking for a new solution. |
|
@darrenmhill - Please try to pinpoint the issue:
(Are you using Tunnelblick 3.7.9beta02? That's what you should be using.) |
I did this. 3.7.9beta02 works fine, no freezes. |
|
Sorry, I didn't mean to close this issue until @darrenmhill has had a chance to try to pinpoint the issue he is experiencing. |
|
I have disabled sleep mode to keep MacBook running all the time while I'm out of home.
|
This did not fix the issue for me unfortunately. |
|
|
|
And here:
|
|
I’ve been experimenting with settings and may have found a workaround/solution. Again, my issue is specifically the following:
All above on latest beta2 and Latest High Sierra. |
|
@darrenmhill - Thanks for your report. Here are a bunch of things for you (and others) to try (A) Please try connecting your Mac to the VPN, sleeping it for two or three minutes, and then waking it up in the same location -- that is, without moving it to a new network. Does that work? (B) Please try the following:
Does that second connection work? (C) When you say "Only way to reconnect via VPN is via a full macOS restart", what have you tried? In particular, have you tried turning Wi-Fi off, waiting a few seconds, and then turning it back on? (Or, for an Ethernet connection, unplugging and then plugging it back in?) (D) When Tunnelblick/OpenVPN lock up, can you quit OpenVPN using Activity Monitor? If OpenVPN won't quit normally, can you force quit it? If OpenVPN does quit, does Tunnelblick then start responding or does it stay "frozen"? |
|
Tests A and B work fine (I'm now on beta 3). c) Generally, I'm just sleeping the Mac with a VPN connection, moving to a new location with known Wifi and then letting the VPN reconnect (usually with no success) D) With Activity Monitor, I normally need to force-quit Tunnelblick AND openvpn before I'm able to get connectivity. Starting up tunnelbick again, it fails to connect until a hard restart of macOS. I will try steps C and D again with beta 3 in the next few days. |
|
@darrenmhill - Thanks!
It isn't enough to quit or force-quit only OpenVPN? Tunnelblick should be able to recover if you force-quit OpenVPN, and then you should be able to quit it via the Tunnelblick menu. In that situation (you've quit or force-quit OpenVPN but Tunnelblick is still not responding), please "sample" the Tunnelblick process in Activity Monitor and post the results or email them to developers@tunnelblick.net. |
|
A) Sleeping and reconnecting to the same network is fine. It's only an issue when waking to another available access point (with the previous no longer available). B) This is totally fine, unless the wifi connection is different (and on a different router/location) @jkbullard no force-quitting doesn't fix it - a full restart is required in this situation. I'll get back to you on the logging. All the above has been re-tested on beta3. Note that I'm on a Mid-2010 MBP, running macOS 10.13.6 (17G6015) |
|
@darrenmhill wrote:
(1) Do you need to force quit the "openvpn" process? Or will a regular quit work? (2) If you quit or force-quit the "openvpn" process, does Tunnelblick stop responding (freeze)?
|
|
Same thing... Any chance to fix it? |
|
Hi, I am having the same issue with the version "Tunnelblick 3.8.8a (build 5776)" on MacOS Monterey as well. ( exactly same issue defined in #505 (comment) ) |
As for me, I solved that by switching to Wireguard, there is no issues at all |
|
This problem may have been fixed in Tunnelblick 4.0.0beta05, released yesterday.
|
|
@jkbullard this is still happening with 4.0.0beta09 for me. Losing internet connection while being connected to a VPN freezes Tunnelblick for about 5 minutes. Might be too many reconnection attempts in a short period of time? |
|
@danidoedel - Thanks. For anyone with this problem: it would be helpful to have a "Spin Dump" from Activity Monitor. |
|
@jkbullard here you go: |
|
@danidoedel - Try removing the If that works, here's happening: Your DHCP server issues short leases. When the lease is up, a new lease is issued with its pre-VPN DNS information, so your computer reverts its DNS settings to the pre-VPN settings. Tunnelblick detects that and tells OpenVPN to reconnect. If By removing |
|
@jkbullard unfortunately Tunnelblick still freezes even with Another spindump if that helps: |
Describe the bug
Tunnelblick icon and menus become unrensponsible while no Internet connection, if multiple connections at time used.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Tunnelblick not freeze on Internet disconnected
Screenshots
Diagnostic information
*Tunnelblick: OS X 10.14.0; Tunnelblick 3.7.7 (build 5150); prior version 3.7.6a (build 5080); Admin user
Console Log:
2018-11-14 13:40:21 com.apple.xpc.launchd[1] Service exited due to SIGPIPE | sent by tunnelblickd[83649]
2018-11-14 13:40:25 Tunnelblick[83723] Tunnelblick: OS X 10.14.0; Tunnelblick 3.7.7 (build 5150)
2018-11-14 13:40:26 Tunnelblick[83723] Warning: preferences contain unknown preference 'NSStatusItem Preferred Position Item-0'
2018-11-14 13:40:27 Tunnelblick[83723] DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on dispatch_bug_deprecated to debug
2018-11-14 13:40:34 Tunnelblick[83723] The 'Online/a2.myserver.com 443-notMonitoringConnection' preference was changed to TRUE because that was encoded in the filename of the log file
2018-11-14 13:40:34 Tunnelblick[83723] The 'Online/a1.myserver_.com 443-notMonitoringConnection' preference was changed to TRUE because that was encoded in the filename of the log file
2018-11-14 13:40:34 Tunnelblick[83723] The 'Online/a3.myserver_.com 443-notMonitoringConnection' preference was changed to TRUE because that was encoded in the filename of the log file
2018-11-14 13:40:34 Tunnelblick[83723] Stopped trying to establish communications with an existing OpenVPN process for 'Online/ovpn2.myserver_.com 443' after 5 seconds
2018-11-14 13:40:36 Tunnelblick[83723] Stopped trying to establish communications with an existing OpenVPN process for 'Online/m8.myserver_.com 1194' after 5 seconds
2018-11-14 13:40:37 Tunnelblick[83723] Stopped trying to establish communications with an existing OpenVPN process for 'Online/ovpn1.myserver_.com 443' after 5 seconds
2018-11-14 13:40:38 Tunnelblick[83723] Stopped trying to establish communications with an existing OpenVPN process for 'Online/ovpn3.myserver_.com 443' after 5 seconds
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/m2.myserver_.com 443' account = 'username'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/m2.myserver_.com 443' account = 'password'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt2.myserver_.com' account = 'username'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt2.myserver_.com' account = 'password'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/a1.myserver_.com 443' account = 'username'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/a1.myserver_.com 443' account = 'password'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt3.myserver_.com' account = 'username'
2018-11-14 13:40:41 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt3.myserver_.com' account = 'password'
2018-11-14 13:40:41 Tunnelblick[83723] pthread_mutex_lock( &unloadKextsMutex ) failed; status = 16, errno = 9
2018-11-14 13:40:42 Tunnelblick[83723] pthread_mutex_lock( &unloadKextsMutex ) failed; status = 16, errno = 9
2018-11-14 13:40:42 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt1.myserver_.com' account = 'username'
2018-11-14 13:40:42 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt1.myserver_.com' account = 'password'
2018-11-14 13:40:42 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt5.myserver_.com' account = 'username'
2018-11-14 13:40:42 Tunnelblick[83723] Keychain item retrieved successfully for service = 'Tunnelblick-Auth-Online/mt5.myserver_.com' account = 'password'
The text was updated successfully, but these errors were encountered: