fascik 0 Posted November 29, 2020 Share Posted November 29, 2020 Hi, I have 2 datacenters (different locations, different VM host configuration) and the same error with EVS. There wasn't any config changes, upgrades, etc.. EVS – version 1.7.1 Vmware vSpehre - VMware vCenter Server Appliance 6.7.0.42000 NSX Manager – v. 6.4.6.14819921 Guest Introspection - 6.4.6.14716228 Once I login to vCenter I saw red exclamation marks on Eset Virtualization Security (error: Guest Introspection SVM status ) and VM hosts (error: Guest Introspection Host status). At Eset Security and Management Center each EVS hase a status: Product is installed but it is not running. After some investigation I saw that all of Eset Virtualization Security virtual machines boot to console with error: cannot access daemon setup - see attachment. What is wrong? I can't find any logs. Link to comment Share on other sites More sharing options...
ESET Staff Solution Matus 21 Posted November 30, 2020 ESET Staff Solution Share Posted November 30, 2020 Hi fascik, there was a problematic update of a module, which was fixed within few hours. However it seems that EVS machine some did not recovered from that. From Installation and Upgrade > Service Deployment if you erase EVS and then re-add, it'll work. I'm not sure right now if there is some less intrusive way of fixing However, thanks to vCenter it'll redeploy within a minutes and will work fine after that. Link to comment Share on other sites More sharing options...
fascik 0 Posted November 30, 2020 Author Share Posted November 30, 2020 11 minutes ago, Matus said: From Installation and Upgrade > Service Deployment if you erase EVS and then re-add, it'll work. I'm not sure right now if there is some less intrusive way of fixing However, thanks to vCenter it'll redeploy within a minutes and will work fine after that. Hi Mateus, thanks for quick answer. So does it mean I have to delete EVS, Guest introspection and Eset vagent host or just redeploy EVS from Eset Security Management Center? Link to comment Share on other sites More sharing options...
fascik 0 Posted November 30, 2020 Author Share Posted November 30, 2020 Sorry - too little coffee So have to delete EVS, GI, vAgent host and redeploy EVS from vcenter? Link to comment Share on other sites More sharing options...
fascik 0 Posted November 30, 2020 Author Share Posted November 30, 2020 Ok so I deleted EVS over vCenter console, redeploy, EVS boot up and works fine, activated it over ESMC but none of agentless machines are connected and Gust introspection status is Guest Introspection service not ready. I checked: /etc/init.d/vShield-Endpoint-Mux status and I have: vShield-Endpoint-Mux is running NSX-Context-Engine is running Should I delete Guest introspection and redeploy it? Link to comment Share on other sites More sharing options...
fascik 0 Posted December 1, 2020 Author Share Posted December 1, 2020 Mateus thanks for hint. I deleted EVS and redeploy it, next wait some time and delete GI and redeploy it. Wait some time and all services are UP now and green. Thank You Link to comment Share on other sites More sharing options...
Recommended Posts