Device name already exists changed to

[brunold]

This happens normally when you register one host against the zlm server, stop zmd, delete the deviceid and secret file, start zmd and register it again against the zlm server without deleting the existing device in the zlm web interface.

What happens at this time is that the zlm client registers with the deviceid and the secret against the zlm server. In the web interface you see the hostname of it. If you open the details, you see the guid of the host which equals the deviceid.

When the zlm client communicates with the zlm server it uses the deviceid and the secret to login and query the bundles, catalogs and policies assigned to it.

So now when the zlm client is stopped, the files deleted, the zlm recreates them the next time it is started. After registering against the zlm server, it tries to login with the new deviceid and the new secret. There is already such a host entry, therefor it renames one and register with the new values again.

Do you have maybe a cron job or something that deletes those files and restarts the zlm client ?

Rainer