Author Topic: Avast beta for mac randomly breaks http connections  (Read 8763 times)

0 Members and 1 Guest are viewing this topic.

Offline bedge

  • Newbie
  • *
  • Posts: 8
Avast beta for mac randomly breaks http connections
« on: June 09, 2011, 04:50:56 PM »
After running with this new beta mac version (110609-0), yesterday ALL http/https connections to external servers started failing. I could still hit machines in my local LAN, but everything else started timing out.

After 5 hours of debugging & hair pulling, I disabled avast web shield and viola` everything was fine again.

Avast web shield is off for now.

Also, in an unrelated lower prio nit, avast clogs up the logs with filesystem events like:

6/9/11 7:40:53 AM   kernel   AvastFileShield: Req 36752: /Users/bedge/Documents/Microsoft User Data/Office 2011 Identities/Main Identity/Data Records/Message Sources/0T/0B/1M/136K/x27_1136536 (reason 0x2)

over and over.

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Avast beta for mac randomly breaks http connections
« Reply #1 on: June 14, 2011, 11:43:38 AM »
Please run the following command from terminal and post the output here, or send it to my email

Code: [Select]
cat /var/log/system.log | grep 'proxy\[[0-9]*\]'

Offline bedge

  • Newbie
  • *
  • Posts: 8
Re: Avast beta for mac randomly breaks http connections
« Reply #2 on: June 14, 2011, 04:32:22 PM »
There's no output from that command. I've been running with web shield disabled for the last 5 days now, so any info that was in the log has been pushed out.

However, if I look in the older logs, there is data: (Note hostname & machine name test replacements are mine to preserve ident data)

1 %> bzcat /var/log/system.log.*.bz2  | grep 'proxy\[[0-9]*\]'
Jun  9 06:38:40 <MACHINE NAME> proxy[248]: Starting daemon.
Jun  9 06:38:40 <MACHINE NAME> proxy[248]: Error opening hosts file: fopen(): No such file or directory
Jun  9 07:31:45 <HOSTNAMNE> proxy[248]: SIGTERM received. Exiting.
Jun  8 06:56:19 <HOSTNAMNE> proxy[232]: Error connecting to server: connect(): Connection refused
Jun  8 06:56:49 <HOSTNAMNE> proxy[232]: Error connecting to server: connect(): Connection refused
Jun  8 07:00:45 <HOSTNAMNE> proxy[232]: Defective HTTP request!
Jun  8 07:00:45 <HOSTNAMNE> proxy[232]: Wrong AV checkurl response code (501)!
Jun  8 07:00:45 <HOSTNAMNE> proxy[232]: Defective HTTP request!
Jun  8 07:00:45 <HOSTNAMNE> proxy[232]: Wrong AV checkurl response code (501)!
Jun  8 07:06:32 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 07:07:17 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 07:08:03 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 07:09:06 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 07:09:39 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 08:16:16 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 08:59:02 <HOSTNAMNE> proxy[232]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 11:35:52 <MACHINE NAME> proxy[225]: Starting daemon.
Jun  8 11:35:52 <MACHINE NAME> proxy[225]: Error opening hosts file: fopen(): No such file or directory
Jun  8 11:53:49 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Connection refused
Jun  8 11:59:26 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Connection refused
Jun  8 13:34:11 <HOSTNAMNE> proxy[225]: Defective HTTP response!
Jun  8 15:01:55 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Operation timed out
Jun  8 15:07:12 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Network is unreachable
Jun  8 15:08:18 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Operation timed out
Jun  8 15:08:20 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Network is unreachable
Jun  8 15:08:20 <HOSTNAMNE> proxy[225]: Error connecting to server: connect(): Operation timed out
Jun  8 15:36:58 <MACHINE NAME> proxy[225]: Starting daemon.
Jun  8 15:36:58 <MACHINE NAME> proxy[225]: Error opening hosts file: fopen(): No such file or directory
Jun  8 15:40:19 <HOSTNAMNE> proxy[225]: Error reading receive buffer: read(): Connection reset by peer
Jun  8 16:06:12 <MACHINE NAME> proxy[178]: Starting daemon.
Jun  8 16:06:12 <MACHINE NAME> proxy[178]: Error opening hosts file: fopen(): No such file or directory
Jun  8 17:09:11 <HOSTNAMNE> proxy[250]: Starting daemon.
Jun  8 17:09:11 <HOSTNAMNE> proxy[250]: Error opening hosts file: fopen(): No such file or directory
Jun  8 17:31:45 <MACHINE NAME> proxy[248]: Starting daemon.
Jun  8 17:31:45 <MACHINE NAME> proxy[248]: Error opening hosts file: fopen(): No such file or directory
Jun  8 19:13:54 <MACHINE NAME> proxy[248]: Starting daemon.
Jun  8 19:13:54 <MACHINE NAME> proxy[248]: Error opening hosts file: fopen(): No such file or directory
Jun  8 19:18:18 <MACHINE NAME> proxy[248]: Starting daemon.
Jun  8 19:18:18 <MACHINE NAME> proxy[248]: Error opening hosts file: fopen(): No such file or directory
Jun  8 19:39:09 <MACHINE NAME> proxy[160]: Starting daemon.
Jun  8 19:39:09 <MACHINE NAME> proxy[160]: Error opening hosts file: fopen(): No such file or directory
Jun  8 19:42:15 <MACHINE NAME> proxy[263]: Starting daemon.
Jun  8 19:42:15 <MACHINE NAME> proxy[263]: Error opening hosts file: fopen(): No such file or directory
Jun  8 19:46:01 <MACHINE NAME> proxy[160]: Starting daemon.
Jun  8 19:46:01 <MACHINE NAME> proxy[160]: Error opening hosts file: fopen(): No such file or directory
Jun  8 19:50:52 <MACHINE NAME> proxy[248]: Starting daemon.
Jun  8 19:50:52 <MACHINE NAME> proxy[248]: Error opening hosts file: fopen(): No such file or directory
Jun  8 20:16:28 <MACHINE NAME> proxy[301]: Starting daemon.
Jun  8 20:16:28 <MACHINE NAME> proxy[301]: Error opening hosts file: fopen(): No such file or directory
Jun  7 01:01:34 <HOSTNAMNE> proxy[62618]: Error connecting to server: connect(): Operation timed out
Jun  7 01:02:41 <HOSTNAMNE> proxy[62618]: Error connecting to server: connect(): Operation timed out

Truncated due to length restrictions....

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Avast beta for mac randomly breaks http connections
« Reply #3 on: June 16, 2011, 01:35:31 PM »
Hmm, the proxy does not terminate in a proper way. Either it is killed by something, or it crashes. Are there any crash logs in /Library/Logs/CrashReporter?

Offline bedge

  • Newbie
  • *
  • Posts: 8
Re: Avast beta for mac randomly breaks http connections
« Reply #4 on: June 16, 2011, 03:39:22 PM »
Not for avast, no: (unless they expired and were deleted)

0 %> ls -l /Library/Logs/CrashReporter
total 16
lrwxr-xr-x  1 root  admin  60 Jun 12 09:44 Locum_2011-06-12-094451_localhost.crash -> ../DiagnosticReports/Locum_2011-06-12-094451_localhost.crash
lrwxr-xr-x  1 root  admin  60 Jun 12 09:45 Locum_2011-06-12-094505_localhost.crash -> ../DiagnosticReports/Locum_2011-06-12-094505_localhost.crash

Here's one more possible clue. I'm running an ipsec vpn client that uses racoon and ipsec. The problem occurred with and without the vpn client active. Perhaps the vpn config itself, even when non-active had some effect on the avast client?

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Avast beta for mac randomly breaks http connections
« Reply #5 on: June 16, 2011, 04:07:05 PM »
Can you please post here the content of one of the files (or send the file to my mail address)? Thanks

Offline bilbo--baggins

  • Jr. Member
  • **
  • Posts: 30
Re: Avast beta for mac randomly breaks http connections
« Reply #6 on: May 08, 2012, 10:00:34 PM »
What was the outcome?  I'm noticing constant messages in console:

proxy: Defective HTTP response!

Just wondering if Avast is causing this, and why it's happening?

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Avast beta for mac randomly breaks http connections
« Reply #7 on: May 09, 2012, 11:44:24 AM »
I'm noticing constant messages in console:

proxy: Defective HTTP response!

Just wondering if Avast is causing this, and why it's happening?

If you get this message permanent for an URL, post here the URL so we can analyze the issue. If you get it "randomly" (and not offten) it is most probable caused by an interrupted HTTP request/response and does not require any attention.

Offline iynque

  • Newbie
  • *
  • Posts: 3
Re: Avast beta for mac randomly breaks http connections
« Reply #8 on: May 16, 2012, 12:05:54 AM »
I've been having the same issue. I figured it was related to Avast Web Shield. I'm going to disable it for now and see if Safari works again.

Generally, Safari would accept a url, appear to be loading, but never get anywhere. If I quit Safari and opened it again, the url would load just fine. I tried simply disabling the Safari Extension, but the problem persists.

The System.log lines that led me to this thread were:
5/15/12 5:57:50.349 PM proxy: Defective HTTP request!
5/15/12 5:57:50.350 PM proxy: Unexpected AV CHECKURL response code (501)!

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Avast beta for mac randomly breaks http connections
« Reply #9 on: May 17, 2012, 12:00:03 PM »
Is this issue related to a specific URL or is it happening randomly (or even for all URLs)?