Inology 0 Posted January 24, 2014 Share Posted January 24, 2014 Hello, We are maintaining a number of Linux (ubuntu 12.04 LTS) desktops for our Java developers. The developers are complaining that their builds are failing. We've tried a number of solutions for this. 1. exclude their builds directory for scanning 2. in realtime scanning set ingnore on file extensions for: .jar .war .ear .class .java but still they are complaining that a lot of their builds are failing. the strange thing is they fail only for about 70% of the time. the builds are failing with file access errors (and yes we are building code known to work, and building the same code every time for testing). what else can we do ?? the developers cannot do their work properly, unless they totally disable the ESET nod32 antivirus, wich offcourse is not what we want. Link to comment Share on other sites More sharing options...
Administrators Marcos 4,932 Posted January 24, 2014 Administrators Share Posted January 24, 2014 I'd suggest contacting Customer care on this matter. We'll need you to do the following: - edit esets.cfg and add syslog_class = "error:warning:summ:summall:part:partall:info:debug" to the General section - restart esets_daemon - reproduce the problem - edit esets.cfg and disable logging to syslog - restart esets_daemon - supply us with syslog (lines with avstatus would be enough) and esets.cfg Link to comment Share on other sites More sharing options...
Inology 0 Posted January 24, 2014 Author Share Posted January 24, 2014 Perfect, i will supply the log Link to comment Share on other sites More sharing options...
Inology 0 Posted January 24, 2014 Author Share Posted January 24, 2014 I'd suggest contacting Customer care on this matter. We'll need you to do the following: - edit esets.cfg and add syslog_class = "error:warning:summ:summall:part:partall:info:debug" to the General section - restart esets_daemon - reproduce the problem - edit esets.cfg and disable logging to syslog - restart esets_daemon - supply us with syslog (lines with avstatus would be enough) and esets.cfg General section = global section Link to comment Share on other sites More sharing options...
Inology 0 Posted January 24, 2014 Author Share Posted January 24, 2014 (edited) the error given in maven: [iNFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project core-api: Compilation failure [ERROR] error: error reading /home/gjenkins/builds/kis-platform/picore/model/target/core-model-3.8.0-SNAPSHOT.jar; invalid END header (bad central directory offset) [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. Note: maven is building multithreaded (T8 option) the syslog is attached syslog.dat.txt Edited January 24, 2014 by Inology Link to comment Share on other sites More sharing options...
Administrators Marcos 4,932 Posted January 24, 2014 Administrators Share Posted January 24, 2014 It's necessary to narrow it down to a particular folder. Let's start with excluding /var/lib/postgresql /home/gjenkins/.m2/repository and see if it makes a difference. If it doesn't help, try excluding each of the main folders in the root folder, one at a time, followed by excluding subfolders until you find the one that, when excluded, the issue doesn't occur. Link to comment Share on other sites More sharing options...
Inology 0 Posted January 27, 2014 Author Share Posted January 27, 2014 It's necessary to narrow it down to a particular folder. Let's start with excluding /var/lib/postgresql /home/gjenkins/.m2/repository and see if it makes a difference. If it doesn't help, try excluding each of the main folders in the root folder, one at a time, followed by excluding subfolders until you find the one that, when excluded, the issue doesn't occur. Excluding the first 2 folders did not give an effect. i'm now exluding all main folders, and will include them again one by one Link to comment Share on other sites More sharing options...
Inology 0 Posted January 27, 2014 Author Share Posted January 27, 2014 (edited) I've excluded all directory's from the root on. it still fails. perhaps it has something to do with the kernel hook in place, and the multitreaded builds ? disabeling the realtime scanning does not solve the issue, but preventing ESET from starting up does solve the issue (but we wouldn't want that) Edited January 27, 2014 by Inology Link to comment Share on other sites More sharing options...
Recommended Posts