Skip to content
Locking up
Got a problem with Viscosity or need help? Ask here!
I have found recently that Viscosity will lock up and because It doesn't show up as an app its impossible, well for me, to kill it and restart. Which would be OK for me, though obviously I would like it not to lock up.
10.6.8
'Vis 1.3.3
I work on getting the log.
10.6.8
'Vis 1.3.3
I work on getting the log.
Hi world2see,
What do you mean by lock-up? Does the Viscosity menu become unresponsive and not open? Or does all of Viscosity crash?
Are there any error messages or warnings from either Viscosity or OpenVPN in the Console log?
http://www.thesparklabs.com/support/vie ... nsole_log/
Cheers,
James
What do you mean by lock-up? Does the Viscosity menu become unresponsive and not open? Or does all of Viscosity crash?
Are there any error messages or warnings from either Viscosity or OpenVPN in the Console log?
http://www.thesparklabs.com/support/vie ... nsole_log/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
I mean that I get the spinning colour wheel when I hover over the icon. The only solution is to restart it that I found because I can't figure out how to force quite viscosity.
Interestingly I can have a green Icon, in the menu have Servers listed as "connect" but with an orange icon.
Interestingly I can have a green Icon, in the menu have Servers listed as "connect" but with an orange icon.
Hi world2see,
If Viscosity is crashing or becoming unresponsive you should hopefully find a warning or error message in the Console log (please see link posted earlier). Also make sure you are using the latest version of Viscosity (1.3.3 at the time of writing) or the latest beta version (1.3.4b1 at the time of writing).
If you ever need to, you can Quit or Force Quit a background application using the Activity Monitor application (under /Applications/Utilities/Activity Monitor.app).
Cheers,
James
If Viscosity is crashing or becoming unresponsive you should hopefully find a warning or error message in the Console log (please see link posted earlier). Also make sure you are using the latest version of Viscosity (1.3.3 at the time of writing) or the latest beta version (1.3.4b1 at the time of writing).
If you ever need to, you can Quit or Force Quit a background application using the Activity Monitor application (under /Applications/Utilities/Activity Monitor.app).
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
I have had this problem with Viscosity for a long time, across two different Macbook pros. Exactly as OP described - Viscosity beachballs and then the system can't gracefully restarted at that point. I tend to leave the VPN up for long periods. But it's not a predictable failure. I could go weeks on a VPN connection or have it fail once in 12 hours.
Post Lion update it is still happening. Version 1.3.4 - just happened.
There is hardly any logs in Console, because the firewall apparently turned itself back on after Lion. I had disabled it in Snow Leopard and forgot to report the issue here but not sure it's a Viscosity problem. Something about the VPN & corporate firewall combination we have, causes the Mac firewall to spam logs. Therefore whatever messages openvpn would send to logger don't stay around long. example
8/3/11 5:19:03.970 PM Firewall: Stealth Mode connection attempt to UDP 10.0.X.X:53169 from X.X.X.X:3964
Those at a rate of 2 logs every 1 second.
So I turned off the firewall due to the volume of that. It is a secondary issue, that is some corp firewall packet mangling issue, rather than an issue with OpenVPN... but in any case I have exhibited the primary issue, same behavior described in this post.
Post Lion update it is still happening. Version 1.3.4 - just happened.
There is hardly any logs in Console, because the firewall apparently turned itself back on after Lion. I had disabled it in Snow Leopard and forgot to report the issue here but not sure it's a Viscosity problem. Something about the VPN & corporate firewall combination we have, causes the Mac firewall to spam logs. Therefore whatever messages openvpn would send to logger don't stay around long. example
8/3/11 5:19:03.970 PM Firewall: Stealth Mode connection attempt to UDP 10.0.X.X:53169 from X.X.X.X:3964
Those at a rate of 2 logs every 1 second.
So I turned off the firewall due to the volume of that. It is a secondary issue, that is some corp firewall packet mangling issue, rather than an issue with OpenVPN... but in any case I have exhibited the primary issue, same behavior described in this post.
Hi newchaos,
Thanks for the additional information. I haven't managed to replicate this one yet, but I'll stay on it. If it is happening without you interacting with Viscosity at all (is this the case?), then it's probably related to Viscosity detecting a network change and getting stuck for some reason. If there are any additional details or log messages anyone can offer please send them along!
Cheers,
James
Thanks for the additional information. I haven't managed to replicate this one yet, but I'll stay on it. If it is happening without you interacting with Viscosity at all (is this the case?), then it's probably related to Viscosity detecting a network change and getting stuck for some reason. If there are any additional details or log messages anyone can offer please send them along!
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
6 posts
Page 1 of 1