Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Problem

It is seen in recent deployments of IDA services that after a fresh deployments the the keys generated seems to have some issues resulting in errors like “No unique alias“.

Solution

This is issue due to same key getting inserted due to the IDA services starting in parallel. To fix this issue follow the below steps:

  1. Stop IDA services

  2. In the Key Alias table of IDA DB remove any Duplicate entries of key alias, especially KERNEL SIGN.

  3. Start one IDA service such as authentication-internal-service, after it is up then start other services. The first service will create an entry of the key alias, then other service started later will pick it, avoiding creation of duplicate key.

To prevent the issue altogether, start the IDA services one by one after a fresh deployment, it can be started in any order.

This issue will be addressed in forth coming release.

Filter by label

There are no items with the selected labels at this time.

  • No labels