So, after running Lunatics 041 since its release with zero problems and virtually no errors across three rigs, this morning I noticed that 10 AP's for NV cuda/opencl had erred out overnight. What was strange was, the units were across all three rigs, not just one. Checking the errors, they were all (-185), indicating a missing file. A quick check of the first rig yielded the following from the event log after a re-start:

10/28/2013 11:57:44 AM | SETI@home | Found app_info.xml; using anonymous platform
10/28/2013 11:57:44 AM | SETI@home | File referenced in app_info.xml does not exist: AP6_win_x86_SSE2_OpenCL_NV_r1843.exe
10/28/2013 11:57:44 AM | SETI@home | [error] State file error: missing application file AP6_win_x86_SSE2_OpenCL_NV_r1843.exe

Yep, after no problems running AP's on the GPUs on three rigs for 6 months, sometime overnight, the main EXE file disappeared from not one, but ALL my rigs. And just that file too; the others like the cmdline file for AP, as well as all the other exe's, are still there.

A couple things, because I know you'll ask: No, nothing has changed on any of the rigs in at least 60 days. No one else has access to the rigs, either physically or remotely. I use Avast Free on all the rigs, and have had no problems with it ever.

Here's the final oddity of it all: Re-running the 041 installer does not correct the problem. I still get BOINC saying no AP exe, and the file is not in the seti folder.

I'm stumped. Either that or the answer is so obvious that I can't see it. Thoughts/suggestions?

---

Could it be that a new definition in the AV software is triggering on the Lunatics file & removing or quarantining it? If so it will be detected during the install & removed as quickly as it gets put there.

I have had similar issues in the past.

Just a thought.

Good Luck Gatekeeper.

---

Happy Crunching,

Graham

Gatekeeper, it looks as if you are not alone - take a look at:
http://setiathome.berkeley.edu/forum_thread.php?id=73154
One solution would be to add the BOINC folders to the "don't scan" list - I did this some time ago when AVG was doing much the same :-(

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Yep, that was it alright. Like the OP in the other thread mentioned, in all the years I've used Avast, this is the first time it's ever false-positived a BOINC/seti file.

What gripes me even more is that it did so silently, with no notice of the action it took in its log, or as a popup. And, I might add, Avast V9 (AKA Avast 2014) is REALLY clunky in access to its virus chest and settings. There were three different places I had to log the exclusion before it finally took.

There's an hour of my life I can never get back.

Thanks to Graham and rob for setting me in the right direction.

---