Closed ghost closed 2 years ago
noticed this as well - seems cloudproxy.providers.aws.main:aws_check_alive
fails, excerpt from logs below.
It waits and waits and waits and eventually destroys the instance, guessing the check fails for some reason.
2021-10-18 16:52:29.079 | INFO | cloudproxy.providers.aws.main:aws_deployment:32 - Minimum AWS instances met
2021-10-18 16:52:29.212 | INFO | cloudproxy.providers.aws.main:aws_check_alive:85 - Waiting: AWS -> 18.133.140.241
2021-10-18 16:52:29.226 | INFO | cloudproxy.providers.aws.main:aws_check_alive:85 - Waiting: AWS -> 18.132.200.216
2021-10-18 16:52:29.227 | INFO | apscheduler.executors.base:run_job:144 - Job "aws_manager (trigger: interval[0:00:20], next run at: 2021-10-18 16:52:48 UTC)" executed successfully
2021-10-18 16:52:30.108 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:30.111 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:33.373 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:33.376 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:36.149 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:36.153 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:39.036 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:39.040 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:42.443 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:42.460 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:45.141 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:45.145 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:48.248 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52075 - "GET /providers HTTP/1.1" 200
2021-10-18 16:52:48.253 | INFO | uvicorn.protocols.http.h11_impl:send:461 - ***.**.**.**:52166 - "GET /destroy HTTP/1.1" 200
2021-10-18 16:52:48.879 | INFO | apscheduler.executors.base:run_job:123 - Running job "aws_manager (trigger: interval[0:00:20], next run at: 2021-10-18 16:53:08 UTC)" (scheduled at 2021-10-18 16:52:48.878660+00:00)
2021-10-18 16:52:49.109 | INFO | cloudproxy.providers.aws.main:aws_deployment:32 - Minimum AWS instances met
2021-10-18 16:52:49.509 | INFO | cloudproxy.providers.aws.main:aws_check_alive:80 - Destroyed: took too long AWS -> 18.133.140.241
2021-10-18 16:52:49.700 | INFO | cloudproxy.providers.aws.main:aws_check_alive:80 - Destroyed: took too long AWS -> 18.132.200.216
For the info you are providing can be almost anything. The only thing now i have in mind is that possible you are using @ or : on user or password. Try to use only a-Z and 0-9 on them.
This issue is now stale.
Thanks @serk7 for your answer. Will close now.
I think you should be more specific. It has been working correctly for me.