Author Topic: OS X El Capitan  (Read 9942 times)

0 Members and 1 Guest are viewing this topic.

Offline 111Yahro

  • Newbie
  • *
  • Posts: 4
Re: OS X El Capitan
« Reply #15 on: October 28, 2015, 02:27:06 PM »
I got following problem on EL Capitan - Avast is in endless crash loop.
How can this be fixed?

swquery.apple.com is unreachable but I have seen somewhere there should be fallback process which uses bare IP....


Oct 28 12:49:00 com.avast.proxy[9355]: swquery.apple.com:https: nodename nor servname provided, or not known
Oct 28 12:49:00 com.avast.proxy[9355]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 28 12:49:00 com.avast.proxy[9355]: Error connecting KEXT controll socket: connect(): No such file or directory
Oct 28 12:49:00 com.avast.proxy[9355]: Fatal error. Exiting.
Oct 28 12:49:00 com.apple.xpc.launchd[1] (com.avast.proxy[9355]): Service exited with abnormal code: 1
Oct 28 12:49:00 com.apple.xpc.launchd[1] (com.avast.proxy): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Oct 28 12:49:04 com.avast.fileshield[2693]: kext_open: The Kext is not loaded.
Oct 28 12:49:10 com.avast.proxy[9356]: Starting daemon.
Oct 28 12:49:10 com.avast.proxy[9356]: swquery.apple.com:https: nodename nor servname provided, or not known
Oct 28 12:49:10 com.avast.proxy[9356]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 28 12:49:10 com.avast.proxy[9356]: Error connecting KEXT controll socket: connect(): No such file or directory
Oct 28 12:49:10 com.avast.proxy[9356]: Fatal error. Exiting.

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: OS X El Capitan
« Reply #16 on: October 29, 2015, 06:25:58 PM »
Unreachable swquery.apple.com is not an issue. It's one of the whitelisted addresses formerly used
by Apple updates. The warning only informs it does not exist any more.

The issue here is the non-functional web/mail shield kernel extension (KEXT). And it has most probable
nothing to do with El Captain but rather with some special/unusual setup of your Mac.

Offline 111Yahro

  • Newbie
  • *
  • Posts: 4
Re: OS X El Capitan
« Reply #17 on: October 30, 2015, 04:29:24 PM »
Starting from beginning:

I use Business Avast security. After installation I get the green sign - You are protected.
After manually opening Avast UI I see already You are Not Protected.

AvastFileShield module is loaded the same as PackageForwarder.

When I update Avast here I see:

Oct 30 16:21:36  com.avast.fileshield[8619]: kext_open: The Kext is not loaded.
Oct 30 16:21:37  com.avast.proxy[8852]: Starting daemon.
Oct 30 16:21:37  com.avast.proxy[8852]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 30 16:21:37  com.avast.proxy[8852]: Error connecting KEXT controll socket: connect(): No such file or directory

in /var/log/system.log

and there is no kext module loaded.

When I try to load it up manually I see:

/Library/Application Support/Avast/components/fileshield/signed # kextload AvastFileShield.kext
/Library/Application Support/Avast/components/fileshield/signed/AvastFileShield.kext failed to load - (libkern/kext) authentication failure (file ownership/permissions); check the system/kernel logs for errors or try kextutil(8).

Please let me know how can I diagnose better why this module is not loading automatically?
Is there any support connected with my Business version of Avast?

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 67895
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: OS X El Capitan
« Reply #18 on: October 31, 2015, 07:59:29 AM »
Is there any support connected with my Business version of Avast?
-> https://forum.avast.com/index.php?board=65.0
Win 8.1 [x64] - Avast PremSec 20.10.2439.Beta#2 [UI.580] - CC 5.74 - EEK - FF ESR 78.5 [NS/AOS/uBO/PB] - TB 78.5 - SB/CP/SL/DU.B
Deutschsprachiger Bereich -> Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: OS X El Capitan
« Reply #19 on: November 02, 2015, 05:14:28 PM »
Starting from beginning:

I use Business Avast security. After installation I get the green sign - You are protected.
After manually opening Avast UI I see already You are Not Protected.

AvastFileShield module is loaded the same as PackageForwarder.

When I update Avast here I see:

Oct 30 16:21:36  com.avast.fileshield[8619]: kext_open: The Kext is not loaded.
Oct 30 16:21:37  com.avast.proxy[8852]: Starting daemon.
Oct 30 16:21:37  com.avast.proxy[8852]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Oct 30 16:21:37  com.avast.proxy[8852]: Error connecting KEXT controll socket: connect(): No such file or directory

in /var/log/system.log

and there is no kext module loaded.

When I try to load it up manually I see:
 # kextload AvastFileShield.kext
/Library/Application Support/Avast/components/fileshield/signed/AvastFileShield.kext failed to load - (libkern/kext) authentication failure (file ownership/permissions); check the system/kernel logs for errors or try kextutil(8).

Please let me know how can I diagnose better why this module is not loading automatically?

What file permissions do the KEXT files have? Can you post the output of
Code: [Select]
ls -lh '/Library/Application Support/Avast/components/fileshield/signed'
ls -lh '/Library/Application Support/Avast/components/proxy/signed'
here? Looks like the binaries have wrong permissions or UID/GID.

Is there any support connected with my Business version of Avast?
Maybe there is, but it will definitely not be better than our - the developers - responses ;-)

Offline 111Yahro

  • Newbie
  • *
  • Posts: 4
Re: OS X El Capitan
« Reply #20 on: November 02, 2015, 05:55:06 PM »
Here is the output:

drwxr-xr-x  3 root  staff   102B Oct 12 17:04 AvastFileShield.kext
drwxr-xr-x  3 root  staff   102B Oct 12 17:04 AvastPacketForwarder.kext

About the support I meant more ordered official way to contact you guys ;-)


Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: OS X El Capitan
« Reply #21 on: November 03, 2015, 03:17:55 PM »
Here is the output:

drwxr-xr-x  3 root  staff   102B Oct 12 17:04 AvastFileShield.kext
drwxr-xr-x  3 root  staff   102B Oct 12 17:04 AvastPacketForwarder.kext

The group should be "wheel", not "stuff". If you run "chown -R root:wheel" on those two directories,
you should fix the issue. Its however a question, how this could happen... We will have a look at
the update process.

About the support I meant more ordered official way to contact you guys ;-)
The official way is using the support channels, but it is definitely not the fastest one (at the end,
such issues will end in our mailboxes anyway). Generally - we do handle posts here that look like
bugs and are from people who can give usable info (like you) quiet promptly.

Offline 111Yahro

  • Newbie
  • *
  • Posts: 4
Re: OS X El Capitan
« Reply #22 on: November 04, 2015, 02:15:17 PM »
I worked. THX!! :D

Offline jazzycat-dances

  • Newbie
  • *
  • Posts: 5
Re: OS X El Capitan
« Reply #23 on: November 05, 2015, 05:51:56 AM »
How do I tell what version of Avast I have on my computer?  I don't see any numbers anywhere.  Where do I figure this out?

Offline RTB

  • Newbie
  • *
  • Posts: 1
Re: OS X El Capitan
« Reply #24 on: November 22, 2015, 10:28:27 PM »
After upgrading to El Capitan I could not connect to ICloud through Itunes. I left enabled IPv6 and enabled both scan secured connections and scan secured connections from browsers only. I am now able to connect.

Tom
« Last Edit: November 25, 2015, 07:22:21 PM by RTB »