Release : 10.0
Component :
It is the Azure waagant trying to set the hostname and filling up the messages log .
to resolved the issue .
check the file
cat /var/lib/waagent/published_hostname
This should have the current hostname as listed in the azure portal if it still has
localhost.localhost or something else.
Delete the file .
restart the waagent using
service waagent stop
service waagent start
Now check the file again
cat /var/lib/waagent/published_hostname
It should now contain the current hostname
if not check the waagent.log
cat /var/log/waagent.log
2022-05-17T09:24:28.187821Z INFO EnvHandler ExtHandler Published hostname record does not exist, creating [/var/lib/waagent/published_hostname] with hostname <hostname>.<yourdomain>.co ]
if it is correct check the messages log for new hostname change messages like
2022-05-17T09:23:04.487696Z INFO EnvHandler ExtHandler EnvMonitor: Detected hostname change: localhost.localdomain -> <hostname>.<yourdomain>.com
This message should not happen anymore .