1 of 1 people found this helpful
These appear to be bugs on custom CMDB sync mappings.
Both look like the host was not found but an attempt was sill made to get the host name,
Thanks all for your good contributions.
I've a similar problem, but in my case it's since a particular date that I'm having different errors of different patterns based on different paths and python scripts. In example:
The problem started on February 14 and just we updated the TKU files the day before, but on this moment we don't had any Error Message. I have another appliances on the same enviroment updated the same day with the same files and without this kind of problems. I have rebooted the appliance and the situation persists.
Could any of you give me an idea about a possible solution?
Thanks for your help.
You mean that an individual scan had this problem?
I am not clear how your TKU update time interacted with the scan time.