Hi Andrei,

When upgrading the CloudStack agent you can accept or refuse to change the
agent.properties. The default operation is to not change configuration
files.

The agent service does not impact directly on the running VMs; thus, I
would suggest you remove the /etc/cloudstack/agent/agent.properties file,
uninstall the CloudStack agent service and reinstall it. I would also
suggest you keep a copy of /etc/cloudstack/ just to have a saved state of
your agent configurations before reinstalling and compare them if needed.

Em seg, 22 de out de 2018 às 09:36, Andrei Mikhailovsky
<[email protected]> escreveu:

> Hi
>
> I have an issue with one of the host servers. This issue is rather
> strange. Perhaps someone can help me with understanding how this happened
> and how to fix it.
>
> About 3 days ago one of the KVM host servers ran out of disk space on its
> root partition. I have fixed the issue and reconnected the agent by running
> 'service cloudstack-agent restart'.
>
> I've noticed that the host server is still showing Disconnected status in
> the web gui. The agent log files repeat the following 3 lines every 10 or
> so seconds:
>
> 2018-10-22 12:50:54,339 INFO [cloud.agent.AgentShell] (main:null) (logid:)
> Agent started
> 2018-10-22 12:50:54,343 INFO [cloud.agent.AgentShell] (main:null) (logid:)
> Implementation Version is 4.11.1.0
> 2018-10-22 12:50:54,345 INFO [cloud.agent.AgentShell] (main:null) (logid:)
> agent.properties found at /etc/cloudstack/agent/agent.properties
>
>
> looking further revealed that the file is 0 bytes:
>
> -rw------- 1 root root 0 Oct 20 06:39 agent.properties
> -rwxr-xr-x 1 root root 8890 Jul 6 14:01 agent.properties.dpkg-dist
>
> Something has replaced the original agent.properties file. The
> creation/modification dates of the agent.properties file on other KVM host
> servers are all different (times and dates). As I always upgrade the host
> servers at the same time, this led me to believe that agent.properties file
> is automatically generated or modified by some script or service that is
> running on the host server or perhaps the modification is pushed from the
> management server to the agent.
>
> As the server is in the Disconnected state I can't migrate servers and
> virtual routers from that host server and I can't set it to Maintenance
> either.
>
> How do I manually force the creation / update of the agent.properties file
> on that host server? The challenge is that vms /vrs which are running on
> that host server are production servers and they should keep running
> without shutting down.
>
> Thanks for any tips/help.
>
> Andrei
>

Reply via email to