Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Hasse_Haglund
Participant

Ghost log server object in MDS

Hi, 

 

I have case running with the "Checkpoint Technical Account service " for almost a month now regarding an ghost object that I have in our Multi Domain Server. 

I have deleted multi-domain-server log-server object "srv-nb12393" from the MDS but it is still showing in the GUI.

I have tired to locate the object via "Gui-DBedit" but it doesn't exist, but if I run the "mgmt_cli" show domain name XXX_AB.

The I can see it, "srv-nb12393"

 

uid: "005ef2ce-bfd6-1644-bea8-311c3f98a659"

name: "XXX_AB"

type: "domain"

domain:

  uid: "a0eebc99-afed-4ef8-bb6d-fedfedfedfed"

  name: "System Data"

  domain-type: "mds"

global-domain-assignments:

- uid: "895eae1c-3e7f-4c34-a9f1-fb7f79244ae1"

  type: "global-assignment"

  domain:

    uid: "a0eebc99-afed-4ef8-bb6d-fedfedfedfed"

    name: "System Data"

    domain-type: "mds"

domain-type: "domain"

servers:

- name: "xxx-cma"

  type: "management server"

  ipv4-address: "1.1.1.16"

  multi-domain-server: "fwmgmtXXX"

  active: true

- name: "srv-nb12393"

  type: "log server"

  ipv4-address: "1.1.1.69"

  multi-domain-server: "sec-nb09225"

  active: false

comments: ""

color: "black"

icon: "Objects/domain"

tags: []

meta-info:

  lock: "locked by other session"

  validation-state: "ok"

  last-modify-time:

    posix: 1556545822750

    iso-8601: "2019-04-29T15:50+0200"

  last-modifier: "System"

  creation-time:

    posix: 1556545686399

    iso-8601: "2019-04-29T15:48+0200"

  creator: "System"

read-only: false

 

So I wonder now if anyone of you have had this issue? 

Or does someone have an tip that can help me remove this ghost object? 

 

Thanks

1 Reply
Peter_Lyndley
Advisor
Advisor

I also have a ghost object issue with a log server object. Again been with TAC a while , they managed to get rid of the object, after replication; however now I cannot re-create an object in it's place due to another duplicate entry somewhere in postgres.

I can only suggest asking them to replicate your environment, like they have with ours, until it is fixed.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events