We are using a GOCD AWS ECS elastic agent plugin. GOCD version: GoCD Version: 23.4.0
GoCD Elastic Agent Plugin for Amazon ECS - Version7.3.0-416 - - - - *AMI id: *ami-0ba9fb6bc8faf1fe0 *Elastic instance is coming up and its not getting assigned to ECS cluster, we logged in to server and found the blow error. * [root@ip-******* ~]# systemctl restart docker Job for docker.service failed because start of the service was attempted too often. See "systemctl status docker.service" and "journalctl -xe" for details. To force a start use "systemctl reset-failed docker.service" followed by "systemctl start docker.service" again. [root@ip- ******* ~]# journalctl -xe -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ecs.service has finished shutting down. Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: start request repeated too quickly for docker.service Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has failed. -- -- The result is failed. Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: docker.service failed. Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: Starting Amazon Elastic Container Service - container agent... -- Subject: Unit ecs.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ecs.service has begun starting up. Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: ecs.service: control process exited, code=exited status=1 Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon amazon-ecs-init[6236]: level=info time=2024-09-02T16:03:20Z msg="post-stop" Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon amazon-ecs-init[6236]: level=info time=2024-09-02T16:03:20Z msg="Cleaning up the credentials endpoint setup for Amazon El Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon amazon-ecs-init[6236]: level=error time=2024-09-02T16:03:20Z msg="Error performing action 'delete' for iptables route: ex Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon amazon-ecs-init[6236]: level=error time=2024-09-02T16:03:20Z msg="Error performing action 'delete' for iptables route: ex Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon amazon-ecs-init[6236]: level=error time=2024-09-02T16:03:20Z msg="Error performing action 'delete' for iptables route: ex Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon amazon-ecs-init[6236]: level=error time=2024-09-02T16:03:20Z msg="Error performing action 'delete' for iptables route: ex Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: Failed to start Amazon Elastic Container Service - container agent. -- Subject: Unit ecs.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ecs.service has failed. -- -- The result is failed. Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: Unit ecs.service entered failed state. Sep 02 16:03:20 ip-10-226-11-63.aws.cloud.epsilon systemd[1]: ecs.service failed. [root@ipXXXX ~]# df -hT Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 7.7G 0 7.7G 0% /dev tmpfs tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs tmpfs 7.7G 376K 7.7G 1% /run tmpfs tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup /dev/nvme0n1p1 xfs 100G 2.4G 98G 3% / tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0 [root@ip-10-226-11-63 ~]# docker --version Docker version 25.0.5, build 5dc9bcc BELOW User data script we are using and getting excited while spinning up an error. "ECS_INSTANCE_ATTRIBUTES={"server-id":"31e424ad-e242-45d2-a5bb-0ef7be0d8306"} EOT echo 'File /etc/ecs/ecs.config successfully created.' log "Finished executing GoCD's user data script, now executing custom user data script from use, if present." #!/bin/bash echo "ECS_CLUSTER=GoCD-ECS-UAT" >> /etc/ecs/ecs.config log "Finished executing user specified user data script." --// #cloud-config cloud_final_modules: - [scripts-user, always] --// Content-Type: text/x-shellscript; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="initialize_instance_store" #!/bin/bash exec > >(tee /var/log/initialize_instance_store.log | logger -t user-data -s 2>/dev/console) 2>&1 function log() { echo "[$(date "+%Y-%m-%d %H:%M:%S")] - $1" >> /var/log/initialize_instance_store.log } function try() { $@ return 0 } log "Starting to setup instance store for the docker." INSTANCE_STORES=$(ls /dev/disk/by-id/*EC2_NVMe_Instance_Storage*-ns-1) if [ -z "${INSTANCE_STORES}" ]; then log "No instance store detected." fi VOLUMES="$INSTANCE_STORES" if [ -e "/dev/xvdcz" ]; then log "Instance has /dev/xvdcz EBS volume. Using it for docker logical volume group." VOLUMES="$VOLUMES /dev/xvdcz" fi if [ -z "${VOLUMES}" ]; then log "No addition volumes. Using box standard docker setup." else log "Available instance stores: ${VOLUMES}." log "Setting up the docker logical volume group." service docker stop rm -rf /var/lib/docker/* dmsetup remove_all VOLUME_GROUP=docker LOGICAL_VOLUME=docker-pool try vgremove -y "${VOLUME_GROUP}" try lvremove -y "${LOGICAL_VOLUME}" vgcreate -y "${VOLUME_GROUP}" ${VOLUMES} sleep 2 lvcreate -y -l 5%VG -n ${LOGICAL_VOLUME}\meta ${VOLUME_GROUP} lvcreate -y -l 90%VG -n ${LOGICAL_VOLUME} ${VOLUME_GROUP} sleep 2 lvconvert -y --zero n --thinpool ${VOLUME_GROUP}/${LOGICAL_VOLUME} --poolmetadata ${VOLUME_GROUP}/${LOGICAL_VOLUME}\meta echo 'DOCKER_STORAGE_OPTIONS=" --storage-driver devicemapper --storage-opt dm.thinpooldev=/dev/mapper/docker-docker--pool --storage-opt dm.use_deferred_removal=true --storage-opt dm.use_deferred_deletion=true --storage-opt dm.fs=ext4 --storage-opt dm.use_deferred_deletion=true"' > /etc/sysconfig/docker-storage test -f /bin/systemctl && systemctl reset-failed docker.service service docker restart test -f /bin/systemctl && systemctl enable --no-block --now ecs fi log "Setup completed." --//" -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/f0fecc4e-cfe4-4291-9b19-18753938546fn%40googlegroups.com.
