yossarianuk 1 Posted October 3, 2018 Share Posted October 3, 2018 Hi. Just installed ubuntu 18.04 - installed latest eset (Version: 4.0.90.0). Once installed and rebooted I am unable to run any local KVM vm's. It is due to the entry added to /etc/ld.so.preload libesets_pac.so When I start any KVM VM on the local machine I get the warning Error starting domain: internal error: cannot load AppArmor profile 'libvirt-1811665e-455d-4673-a10d-c5ae9b5028e7' And journalctl shows this, as you can see it is due to the library that eset adds -> libesets_pac.so Oct 03 12:50:25 mcox-N552VW libvirtd[4197]: 2018-10-03 11:50:25.922+0000: 4202: error : virCommandWait:2601 : internal error: Child process (LIBVIRT_LOG_OUTPUTS=3:stderr /usr/lib/libvirt/virt-aa-helper -p 0 -c -u libvirt-1811665e-455d-4673-a10d-c5ae9b5028e7) unexpected exit status 127: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (failed to map segment from shared object): ignored. Oct 03 12:50:25 mcox-N552VW libvirtd[4197]: Inconsistency detected by ld.so: rtld.c: 720: init_tls: Assertion `i == GL(dl_tls_max_dtv_idx)' failed! Oct 03 12:50:25 mcox-N552VW libvirtd[4197]: 2018-10-03 11:50:25.922+0000: 4202: error : AppArmorGenSecurityLabel:472 : internal error: cannot load AppArmor profile 'libvirt-1811665e-455d-4673-a10d-c5ae9b5028e7' If I comment out the line in /etc/ld.so.preload it works perfectly. How can this be fixed, at the moment I have had to comment out that line. Link to comment Share on other sites More sharing options...
Administrators Marcos 4,356 Posted October 3, 2018 Administrators Share Posted October 3, 2018 AppArmor is not supported. Link to comment Share on other sites More sharing options...
yossarianuk 1 Posted October 3, 2018 Author Share Posted October 3, 2018 It used to work fine in ububntu 16.04 and older version of eset. Seeing as all version of Ubuntu has apparmor do you not support Ubuntu then ? If I comment the line out i can still use nod32 but it disables realtime scanning, in that case I would be better off using Clamav which has zero cost... Link to comment Share on other sites More sharing options...
Administrators Marcos 4,356 Posted October 3, 2018 Administrators Share Posted October 3, 2018 Please contact customer care. This forum is intended rather for sharing knowledge and actual issues requiring several iterations should be tracked through standard support tickets. Link to comment Share on other sites More sharing options...
Most Valued Members Nightowl 164 Posted October 4, 2018 Most Valued Members Share Posted October 4, 2018 12 hours ago, Marcos said: Please contact customer care. This forum is intended rather for sharing knowledge and actual issues requiring several iterations should be tracked through standard support tickets. Setting the rule in Apparmor to allow ESET won't do any help? , I guess it's having troubles with this problem and my problem earlier posted in the forum , won't it get fixed if we allow ESET in Apparmor? , Because Ubuntu now uses AppArmor and other Linux will use SELinux so it will be the same with Apparmor or SELinux Link to comment Share on other sites More sharing options...
Recommended Posts