ShortmeURL - Deployment Failed With Error message: ExitStatusError ExitStatus unix_wait_status 256

Questions and Answers
1

Followed the Qovery youtube tutorial as it is to deploy a demo app, ShortMe URL. But the deployment failed with the following error in the qovery console logs:

Screenshot 2022-03-09 at 12.55.41 PM
Screenshot 2022-03-09 at 12.55.41 PM2374×806 90.5 KB

2

Hi @boloshabashe , can you show me the top of the error message? Do you use Buildpacks?

3

no docker, port 5555

4

Screenshot 2022-03-09 at 1.22.06 PM
Screenshot 2022-03-09 at 1.22.06 PM1920×859 75.6 KB

Screenshot 2022-03-09 at 1.22.13 PM
Screenshot 2022-03-09 at 1.22.13 PM1920×880 63.1 KB

Screenshot 2022-03-09 at 1.22.24 PM
Screenshot 2022-03-09 at 1.22.24 PM1920×694 40.2 KB

Can’t see any nodes under the nodes group, is it normal?

5

Under instances tab I can see three nodes running! So why they are not showing under the nodes group?
Can this be an issue?

Screenshot 2022-03-09 at 1.25.38 PM
Screenshot 2022-03-09 at 1.25.38 PM1920×240 41.6 KB

6

@Pierre_Mavro can you give the steps to get access to the nodes?

7

09 Mar, 15:44:09.582
test
DEPLOYMENT_IN_PROGRESS
| ^~~~~~~~
09 Mar, 15:44:09.582
test
DEPLOYMENT_IN_PROGRESS
ast27/Custom/typed_ast.c:81:1: warning: ‘err_input’ defined but not used [-Wunused-function]
09 Mar, 15:44:09.582
test
DEPLOYMENT_IN_PROGRESS
81 | err_input(perrdetail *err)
09 Mar, 15:44:09.582
test
DEPLOYMENT_IN_PROGRESS
| ^~~~~~~~~
09 Mar, 15:44:09.583
test
DEPLOYMENT_IN_PROGRESS
ast27/Custom/typed_ast.c:66:12: warning: ‘PARSER_FLAGS’ defined but not used [-Wunused-function]
09 Mar, 15:44:09.583
test
DEPLOYMENT_IN_PROGRESS
66 | static int PARSER_FLAGS(PyCompilerFlags *flags)
09 Mar, 15:44:09.583
test
DEPLOYMENT_IN_PROGRESS
| ^~~~~~~~~~~~
09 Mar, 15:44:09.583
test
DEPLOYMENT_IN_PROGRESS
error: command ‘/usr/bin/gcc’ failed with exit code 1
09 Mar, 15:44:09.583
test
DEPLOYMENT_IN_PROGRESS

09 Mar, 15:44:09.584
test
DEPLOYMENT_IN_PROGRESS
ERROR: Command errored out with exit status 1: /usr/local/bin/python -u -c ‘import io, os, sys, setuptools, tokenize; sys.argv[0] = ‘"’"’/tmp/pip-install-kyordp90/typed-ast_b3a7f4274c9145308922bc168d6bb92d/setup.py’"’"’; file=’"’"’/tmp/pip-install-kyordp90/typed-ast_b3a7f4274c9145308922bc168d6bb92d/setup.py’"’"’;f = getattr(tokenize, ‘"’"‘open’"’"’, open)(file) if os.path.exists(file) else io.StringIO(’"’"‘from setuptools import setup; setup()’"’"’);code = f.read().replace(’"’"’\r\n’"’"’, ‘"’"’\n’"’"’);f.close();exec(compile(code, file, ‘"’"‘exec’"’"’))’ install --record /tmp/pip-record-2vig_00y/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.10/typed-ast Check the logs for full command output.
09 Mar, 15:44:09.761
test
DEPLOYMENT_IN_PROGRESS
WARNING: You are using pip version 21.2.4; however, version 22.0.4 is available.
09 Mar, 15:44:09.761
test
DEPLOYMENT_IN_PROGRESS
You should consider upgrading via the ‘/usr/local/bin/python -m pip install --upgrade pip’ command.
09 Mar, 15:44:10.557
test
DEPLOYMENT_IN_PROGRESS
09 Mar, 15:44:10.557
test
DEPLOYMENT_IN_PROGRESS
The command ‘/bin/sh -c pip install --no-cache-dir -r requirements.txt’ returned a non-zero code: 1
09 Mar, 15:44:10.558
test
DEPLOYMENT_IN_PROGRESS
:x: Container build-0511f632-bacb-4c8a-b5cf-5241c03ba757 (zc3cffe23) failed to be build: ExitStatusError(ExitStatus(unix_wait_status(256)))
09 Mar, 15:44:10.561
test
DEPLOYMENT_ERROR
Execution ID: 3939530f-241f-47a1-92cb-902639f5313b-1-1646820792

~~ THIS IS AN INTERNAL ERROR, THE SUPPORT TEAM HAS BEEN ALERTED ~~

