cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

The update failed; see event log (Linux)

Jump to solution

I'm running Endpoint Security for Linux v10.6.6 (Platform, Firewall & Threat Prevention) and Agent v5.6.1.157. I'm seeing the subject event in ePO. In the endpoint's mfetpd.log I see the following:

Oct 09 00:10:05 fcc1014 INFO TpAgentUpdate [2668] Update state event callback has triggered - eventId: 0 severity: 0 updateState: 2 updateError: 0
Oct 09 00:10:05 fcc1014 INFO dispatcher [2668] ma_dispatcher_load 0x7fac78004610 ma_variant:EPOAGENT3000:libma_variant.so
Oct 09 00:10:05 fcc1014 INFO dispatcher [2668] ma_dispatcher_load returns <0>
Oct 09 00:10:05 fcc1014 ERROR MsgBusAgentUpdater [2668] Agent updater getUpdateState failed due to std::exception
Oct 09 00:10:05 fcc1014 ERROR AMUpdater [2668] MA failed to stop update

 

What does this error mean? What's the fix?

1 Solution

Accepted Solutions
Highlighted

Re: The update failed; see event log (Linux)

Jump to solution

After looking further into this, I'm seeing that it is the regularly scheduled DAT update is failing because the DAT version is up to date. It would be very helpful if ePO could indicate this in the event details so I wouldn't have to chase a non-problem. When there is a new DAT available, the update is successful.

Please McAfee, improve your threat events' details as shown in ePO. 

View solution in original post

4 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: The update failed; see event log (Linux)

Jump to solution

Hello,

I would like to request you to please open a Service Request with the Technical Support Team.

https://support.mcafee.com/webcenter/portal/supportportal/pages_home


So we can check the issue and provide you solution.

Was my reply helpful?
If you find this post useful, Please give it a Kudos! l Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 5

Re: The update failed; see event log (Linux)

Jump to solution

@Randy_Bell1  

Can you please let me know if you are seeing DAT being update for the machine or not? As  per my understanding the DAT update has failed because of which you are seeing this event. So if the EPO shows Older DAT information then we just have to work on why the DAT is not getting updated. If you can share the MER log from the machine then we can look into it

Highlighted

Re: The update failed; see event log (Linux)

Jump to solution

Can this issue cause high CPU? I have three servers that shows the same error in log and showing high CPU.

Highlighted

Re: The update failed; see event log (Linux)

Jump to solution

After looking further into this, I'm seeing that it is the regularly scheduled DAT update is failing because the DAT version is up to date. It would be very helpful if ePO could indicate this in the event details so I wouldn't have to chase a non-problem. When there is a new DAT available, the update is successful.

Please McAfee, improve your threat events' details as shown in ePO. 

View solution in original post

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community