Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 836 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Central has problems with synchronizing objects and/or deletions of objects

BerndFeist

Hello,

I am running the latest Firmware (SFOS 18.5.2 MR-2) on all my production firewalls except one where I am testing 19.0.0_EAP1. Today I created a lot of network object in my overall policy. There were also some mistakes in the naming which led to some deletions.

The distribution is only working to some of the firewalls. Actually all single firewalls are working and I have errors / pending transactions on my two XG 210 Clusters and one of my XG 550 Cluster. The Firewall with the EAP is also fine.


How can this be resolved. Is one error blocking the completion of the other changes.

A retry does not work. Can I skip the error without getting some inconsistencies? How can I find out what is causing the issue? My impression is that only the last change is shown and that this is not causing the issue (If I do more changes I will see another transaction there ...)

What is causing the issue?
What needs to be done to correct these issues?
Could there be a naming Conflict or something like that?
Is one failing task blocking subsequent tasks?

When I saw this in the past I removed the firewall from central and rejoined it. This resolved such kind of issues two times. However it happent too frequently and I do not want to do this all the time :-(.

Regards,
BeEf

Regards,
Bernd



This thread was automatically locked due to age.
  • 0

    Hello Bernd,

    Thank you for reaching out to the Sophos Community Forum.

    Could you re-try the operation so that it fails and then send a screenshot of the details as you've done for the "Pending" screenshot? If the same tasks are already listed under "Failed" you can just expand that section to view the information. 

  • 0 in reply to Qoosh

    1) An error on one Firewall:

    2) Another error on a remote Cluster

    3) A third error on another remote cluster

    In the first and second case I did not see the object on the firewall.
    In the third case an object with that name was there but I still got the error.

    After skipping the failed connections the other transaction run through in the first two cases.

    In the third case several times it ran into then next errors, then some successfull transactions until there was an error again .... Finally the last transactions run thrugh. 

    All cases were using the same policies in which I created the objects. However they behaved differently.