My Avast message is: “An internal error occurred. You may find more info by opening the avast application or by searching the system logs.” I have no further information on my app and don’t know how to navigate my system logs thru console. Please help, thanks.
Hallo, logs are available in /var/log (those that belong to fileshield and scanning daemon), in /tmp (those describing install/uninstall/update steps) and in /var/log/system.log (look for lines with com.avast.proxy ident).
Regards,
pc
I am getting this error also. Any idea what’s causing it? I’m not comfortable going into terminal. Is there another way to see the logs?
Yes, you can use the “Console” application that is located in Applications → Utilities to read/search all standard system log files.
I have the same error message. I have used Console to view var/log/avastdaemon.log, var/log/avastfileshield.log, var/log/kernel.log and var/log/system.log.
But I don’t know what I’m looking for and, even if I did, how would I fix it?
Internal error occured = scanning service was not available for some time.
So, typically have a look for lines complaining about “connecting to master socket”, and then, have a look into avastdaemon.log what actions were performed just before this has begun - might be some bulk network traffic processing, or some particular file scan.
regards,
pc
I started getting this terribly un-useful alert a few days ago also.
I get it on every bootup and just got it when I start up Google Chrome
I looked in system.log for mention of master socket and found this at about the time the alert had popped up:
Apr 21 16:53:21 com.avast.helper[283]: Pop socket closed by peer
Apr 21 16:53:21 com.avast.helper[283]: Error connecting to master socket: connect(): Connection refused
Apr 21 16:53:49 com.avast.helper[283]: Pop socket closed by peer
I looked in avastdaemon.log at this time and found tons of entries like this for each tab being reloaded:
Sun Apr 21 16:53:20 2013 [SESSION 2977812480]: Input (normal): ‘CHECKURL http://1.gravatar.com/avatar/ad516503a11cd5ca435acc9bb6523536?s=67’.
Sun Apr 21 16:53:20 2013 [SESSION 2990592000]: Input (normal): ‘SCAN /tmp/proxy-VuPNHL/fAUUyp CID webshield TRIGGER ON_WEB SOURCE http://order.tupperware.com/coe-images/home/newhome_youtube.png REFERRER http://order.tupperware.com/coe/app/tup_widget.show_page?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500’.
Sun Apr 21 16:53:20 2013 [SESSION 2990592000]: Scanning path ‘/tmp/proxy-VuPNHL/fAUUyp’ started.
I looked in avastfileshield.log at the same time and found:
[61-warn] Sun Apr 21 16:53:13 2013 - avscan_handle_timeout: Timeout scan-end has occured
[61-warn] Sun Apr 21 16:53:13 2013 - avscan_handle_timeout: Timeout scan-end has occured
[61-warn] Sun Apr 21 16:53:13 2013 - avscan_handle_timeout: Timeout scan-end has occured
[61-warn] Sun Apr 21 16:53:15 2013 - avscan_handle_timeout: Timeout scan-abort has occured
[61-warn] Sun Apr 21 16:53:15 2013 - avscan_handle_timeout: Timeout scan-abort has occured
[61-warn] Sun Apr 21 16:53:15 2013 - avscan_handle_timeout: Timeout scan-abort has occured
[61-warn] Sun Apr 21 16:53:19 2013 - avscan_handle_timeout: Timeout scan-end has occured
[61-warn] Sun Apr 21 16:53:19 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
Cannot perform HTTP request. [1c]
[61-err] Sun Apr 21 16:53:21 2013 - avscan_handle_read: Lost connection to daemon.
[61-err] Sun Apr 21 16:53:21 2013 - avscan_handle_write: I/O error. Broken pipe [32]
[61-err] Sun Apr 21 16:53:21 2013 - avscan_handle_read: Lost connection to daemon.
[61-err] Sun Apr 21 16:53:21 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[61-err] Sun Apr 21 16:53:21 2013 - avmaster_handle_read: Lost connection to daemon.
[61-err] Sun Apr 21 16:53:21 2013 - avmaster_open: connect() failed. Connection refused [61]
[61-err] Sun Apr 21 16:53:28 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:30 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:33 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:36 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:39 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:42 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:45 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-err] Sun Apr 21 16:53:48 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[61-warn] Sun Apr 21 16:53:48 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
Cannot perform HTTP request. [1c]
[61-err] Sun Apr 21 16:53:49 2013 - avmaster_handle_read: Lost connection to daemon.
[61-warn] Sun Apr 21 16:53:51 2013 - timeout_enable: Timeout avmaster-quit already enabled.
[61-err] Sun Apr 21 16:53:51 2013 - avmaster_handle_timeout: Timeout avmaster-quit has occured.
[61-err] Sun Apr 21 16:53:53 2013 - config_load: ini_read() failed [-1]. Will use defaults.
So I seem to ba able to locate the parts of the logs you suggested we look at, but I have no idea what they may or may not mean.
As a possibly related item, when Chrome was relaoding the tabs the fan in the MacBook Pro ramped up to maximum. I checked the Activity Monitor and found com.avast.MacAvast.MAD had once again gone totally berserk (I opened a ticket on this previously) and was showing over 750% CPU usage of the MBP’s 8 cores. I force-quit that process and it is now behaving itself.
I am also getting this message only on boot-up, and once I open Avast once it works fine. No idea what is causing it but it is annoying.
That is what I am seeing. Get the “internal error message” whenever I have to either reboot or shut down the iMac. Open the Avast program - get a message the program must “repair” itself. Click REPAIR and everything seems fine - until the next time I have to shutdown/reboot.
Hi,
I had the same message a few days ago. At that time my computer had a USB thumb drive (its file system is exFAT) connected to when I turned it on. Once I unmounted and removed it from the machine, and rebooted the computer, then the message had gone, it never appears.
Will it give any help?