MESSAGE FOR QOVERY TEAM:
    * Execution ID: 3939530f-241f-47a1-92cb-902639f5313b-1-1646820792
    * Scope: Build platform 'build-0511f632-bacb-4c8a-b5cf-5241c03ba757' with id 'zc3cffe23'
    * Rollback message: 

❌ ❌ ❌ MESSAGE FOR THE USER ❌ ❌ ❌

    ✉️ Error message: ExitStatusError(ExitStatus(unix_wait_status(256)))
    💬 Need help: If you need assistance, you can reach the support team on Discord (https://discord.qovery.com) or on the Qovery console (https://console.qovery.com) with the integrated chat.
8

Did not get it? I just used the aws console to visit the EKS cluster and then checked the ec2 instances. Under the cluster node group i usually see the nodes when i create eks cluster and node group directly via the aws console, but i guess qovery created the cluster and node group, but under the nodes group the nodes are not mentioned. So what steps you are talking about?

9
09 Mar, 16:39:18.859 Test DEPLOYMENT_IN_PROGRESS PyMem_Free
09 Mar, 16:39:18.859 Test DEPLOYMENT_IN_PROGRESS At top level:
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ast27/Custom/typed_ast.c:201:1: warning: ‘err_free’ defined but not used [-Wunused-function]
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS 201 err_free(perrdetail *err)
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ^~~~~~~~
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ast27/Custom/typed_ast.c:81:1: warning: ‘err_input’ defined but not used [-Wunused-function]
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS 81 err_input(perrdetail *err)
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ^~~~~~~~~
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ast27/Custom/typed_ast.c:66:12: warning: ‘PARSER_FLAGS’ defined but not used [-Wunused-function]
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS 66 static int PARSER_FLAGS(PyCompilerFlags *flags)
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ^~~~~~~~~~~~
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS error: command ‘/usr/bin/gcc’ failed with exit code 1
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ----------------------------------------
09 Mar, 16:39:18.860 Test DEPLOYMENT_IN_PROGRESS ERROR: Command errored out with exit status 1: /usr/local/bin/python -u -c ‘import io, os, sys, setuptools, tokenize; sys.argv[0] = ‘"’"’/tmp/pip-install-nnzj4gxj/typed-ast_23d8359c28a84288975c8ec642a7e47d/setup.py’"’"’; file=’"’"’/tmp/pip-install-nnzj4gxj/typed-ast_23d8359c28a84288975c8ec642a7e47d/setup.py’"’"’;f = getattr(tokenize, ‘"’"‘open’"’"’, open)(file) if os.path.exists(file) else io.StringIO(’"’"‘from setuptools import setup; setup()’"’"’);code = f.read().replace(’"’"’\r\n’"’"’, ‘"’"’\n’"’"’);f.close();exec(compile(code, file, ‘"’"‘exec’"’"’))’ install --record /tmp/pip-record-cw8u8g8k/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.10/typed-ast Check the logs for full command output.
09 Mar, 16:39:18.983 Test DEPLOYMENT_IN_PROGRESS WARNING: You are using pip version 21.2.4; however, version 22.0.4 is available.
09 Mar, 16:39:18.983 Test DEPLOYMENT_IN_PROGRESS You should consider upgrading via the ‘/usr/local/bin/python -m pip install --upgrade pip’ command.
09 Mar, 16:39:19.497 Test DEPLOYMENT_IN_PROGRESS
09 Mar, 16:39:19.497 Test DEPLOYMENT_IN_PROGRESS The command ‘/bin/sh -c pip install --no-cache-dir -r requirements.txt’ returned a non-zero code: 1
09 Mar, 16:39:19.497 Test DEPLOYMENT_IN_PROGRESS :x: Container build-84197fb4-6b2e-4f74-9e64-e62413a13f25 (zffea9fb8) failed to be build: ExitStatusError(ExitStatus(unix_wait_status(256)))
09 Mar, 16:39:19.501 prod DEPLOYMENT_ERROR Execution ID: 00fa5903-99c3-4156-b470-0143f4ec0793-1-1646824118

------------------------------------------------------------------------------- ~~ THIS IS AN INTERNAL ERROR, THE SUPPORT TEAM HAS BEEN ALERTED ~~ MESSAGE FOR QOVERY TEAM: * Execution ID: 00fa5903-99c3-4156-b470-0143f4ec0793-1-1646824118 * Scope: Build platform ‘build-84197fb4-6b2e-4f74-9e64-e62413a13f25’ with id ‘zffea9fb8’ * Rollback message: ------------------------------------------------------------------------------- :x: :x: :x: MESSAGE FOR THE USER :x: :x: :x: :email: Error message: ExitStatusError(ExitStatus(unix_wait_status(256))) :speech_balloon: Need help: If you need assistance, you can reach the support team on Discord (https://discord.qovery.com) or on the Qovery console (https://console.qovery.com) with the integrated chat.|

Screenshot 2022-03-09 at 4.41.42 PM
Screenshot 2022-03-09 at 4.41.42 PM1920×1575 95 KB

SAME ERROR WHILE DEPLOYING THE APP TO DIGITAL OCEAN

10

At the moment, the issue is on our side. It’s an authorization issue on AWS cc @Enzo . Nodes should be visible as you can see them in AWS. It will be fixed in the coming weeks.

Thanks for the report

11

09 Mar, 18:26:37.162
demoo
DEPLOYMENT_IN_PROGRESS
WARNING: Running pip as the ‘root’ user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: 12. Virtual Environments and Packages — Python 3.10.2 documentation
09 Mar, 18:26:39.544
demoo
DEPLOYMENT_IN_PROGRESS
Removing intermediate container 1f918871e638
09 Mar, 18:26:39.544
demoo
DEPLOYMENT_IN_PROGRESS
—> bf08d3d534ae
09 Mar, 18:26:39.544
demoo
DEPLOYMENT_IN_PROGRESS
Step 9/12 : COPY djangofollow /usr/src/app/
09 Mar, 18:26:39.765
demoo
DEPLOYMENT_IN_PROGRESS
—> 60ed3e80efdd
09 Mar, 18:26:39.765
demoo
DEPLOYMENT_IN_PROGRESS
Step 10/12 : COPY entrypoint.sh /usr/src/app
09 Mar, 18:26:39.945
demoo
DEPLOYMENT_IN_PROGRESS
—> 2340018da9de
09 Mar, 18:26:39.945
demoo
DEPLOYMENT_IN_PROGRESS
Step 11/12 : EXPOSE 8000
09 Mar, 18:26:40.005
demoo
DEPLOYMENT_IN_PROGRESS
—> Running in 43b391ad4258
09 Mar, 18:26:40.106
demoo
DEPLOYMENT_IN_PROGRESS
Removing intermediate container 43b391ad4258
09 Mar, 18:26:40.106
demoo
DEPLOYMENT_IN_PROGRESS
—> cbcc560bd79e
09 Mar, 18:26:40.106
demoo
DEPLOYMENT_IN_PROGRESS
Step 12/12 : ENTRYPOINT ["./entrypoint.sh"]
09 Mar, 18:26:40.148
demoo
DEPLOYMENT_IN_PROGRESS
—> Running in fe81e5ddebe6
09 Mar, 18:26:40.319
demoo
DEPLOYMENT_IN_PROGRESS
Removing intermediate container fe81e5ddebe6
09 Mar, 18:26:40.320
demoo
DEPLOYMENT_IN_PROGRESS
—> 39f7b8caa2ff
09 Mar, 18:26:40.323
demoo
DEPLOYMENT_IN_PROGRESS
Successfully built 39f7b8caa2ff
09 Mar, 18:26:40.334
demoo
DEPLOYMENT_IN_PROGRESS
Successfully tagged zbabf9f28:2695210642633984668-bafafd0e2ab61282f38837058d63d22e1b770a45
09 Mar, 18:26:40.343
demoo
DEPLOYMENT_IN_PROGRESS
Successfully tagged zbabf9f28:latest
09 Mar, 18:26:40.347
demoo
DEPLOYMENT_IN_PROGRESS
:white_check_mark: Container build-84197fb4-6b2e-4f74-9e64-e62413a13f25 (zffea9fb8) is built
09 Mar, 18:26:40.640
demo
DEPLOYMENT_ERROR
Execution ID: 399cb26d-b156-4a4f-80d3-3d1dfb7b9279-2-1646830561

~~ THIS IS AN INTERNAL ERROR, THE SUPPORT TEAM HAS BEEN ALERTED ~~

MESSAGE FOR QOVERY TEAM:
    * Execution ID: 399cb26d-b156-4a4f-80d3-3d1dfb7b9279-2-1646830561
    * Scope: Container registry 'registry-the-one-and-unique' with id 'z453e6efd'
    * Rollback message: 

❌ ❌ ❌ MESSAGE FOR THE USER ❌ ❌ ❌

    ✉️ Error message: Incorrect Status received from Digital Ocean when tyring to get container registry
    💬 Need help: If you need assistance, you can reach the support team on Discord (https://discord.qovery.com) or on the Qovery console (https://console.qovery.com) with the integrated chat.

Screenshot 2022-03-09 at 6.36.02 PM
Screenshot 2022-03-09 at 6.36.02 PM1920×1035 88.4 KB

Screenshot 2022-03-09 at 6.36.37 PM
Screenshot 2022-03-09 at 6.36.37 PM2344×796 119 KB

Screenshot 2022-03-09 at 12.55.41 PM
Screenshot 2022-03-09 at 12.55.41 PM2374×806 90.5 KB

ERROR WITH DIGITAL OCEAN TOO :frowning:

I am facing error with the digital ocean too :frowning: Maybe i am doing something wrong, i used this GitHub - boloshabashe/ShortMe-URL-Shortener: A Flask web app and API used to shorten long URLs. repo to deploy the app as per the youtube tutorial on aws as well as digital ocean but both times deployment failed :frowning: Any