Skip to main content
Resolve your agent installation issues

Avoid unexpected disruption to your internal scanning

Updated over a month ago

The most common one we see, looks like this:

Link fail: [409] Agent with uuid agentUuid=df3d15c2-97ab-4b5b-a2af-3fc7b5886ee2 attempt to link, but another agent in container containerUuid=ee2f47bd-7354-4fd3-ade6-d318e219dfe7 with different token already exists.. Request UUID: a7c122b168fae5545fdf2811e79c7d3a

Why does this happen?

This is shown in cases where you attempt to link a machine that has already been linked or a cloned machine (where all files, parameters, settings, etc. are exactly the same).

How do I resolve it?

To fix this you’d need to follow the steps in the article linked below in order to reset the UUID and attempt a relinking.

Did this answer your question?