Multiple Copies of Viscosity Helper

Got a problem with Viscosity or need help? Ask here!

mark143

Posts: 19
Joined: Wed Aug 03, 2011 6:58 am

Post by mark143 » Sat Jul 07, 2012 8:52 am
Hi James!

When will be this corrected? I'm getting hundreds of copies running simultaneously again when I tried the b4 of ver 1.4

It somehow stopped bugging us in ver 1.35 I don't know what happened there. This going to be a big issue since it hogs system resources

Mark

James

User avatar
Posts: 2102
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sat Jul 07, 2012 6:00 pm
Hi Mark,

I'll move this one to support. I'm afraid unfortunately it's never something we've every heard of besides your case, so we've been completely unable to replicate it. A few things I'd suggest:

1. Try disabling DNS support for your connection and then try connecting. I'd hazard a guess that Viscosity might be fighting for control of DNS on your system. Do you have any software that could be interfering with Viscosity's control of DNS? Things like OpenDNS's DNSCrypt application are known to be incompatible.

2. Try checking the Console log for any messages from Viscosity, OpenVPN, or from other processes around the same time this is happening. You may prefer to send a copy of the log along to us via email (to save posting details publicly).
http://www.thesparklabs.com/support/vie ... nsole_log/

3. Does the same thing happen with newer versions of the 1.4 beta?

Cheers,
James
James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

mark143

Posts: 19
Joined: Wed Aug 03, 2011 6:58 am

Post by mark143 » Sun Jul 08, 2012 9:30 am
I'm using opendns servers. This is only happening from time to time in Vuze & Transmission. It is also happening in ver 1.4

mark143

Posts: 19
Joined: Wed Aug 03, 2011 6:58 am

Post by mark143 » Sat Jul 14, 2012 11:29 pm
I removed opendnscrypt. So far no problem

pm47

Posts: 1
Joined: Sat Jul 28, 2012 2:38 pm

Post by pm47 » Sat Jul 28, 2012 2:46 pm
I see this too with Mountain Lion OS X 10.8 (12A269) and Viscosity 1.4 (1070). I upgraded Viscosity just after upgrading to Mountain Lion, and then the first time I connected on VPN I got this in the logs:

2012-07-28 12:23:35.408 AM openvpn[854]: OpenVPN 2.3_alpha2 i386-apple-darwin10.8.0 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110522-1 (2.2.0)] built on Jul 24 2012
2012-07-28 12:23:38.088 AM Viscosity[686]: [QL] QLError(): +[QLSeamlessDocumentOpener seamlessDocumentOpenerForURL:] should only be called in the main thread
2012-07-28 12:23:38.090 AM Viscosity[686]: [QL] QLError(): -[QLSeamlessDocumentOpener showWindow:contentFrame:withBlock:] should only be called in the main thread
2012-07-28 12:23:51.734 AM openvpn[855]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
2012-07-28 12:23:51.790 AM openvpn[855]: Attempting to establish TCP connection with [AF_INET]nn.nn.nn.nn:443 [nonblock]
2012-07-28 12:23:52.792 AM openvpn[855]: TCP connection established with [AF_INET]nn.nn.nn.nn:443
2012-07-28 12:23:52.792 AM openvpn[855]: TCPv4_CLIENT link local: [undef]
2012-07-28 12:23:52.793 AM openvpn[855]: TCPv4_CLIENT link remote: [AF_INET]nn.nn.nn.nn:443
2012-07-28 12:23:52.818 AM openvpn[855]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2012-07-28 12:23:53.477 AM openvpn[855]: [tap0] Peer Connection Initiated with [AF_INET]nn.nn.nn.nn:443
2012-07-28 12:24:00.335 AM openvpn[855]: viscosity_foreign_option_2=dhcp-option DNS nn.nn.nn.nn
2012-07-28 12:24:00.335 AM openvpn[855]: viscosity_foreign_option_3=dhcp-option DOMAIN ott.qnx.com
2012-07-28 12:24:00.336 AM openvpn[855]: NOTE: setsockopt TCP_NODELAY=1 failed (No kernel support)
2012-07-28 12:24:00.336 AM openvpn[855]: TUN/TAP device /dev/tap0 opened
2012-07-28 12:24:00.337 AM openvpn[855]: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
2012-07-28 12:24:00.337 AM openvpn[855]: /sbin/ifconfig tap0 delete
2012-07-28 12:24:00.348 AM openvpn[855]: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2012-07-28 12:24:00.349 AM openvpn[855]: /sbin/ifconfig tap0 nn.nn.nn.nn netmask 255.255.248.0 mtu 1500 up
2012-07-28 12:24:00.000 AM kernel[0]: tuntap: Fixing address family for tap0
2012-07-28 12:24:00.408 AM openvpn[855]: Initialization Sequence Completed
2012-07-28 12:24:01.132 AM Viscosity[865]: Changing DNS Servers
2012-07-28 12:24:01.232 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:01.360 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:01.385 AM Viscosity[865]: Flushing DNS
2012-07-28 12:24:01.415 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:02.443 AM Viscosity[874]: Changing DNS Servers
2012-07-28 12:24:02.582 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:02.643 AM Viscosity[880]: Changing DNS Servers
2012-07-28 12:24:02.645 AM Viscosity[878]: Changing DNS Servers
2012-07-28 12:24:02.813 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:02.870 AM Viscosity[874]: Flushing DNS
2012-07-28 12:24:02.919 AM Viscosity[880]: Flushing DNS
2012-07-28 12:24:03.002 AM Viscosity[878]: Flushing DNS
2012-07-28 12:24:03.287 AM mDNSResponderHelper[919]: do_mDNSInterfaceAdvtIoctl: ioctl call SIOCGIFINFO_IN6 failed - error (22) Invalid argument
2012-07-28 12:24:03.662 AM Viscosity[890]: Changing DNS Servers
2012-07-28 12:24:03.696 AM Viscosity[910]: Changing DNS Servers
2012-07-28 12:24:03.755 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:03.894 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:03.919 AM Viscosity[890]: Flushing DNS
2012-07-28 12:24:03.948 AM Viscosity[910]: Flushing DNS
2012-07-28 12:24:04.709 AM Viscosity[934]: Changing DNS Servers
2012-07-28 12:24:04.723 AM Viscosity[942]: Changing DNS Servers
2012-07-28 12:24:04.811 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:04.967 AM Viscosity[934]: Flushing DNS
2012-07-28 12:24:04.980 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:05.044 AM Viscosity[942]: Flushing DNS
2012-07-28 12:24:05.794 AM Viscosity[963]: Changing DNS Servers
2012-07-28 12:24:05.855 AM Viscosity[969]: Changing DNS Servers
2012-07-28 12:24:05.880 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:06.030 AM Viscosity[963]: Flushing DNS
2012-07-28 12:24:06.049 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:06.100 AM Viscosity[969]: Flushing DNS
2012-07-28 12:24:06.937 AM Viscosity[986]: Changing DNS Servers
2012-07-28 12:24:06.998 AM Viscosity[995]: Changing DNS Servers
2012-07-28 12:24:07.030 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB
2012-07-28 12:24:07.185 AM configd[18]: network changed: v4(en0:10.0.1.2) DNS! Proxy SMB

... and on it goes. I ended up with about 100 Viscosity Helper process and both CPUs maxed. When I killed Viscosity, they all exited.

Is there a workaround?

Thanks.

James

User avatar
Posts: 2102
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Sat Jul 28, 2012 4:15 pm
James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
6 posts Page 1 of 1