Thread Info
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 10 subscribers
  • Views 4905 views
  • Users 0 members are here
Options
Suggested

Firewall Transaction Details | STATUS: FAILED | EVENT : UPDATE "statusmessage": "record exists"

SGH

Using Sophos Central Firewall Management to make changes to multiple XGS136 (SFOS 20.0.0 GA-Build222)

The Tasks Queue are failed:
Firewall Transaction Details
ID : 123 | STATUS: FAILED | EVENT : UPDATE
ExampleApplicationFilter (Update app filter policy api)
record exists (503)
{
"response": {
"Entity": "applicationfilterpolicy",
"statusmessage": "record exists",
"status": "503",
"Event": "UPDATE"
}
}

Because the statusmessage is "Record Exists" 
The I have deleted the Application filter: ExampleApplicationFilter

Then I click Retry in Task Queue ID : 123

I get the same FAILED message

When I click: Skip (Ignore this failure) 
The Queue got stuck on the next ID #124 with the same FAILED message.

Is it possible to clear all Task Queues?
Is this a known problem?



Added tags
[edited by: Gladys at 2:18 PM (GMT -8) on 1 Jan 2024]
Parents
  • 0

    update1
    I have contacted Sophos support

    He suggested to disconnect the firewall from Sophos Central en reconnect it to have it synchronised.

    The compleet synchronisation took a couple of minutes and finished in the same failed status

    record exists (503)
    {
    "response": {
    "Event": "UPDATE",
    "status": "503",
    "statusmessage": "record exists",
    "Entity": "applicationfilterpolicy"
    }
    }


    Because of new synchronisation this is part of the TASK:

    First ADD and then UPDATE
    What I think is strange that it give no error by ADD filter policy but with UPDATE filter policy
    I expected to fail at ADD filter policy

    {
    "opcodeID": 951,
    "entityID": 552,
    "entityName": "add_app_filter_policy_api",
    "opcodeType": 1,
    "orderID": 1238,
    "opcodeString": "",
    "responseStatus": "{\"status\":\"503\",\"Event\":\"ADD\",\"Entity\":\"applicationfilterpolicy\",\"statusmessage\":\"record exists\"}",
    "uniqueName": "ExampleApplicationFilter apps-552",
    "updateFlag": "f",
    "mainEntity": "t"
    }


    {
    "opcodeID": 948,
    "entityID": 552,
    "entityName": "update_app_filter_policy_api",
    "opcodeType": 1,
    "orderID": 1239,
    "opcodeString": "",
    "responseStatus": "{\"Event\":\"UPDATE\",\"status\":\"503\",\"statusmessage\":\"record exists\",\"Entity\":\"applicationfilterpolicy\"}",
    "uniqueName": "ExampleApplicationFilter apps-552",
    "updateFlag": "t",
    "mainEntity": "t"
    }

Reply
  • 0

    update1
    I have contacted Sophos support

    He suggested to disconnect the firewall from Sophos Central en reconnect it to have it synchronised.

    The compleet synchronisation took a couple of minutes and finished in the same failed status

    record exists (503)
    {
    "response": {
    "Event": "UPDATE",
    "status": "503",
    "statusmessage": "record exists",
    "Entity": "applicationfilterpolicy"
    }
    }


    Because of new synchronisation this is part of the TASK:

    First ADD and then UPDATE
    What I think is strange that it give no error by ADD filter policy but with UPDATE filter policy
    I expected to fail at ADD filter policy

    {
    "opcodeID": 951,
    "entityID": 552,
    "entityName": "add_app_filter_policy_api",
    "opcodeType": 1,
    "orderID": 1238,
    "opcodeString": "",
    "responseStatus": "{\"status\":\"503\",\"Event\":\"ADD\",\"Entity\":\"applicationfilterpolicy\",\"statusmessage\":\"record exists\"}",
    "uniqueName": "ExampleApplicationFilter apps-552",
    "updateFlag": "f",
    "mainEntity": "t"
    }


    {
    "opcodeID": 948,
    "entityID": 552,
    "entityName": "update_app_filter_policy_api",
    "opcodeType": 1,
    "orderID": 1239,
    "opcodeString": "",
    "responseStatus": "{\"Event\":\"UPDATE\",\"status\":\"503\",\"statusmessage\":\"record exists\",\"Entity\":\"applicationfilterpolicy\"}",
    "uniqueName": "ExampleApplicationFilter apps-552",
    "updateFlag": "t",
    "mainEntity": "t"
    }

Children
Unfiltered HTML