Avast WEBforum
Consumer Products => Avast Mac Security => Topic started by: REDACTED on February 15, 2015, 06:18:19 PM
-
Running OS X Yosemite v. 10.10.2
I've just removed SOPHOS and successfully installed AVAST.
I wanted to perform an initial FULL SCAN, but it never gets beyond 5 % of completion.
It subsequently stopped at a file described as /dev/fd/71
Anyone out there experiencing the same kind of issue and having a solution?
Thanks,
Laerg1
-
Yep, same here. I'm using Yosemite 10.10.2 as well. My first stalled scan occurred at about 82%; next one at 81%. Both of those were stopped at a directory I failed to write down, but it was the same location both times. I tried one more time and the scan stopped at 6% complete at /dev/fd/96.
-
Is there anything in the system log file?
-
I'm not real savvy here, but I assume by system log file you mean the log file for my Mac? I checked there and didn't see anything labeled Avast.
I ran another scan this morning and this time it went all the way to 86% before stalling. This is what I see now:
Scanned files: 468189
Unable to scan: 1008
Infections: 0
Last scanned file: /Users/MyName/Library/Messages/chat.db-wal
I believe that is the location of the last scanned file on the first two scans I mentioned in my first post.
-
What happens if you execute the following commands in the Terminal?
scan /Users/MyName/Library/Messagesscan /dev
Does the scan hang? crash? (You would find a new crash report in the Console)
-
Okay, you're asking me to do something I'm completely unfamiliar with. Is there a risk of totally fouling things up if I try those commands in Terminal?
Also, are you asking me to try two different things? In other words, at the blinking cursor in Terminal, type: scan(space)/Users/MyName/Library/Messages, and if that doesn't show anything type: scan(space)/dev
I'm afraid this makes me nervous and I really need explicit step-by-step instructions. Please, don't be afraid to talk to me like I don't know anything because I really don't!
-
Hello
Same issue. Uninstalled and reinstalled. From not being able to scan and protection shields on, the app now just says "not protected".
Came accross this post ... ran the two commands. Both delivers similar response:
scan /dev
connect(): /Library/Application Support/Avast/scan.sock: No such file or directory
please advise further
-
Okay, you're asking me to do something I'm completely unfamiliar with. Is there a risk of totally fouling things up if I try those commands in Terminal?
No, scan is the Avast command line scanner, running it may not cause any harm to your
computer. In fact it is equivalent to pressing the "Scan" button in the Avast GUI. More info about
the scan tool can be found in its manual page (man scan).
The reason I wanted You to run the command line tool was to see if your issue is related to the GUI
or to the scan engine.
-
Came accross this post ... ran the two commands. Both delivers similar response:
scan /dev
connect(): /Library/Application Support/Avast/scan.sock: No such file or directory
In your case there is something wrong with the scan engine. There will for sure be some info
in the system log file and/or a crash report file (you can browse both in the Console application).
-
Running OS X Yosemite v. 10.10.2 I have the same problem since a few days. Avast does not complete the scan.
Sometimes is stops after 16% on a file called dev/fd/10 and sometimes on other files.
Any idea?
Thanks
-
My system log during scanning. I killed the process with force quit...
I hope it does not burn my CPU. :'(
Feb 16 18:35:41 My-iMac com.apple.xpc.launchd[1] (com.avast.daemon): This service is defined to be constantly running and is inherently inefficient.
Feb 16 18:35:41 My-iMac.local com.avast.daemon[147]: Starting daemon.
Feb 16 18:35:44 My-iMac.local com.avast.daemon[147]: Loaded VPS #15021501
Feb 16 18:35:45 My-iMac com.apple.xpc.launchd[1] (com.avast.service): This service is defined to be constantly running and is inherently inefficient.
Feb 16 18:35:48 My-iMac com.apple.xpc.launchd[1] (com.avast.proxy): This service is defined to be constantly running and is inherently inefficient.
Feb 16 18:35:48 My-iMac.fritz.box com.avast.proxy[914]: Starting daemon.
Feb 16 18:35:48 My-iMac kernel[0]: com.avast.fileshield: Started.
Feb 16 18:35:48 My-iMac com.apple.xpc.launchd[1] (com.avast.fileshield): This service is defined to be constantly running and is inherently inefficient.
Feb 16 18:35:48 My-iMac.fritz.box com.avast.fileshield[939]: Starting File Shield (build Feb 9 2015 16:59:39)
Feb 16 18:35:48 My-iMac.fritz.box com.avast.fileshield[939]: config_load: ini_read() failed [-1]. Will use defaults.
Feb 16 18:35:48 My-iMac kernel[0]: com.avast.fileshield: Unmount of /Volumes/G-DRIVE Backup detected: Cleaning cached entries.
Feb 16 18:35:48 My-iMac.fritz.box com.avast.fileshield[939]: Detected unmount of /Volumes/G-DRIVE Backup
Feb 16 18:35:48 My-iMac.fritz.box com.avast.proxy[914]: swquery.apple.com:https: nodename nor servname provided, or not known
Feb 16 18:36:31 My-iMac com.apple.xpc.launchd[1] (com.avast.update-agent): This service is defined to be constantly running and is inherently inefficient.
Feb 16 18:36:35 My-iMac com.apple.xpc.launchd[1] (com.avast.helper): This service is defined to be constantly running and is inherently inefficient.
Feb 16 18:45:46 My-iMac.fritz.box com.avast.daemon[147]: SIGHUP received. Reloading...
Feb 16 18:45:47 My-iMac.fritz.box com.avast.daemon[147]: Loaded VPS #15021600
Feb 16 18:46:36 My-iMac.fritz.box com.avast.daemon[147]: Removed VPS #15021501
Feb 16 18:55:48 My-iMac com.apple.xpc.launchd[1] (com.avast.update): Service only ran for 607 seconds. Pushing respawn out by 10193 seconds.
Feb 16 19:01:53 My-iMac kernel[0]: process com.avast.daemon[147] thread 100995 caught burning CPU! It used more than 50% CPU (Actual recent usage: 81%) over 180 seconds. thread lifetime cpu usage 90.230014 seconds, (77.432730 user, 12.797284 system) ledger info: balance: 90014011550 credit: 90014011550 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 110407300276
Feb 16 19:01:53 My-iMac.fritz.box spindump[1486]: Saved cpu_resource.diag report for com.avast.daemon version ??? (???) to /Library/Logs/DiagnosticReports/com.avast.daemon_2015-02-16-190153_My-iMac.cpu_resource.diag
Feb 16 19:11:58 My-iMac.fritz.box com.avast.fileshield[939]: Detected unmount of /Volumes/Recovery HD
Feb 16 19:11:58My-iMac kernel[0]: com.avast.fileshield: Unmount of /Volumes/Recovery HD detected: Cleaning cached entries.
Looked for the diag file and found this:
Command: com.avast.daemon
Path: /Library/Application Support/Avast/*/com.avast.daemon
Powerstats for: com.avast.daemon [147] thread 0x18a83
70 handler + 1127 (com.avast.daemon) [0x100002a87]
70 engine_scan + 187 (com.avast.daemon) [0x10000541b]
0x100000000 - 0x1000c3fe7 com.avast.daemon <023728F1-100E-36FD-B74E-B6523EFBB0BD> /Library/Application Support/Avast/*/com.avast.daemon
0x11abcc000 - 0x11ae2cfe7 engine.so (0) <C654BE7D-C67A-31B9-B0FE-21047A76FD7A> /Library/Application Support/Avast/*/engine.so
0x11aea5000 - 0x11b167fff algo.so (0) <3A009D00-BDC5-31B2-A3B0-E1E63916433B> /Library/Application Support/Avast/*/algo.so
Powerstats for: com.avast.daemon [147] (other threads)
0x100000000 - 0x1000c3fe7 com.avast.daemon <023728F1-100E-36FD-B74E-B6523EFBB0BD> /Library/Application Support/Avast/*/com.avast.daemon
0x11abcc000 - 0x11ae2cfe7 engine.so (0) <C654BE7D-C67A-31B9-B0FE-21047A76FD7A> /Library/Application Support/Avast/*/engine.so
Powerstats for: Avast
2 -[AVCCServiceSocket worker:] + 2310 (Avast) [0x100003c26]
2 -[AVCCServiceSocket processMsg:length:] + 1056 (Avast) [0x100003110]
2 __22-[ScanModel startScan]_block_invoke + 80 (Avast) [0x100060180]
1 -[ScanModel processProgress:] + 659 (Avast) [0x10005fa23]
1 -[ScanModel addScanItem:] + 385 (Avast) [0x10005da51]
1 -[ScanModel processProgress:] + 246 (Avast) [0x10005f886]
3 start + 52 (Avast) [0x1000021a4]
1 -[ScanStartController update:] + 342 (Avast) [0x10004ffb6]
1 +[Localization _L:fromTable:] + 61 (Avast) [0x10007b12d]
1 +[Localization _L:fromTables:] + 168 (Avast) [0x10007adb8]
1 -[ScanStartController update:] + 134 (Avast) [0x10004fee6]
0x100000000 - 0x100103ff7 com.avast.AAFM 10.6 (43623) <48848427-1E2F-3420-88C3-23E0B766C158> /Applications/Avast.app/Contents/MacOS/Avast
Hope this helps finding the problem.
Thanks
-
Sorry, as I said before, I am so lacking in this area that I don't even know how to quote a line from a previous post. Is there any way you could show me a screen shot of the command you suggested in an actual Terminal window?
-
Mine stops at /Users/MyName/Library/Messages/chat.db-wal also and it stops at the dev/ files too. Mine ran initially to 81%, now it stops at about 3%.
-
Yep. same problem here. I have Yosemite right up-to-date. Yesterday the scan stopped at 63%. Last night it stopped at 3%, which suggests that it's the scan engine and not the files that's stopping it. I'm not about to meddle with Terminal either, so if Avast! can't solve this soon, I'm about to change to another programme.
-
I agree that Avast needs to look into this. I was tempted to uninstall and reinstall Avast but the system requirements listed on the Avast site don't include Yosemite (only includes up to Mavericks). I don't want to risk screwing things up further. I'm going to wait awhile to see if a program update comes through. If not, I may try to find another program as well. Let us know if you find a program you're happy with. I've really liked Avast and hope a solution can be found soon though.
-
OK Baschio, will do. To be fair, Avast! has served me well so far, it's free, and it does, of course, still protect my system. I have no problem in paying for another system but I do object to an annual fee, and most of them seem to ask for this. However, I will continue to look. Hopefully, Avast! will have fixed it before I find one!
-
There was indeed a serious bug that caused the scan engine to deadlock
on some special files. Version 10.7 (43713) fixed this.
-
Thanks for this, Tumic. Now attempting to update to 10.7.
-
Yes! I updated to 10.7 and just completed a full scan without a problem.
-
Me too. Many thanks Avast!
-
Haha, that's it? Thank you guys, now I can do a full scan into my mac. I will prompt you when it's done :)
Yep! It's done. Nice work Avast.
I'm wondering if you could give me some advices about this aspect ratio calculator guys (http://www.ninjaunits.com/aspect-ratio-calculator/). It's working fine or not?