Windows Cloud not start the Amazon CloudWatch Agent Services on Local Computar
I have an update with the cloudWatch agent. Make an AMI from a server and deploy a matching server:
specifications Original Server: r6i.4xlarge Cloned Server: r6i.2xlarge OS: Windows Server 2012 R2
At the time of lifting this new server I realize that the CLouWatch is not generating data, so I proceed to check the role of IAM in the EC2, which has the appropriate permissions, I check if the metrics of memory and disks and I find that everything is correct.
Then when I enter the server I notice that the cloudWatch agent service is not running, so I proceed to try to raise it and the following error appears: "Error 1053: The Service did not respond to the start or control request in a timely fashion".
Try:
- repair the agent from the control panel; it did not work.
- reinstall agent; did not work.
- Clean install with reboot; did not work.
Could you please give me an indication of why this failure occurs and how to fix it.
- Newest
- Most votes
- Most comments
Hi,
I found the following document which may be helpful to your problem:
The CloudWatch agent won't start on Windows Server
On Windows Server, you might see the following error:
Start-Service : Service 'Amazon CloudWatch Agent (AmazonCloudWatchAgent)' cannot be started due to the following
error: Cannot start service AmazonCloudWatchAgent on computer '.'.
At C:\Program Files\Amazon\AmazonCloudWatchAgent\amazon-cloudwatch-agent-ctl.ps1:113 char:12
+ $svc | Start-Service
+ ~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
ServiceCommandException
+ FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand
To fix this, first make sure that the server service is running. This error can be seen if the agent tries to start when the server service isn't running.
If the server service is already running, the following may be the issue. On some Windows Server installations, the CloudWatch agent takes more than 30 seconds to start. Because Windows Server, by default, allows only 30 seconds for services to start, this causes the agent to fail with an error similar to the following:
To fix this issue, increase the service timeout value. For more information, see A service does not start, and events 7000 and 7011 are logged in the Windows event log.
This error occurs when your cloudwatch agent configuration is invalid.
I would check the json carefully and even recreate the configuration file using the agent wizard.
Once corrected the agent will start up successfully.
I did the reconfiguration process and it still does not work, I attach the .json:
{ "logs": { "logs_collected": { "windows_events": { "collect_list": [ { "event_format": "xml", "event_name": "System", "log_group_name": "System", "log_stream_name": "{instance_id}", "retention_in_days": -1 } ] } } }, "metrics": { "aggregation_dimensions": [ [ "InstanceId" ] ], "append_dimensions": { "AutoScalingGroupName": "${aws:AutoScalingGroupName}", "ImageId": "${aws:ImageId}", "InstanceId": "${aws:InstanceId}", "InstanceType": "${aws:InstanceType}" }, "metrics_collected": { "LogicalDisk": { "measurement": [ "% Free Space" ], "metrics_collection_interval": 10, "resources": [ "*" ] }, "Memory": { "measurement": [ "% Committed Bytes In Use" ], "metrics_collection_interval": 10 } } } }
Relevant content
- asked 4 months ago
- asked 6 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 15 days ago
I performed the process indicated by microsoft; it did not work.