EventSyncUpdate.logUpdate(554) - Event update request has expired for node

Dear All,

We are getting continously the below error from the one of OMi data collector gateway to the OMi MOM

EventSyncUpdate.logUpdate(554) - Event update request has expired for node

It is related to event forwarding from OMi to OMi (MOM), please help me to resolve this issue.



Labels (1)
3 Replies
Fleet Admiral
Fleet Admiral

Might be a buffer or connection issue. 

  • try BBC ping between the boxes
  • check tcp connectivity
  • check event queue for synchronization updates
Captain Captain

Hi Deepak,

I was facing the same issue but not sure how it helps you.


First Look itself I identified that there is issue with some events which are not processing or event fileds are not updating. I beleive you would be seeing 2 error events at the same time if not then ignore :).

Please see below :

EventSyncUpdate.logUpdate(554) - Event update request has expired for node XYZ.ABC.com. Deleting request from queue for event with ID: fe116ae9-40b3-4fbe-9e75-87f19f53756f 
EventSyncThread.logDeliveryFailure(1519) - Delivery for server XYZ.ABC.com failed to forward event: fe116ae9-40b3-4fbe-9e75-87f19f53756f.  

In my environment, We are forwarding All the OMi events to other events management console(Not OMi). To forward all the events we created event filter where we selects all the lifecycle stats and EPI does rest of the work.

We do have OMi-NNMi intergation and lots of traps comes to OMi directly in Closed state and where issue has identified. The Moment Events comes to OMi event channel our EPI RUN and try to forward to target server. At the same time EPI only process (Active/INprogress/Resolve) events to target server. We indentified that CLosed state events are not forwarding and due to this OMi is generating lots of junk events.

Now I removed the Closed state from the Filter and could not see any error since last 4-5 days.

Well, Again It is depend on the environemnt-2 but I am sharing my findings. hope it helps you. 🙂



Error events hes been stopped by restarting the gatway services.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.