VlP 0 Posted August 29, 2019 Share Posted August 29, 2019 Hello, In ESMC, one server is reporting modules not updated: But when I login to remote server, ESET is resporting that everythnig is fine: Why is not module status updated in ESMC? Thanks, VP Link to comment Share on other sites More sharing options...
Administrators Marcos 5,189 Posted August 29, 2019 Administrators Share Posted August 29, 2019 Please click on "Not updated", take a screen shot of the screen and post it. Maybe it's agent that doesn't have the modules updated. Link to comment Share on other sites More sharing options...
VlP 0 Posted August 29, 2019 Author Share Posted August 29, 2019 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,189 Posted August 29, 2019 Administrators Share Posted August 29, 2019 Ok, now click Alerts and then check what product reports it: Link to comment Share on other sites More sharing options...
VlP 0 Posted August 29, 2019 Author Share Posted August 29, 2019 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,189 Posted August 29, 2019 Administrators Share Posted August 29, 2019 It obviously comes from our security product, not from agent. Please expand the column "Problem detail" to get the whole message. If you check the event log of the client, there will be probably more records about recent module updates failing. Link to comment Share on other sites More sharing options...
VlP 0 Posted August 29, 2019 Author Share Posted August 29, 2019 There was problem with disk space yesterday, but now plenty of space is available on system disk... Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted September 2, 2019 ESET Staff Share Posted September 2, 2019 What might help is to restart the machine (as restarting of the ESMC agent service is not possible). If that does not help, we will need to investigate why the data fails to replicate correctly, and the record is stalled (you see it was reported on August 27, but is not gone day after). Link to comment Share on other sites More sharing options...
VlP 0 Posted September 2, 2019 Author Share Posted September 2, 2019 Yes, after restart problem with modules disappeared. ESMC agent is also reporting information about free space on system disk correctly now (via dynamic group). Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted September 2, 2019 ESET Staff Share Posted September 2, 2019 I will check with the development team, about what is the interval this information is shared between the agent / server. AFAIK some of the information is replicated only every 24 hours, which might be the cause. I will track a bug in that case, as it should replicate upon every significant change. Link to comment Share on other sites More sharing options...
VlP 0 Posted September 2, 2019 Author Share Posted September 2, 2019 It was more then 24h after freeing up space on system disk and ESMC still reported modules update failed... Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted September 2, 2019 ESET Staff Share Posted September 2, 2019 I have discussed this with development team. They suggest that you report this as a customer care ticket in case this issue happens again. Just to prevent any misunderstanding, how are the following settings configured on your Endpoint: - Update / Basic / Outdated Detection Engine Alerts / Database Age (what is the configured value?) - User Interface / User Interface Elements / Statuses / Application Statuses / Update (information about product being not out of date). If they are both kept in defaults, we will try to analyze it internally whether they are any implementation hiccups. Link to comment Share on other sites More sharing options...
VlP 0 Posted September 4, 2019 Author Share Posted September 4, 2019 There are settings, both are on defaults: Application statuses: all are enabled Link to comment Share on other sites More sharing options...
.thumb.jpg.d0dae4df7d520793aba4b217c88691a6.jpg)
Recommended Posts