Can not creating machine in ClusterODM on AWS

ODM
1

Hello there,

I was try to using ClusterODM on AWS EC2 and S3 but I had falling some error like this log.
I don’t know what’s the problem.

my environment is OnDemand EC2 for dummy NodeODM on Docker and ClusterODM.

SOME BODY HELP ME :cry::cry::cry:

2019-08-28T09:08:24.124Z - debug: Running pre-create checks...
2019-08-28T09:08:24.289Z - debug: Creating machine...
2019-08-28T09:08:24.343Z - debug: (clusterodm-12-jZveZmLSq6XfvtxpKkkBZi) Launching instance...
2019-08-28T09:08:25.034Z - debug: (clusterodm-12-jZveZmLSq6XfvtxpKkkBZi) Waiting for spot instance...
2019-08-28T09:08:30.253Z - debug: (clusterodm-12-jZveZmLSq6XfvtxpKkkBZi) Created spot instance request sir-6esinsmh
2019-08-28T09:08:36.780Z - debug: Waiting for machine to be running, this may take a few minutes...
2019-08-28T09:08:36.817Z - debug: Detecting operating system of created instance...
Waiting for SSH to be available...
2019-08-28T09:11:40.819Z - debug: Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded
2019-08-28T09:11:41.630Z - warn: Cannot create machine: Error: docker-machine exited with code 1
2019-08-28T09:11:41.630Z - debug: Running: docker-machine rm -y -f clusterodm-12-jZveZmLSq6XfvtxpKkkBZi
2019-08-28T09:11:41.672Z - debug: About to remove clusterodm-12-jZveZmLSq6XfvtxpKkkBZi
WARNING: This action will delete both local reference and remote instance.
2019-08-28T09:11:41.936Z - debug: Successfully removed clusterodm-12-jZveZmLSq6XfvtxpKkkBZi
2019-08-28T09:11:51.938Z - debug: Running: docker-machine rm -y clusterodm-12-jZveZmLSq6XfvtxpKkkBZi
2019-08-28T09:11:51.978Z - debug: About to remove clusterodm-12-jZveZmLSq6XfvtxpKkkBZi
WARNING: This action will delete both local reference and remote instance.
2019-08-28T09:11:51.978Z - debug: Error removing host "clusterodm-12-jZveZmLSq6XfvtxpKkkBZi": Docker machine "clusterodm-12-jZveZmLSq6XfvtxpKkkBZi" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
2019-08-28T09:11:51.980Z - warn: Could not remove docker-machine, it's likely that the machine was not created, but double-check!
2019-08-28T09:11:51.980Z - warn: Cannot create node via autoscaling: Cannot create machine (attempted 1 times)
2019-08-28T09:11:51.980Z - debug: Added fc416799-2707-4331-9a12-f08e3e8f4a83 --> {"taskInfo":{"uuid":"fc416799-2707-4331-9a12-f08e3e8f4a83","name":"Task of 2019-08-28T09:08:23.830Z","dateCreated":1566983303830,"status":{"code":30},"options":[],"imagesCount":12},"output":["No nodes available (attempted to autoscale but failed). Try again later."]} in task table
2019-08-28T09:11:51.980Z - warn: Cannot forward task fc416799-2707-4331-9a12-f08e3e8f4a83 to processing node localhost:3001: No nodes available (attempted to autoscale but failed). Try again later.
2

Mm, how does your ASR configuration file look like? Perhaps this is relevant: Update aws.md by Jeongyong-park · Pull Request #35 · OpenDroneMap/ClusterODM · GitHub

3

Thank you for answer, but I think. this case is different from like this thread.

perhaps the docker-machine does not run properly under certain Linux environments.

4

ok
ok980×512 11.5 KB

I just try copy and paste this codes and run on my Windows Command Prompt. and Docker-machine was running. but not running on Ubuntu 18.04 in AWS EC2

docker-machine create --driver amazonec2 --amazonec2-access-key <Access-Key> --amazonec2-secret-key <Secret-Key> --amazonec2-region ap-northeast-2 --amazonec2-ami ami-034a529df1a711653 --amazonec2-instance-type t3a.micro --amazonec2-root-size 10 --amazonec2-security-group cluster-odm-sg --amazonec2-monitoring --amazonec2-request-spot-instance --amazonec2-spot-price 0.01 --amazonec2-tags type,clusterodm clusterodm-13-eA9j33zATD4eX7x3f7mnyL
5

solved.

I was found error message by debug parameter to docker-machine.

docker-machine --debug

In my case, I was run clusterodm in nodejs without docker on clean ubuntu 18.04 images and printed error message like “Could not get lock /var/lib/dpkg/lock-frontend”. so i was found solution by googling

referenced:

1 Like