Author Topic: [SOLVED] Mac internal error message at start up  (Read 4654 times)

0 Members and 1 Guest are viewing this topic.

Offline mbohlman1

  • Newbie
  • *
  • Posts: 2
[SOLVED] Mac internal error message at start up
« on: January 09, 2018, 01:49:57 AM »
Newbie here so apologies if answered already but I have not found this listed.

I keep getting an Internal error dialog at start up and that I should check the system log.  Looking in there I see a couple of errors but not sure which is causing this problem or how to fix.

Here is the excerpt from the system log:
com.avast.daemon[202]: SIGTERM/SIGINT received. Exiting.
com.avast.fileshield[558]: fs:  Error on socket

com.avast.proxy[526]: SIGTERM/SIGINT received. Exiting.
com.avast.fileshield[558]: fs:  Stopping File Shield...
com.avast.wifiguard[568]: BUG in libdispatch client: kevent[read] monitored resource vanished before the source cancel handler was invoked
com.apple.xpc.launchd[1] (com.avast.daemon): This service is defined to be constantly running and is inherently inefficient.
com.avast.daemon[1379]: Starting daemon.
com.avast.daemon[1379]: Loaded VPS #18010804
com.apple.xpc.launchd[1] (com.avast.service): This service is defined to be constantly running and is inherently inefficient.
com.avast.service[1403]: sock_connect_unix_socket: connect(/Library/Application Support/Avast/run/wifiguard.sock) failed: No such file or directory
com.avast.service[1403]: WifiGuardNotifier: failed to connect
com.avast.service[1403]: Failed to check FileShield driver
com.apple.xpc.launchd[1] (com.avast.proxy): This service is defined to be constantly running and is inherently inefficient.
com.avast.proxy[1453]: Starting daemon.
com.avast.proxy[1453]: Error connecting to service socket: connect(): /Library/Application Support/Avast/run/service.sock: No such file or directory
com.avast.proxy[1453]: swquery.apple.com:https: nodename nor servname provided, or not known
com.apple.xpc.launchd[1] (com.avast.fileshield): This service is defined to be constantly running and is inherently inefficient.
com.apple.xpc.launchd[1] (com.avast.account[1476]): Could not find and/or execute program specified by service: 2: No such file or directory: /Library/Application Support/components/account/com.avast.account-sync
com.avast.fileshield[1471]: fs:  Starting daemon
com.apple.xpc.launchd[1] (com.avast.account[1476]): Service setup event to handle failure and will not launch until it fires.
com.avast.fileshield[1471]: fs:  config_load: ini_read() failed [-1]. Will use defaults.
com.avast.fileshield[1471]: fs:  avsvc_open: connect() failed. No such file or directory [2]
com.apple.xpc.launchd[1] (com.avast.wifiguard): This service is defined to be constantly running and is inherently inefficient.
com.apple.xpc.launchd[1] (com.avast.helper): This service is defined to be constantly running and is inherently inefficient.
com.avast.service[1403]: Failed to check MailShield driver
com.avast.daemon[1379]: License error: /Library/Application Support/Avast/config/license.avastlic: No such file or directory
com.avast.daemon[1379]: SIGHUP received. Reloading...
com.avast.fileshield[1471]: fs:  Rereading config...
com.avast.fileshield[1471]: fs:  config_load: ini_read() failed [-1]. Will use defaults.

Any help is appreciated.  Running High Sierra with latest updates and 13.4 (downloaded 13.3 and it automatically updated to 13.4 - and generated the same internal error message when restarting after that).

Thanks,
mark
« Last Edit: January 23, 2018, 11:04:03 AM by lukas.hasik »

Offline ondrej.kolacek

  • Avast team
  • Sr. Member
  • *
  • Posts: 283
Re: Mac internal error message at start up
« Reply #1 on: January 09, 2018, 12:33:05 PM »
Hello,
the sigterm messages in log hint that either some other program is messing with avast or some kind of partial uninstallation occurred (but that does not seem likely).
You could send me output of command "find  /Library/Application Support/Avast" to my mail (ondrej dot kolacek at avast.com) but that won't probably help you.
Does reinstallation of avast fix the issue? Please note that you will probably have to restart after the uninstallation.
Kind regards,
Ondrej Kolacek

Offline mbohlman1

  • Newbie
  • *
  • Posts: 2
Re: Mac internal error message at start up
« Reply #2 on: January 09, 2018, 01:11:29 PM »
Hi,

  Had already tried uninstall, reboot, new install but that did not resolve the issue.  I also manually removed the Avast directory from the system thinking maybe something was left over.  I will send the output. 
Thanks,
-- mark

Offline duffy.online

  • Newbie
  • *
  • Posts: 1
Re: Mac internal error message at start up
« Reply #3 on: January 11, 2018, 10:49:19 AM »
I too am receiving the same popup :  Internal Error!  I've deleted, rebooted and reinstalled and the error still displays.  One immediate option:  delete it and find an antivirus that works with OSX 10.13.2. 

Offline ondrej.kolacek

  • Avast team
  • Sr. Member
  • *
  • Posts: 283
Re: Mac internal error message at start up
« Reply #4 on: January 17, 2018, 09:12:58 AM »
Just a follow up - I have investigated this with kind help of the OP and the message is spurious, caused by timing upon startup on certain configurations. This will be fixed in the next version.

Offline uri6

  • Newbie
  • *
  • Posts: 2
Re: Mac internal error message at start up
« Reply #5 on: January 20, 2018, 09:49:52 PM »
Same story here. Mac Pro, OS 10.13.2 (High Sierra) and Avast 13.4 - Random 'Internal Error' warning message on avast start, everything seems to work fine. Hoping for issue to get fixed next update!