You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Failed installation : Illegal instruction (core dumped) on Linux ARM64 #8008
$ gdb /usr/local/aws-cli/v2/current/dist/aws
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Reading symbols from /usr/local/aws-cli/v2/current/dist/aws...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/local/aws-cli/v2/dist/aws
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
process 11080 is executing new program: /usr/local/aws-cli/v2/dist/aws
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
OPENSSL_cpuid_setup () at /aws-crt-python/crt/aws-lc/crypto/fipsmodule/cpucap/cpu_aarch64_linux.c:132132 /aws-crt-python/crt/aws-lc/crypto/fipsmodule/cpucap/cpu_aarch64_linux.c: No such file or directory.
Hi @dennis-glx thanks for reaching out. I think the Illegal instruction (core dumped) could indicate a compatibility issue with your architecture. Have you tried installing on another system? It might also be worth opening in an issue in the aws-crt-python repository given the output shared above.
Based on the line number cpu_aarch64_linux.c:132 I believe you are hitting the same MIDR_EL1 issue that Valgrind was hitting. This was fixed in aws/aws-lc#1006 which was released in v1.10.0 of AWS-LC. The most recent version of the Python CRT includes aws-lc @ 80c3943 which is v1.11.0 which includes the fix. Can you try updating to a newer version of the AWS CLI?
@andrewhop , I'm also getting the same issue when installing aws-cli v2 on arm64 processor. This is impacting our production. Can you please investigate and let us know the resolution.
It appears we may have hit this issue and managed to workaround it by installing an earlier version of awscli . Tested with version 2.0.30 , 2.3.0, 2.4.0, 2.8.0, 2.11.0 , 2.11.10, 2.11.12 and 2.11.13 which appear to be working .
Issue appears to occurs from release 2.11.14 on wards .
After further research by the team it appears that increasing the awscrt version ceiling should address this. Here is the PR for that: #8056. A related PR (aws/aws-lc#1006) was referenced in an earlier comment as well as awscrt v0.16.18.
after further research by the team it appears that the corrupted coding is now being settled by the clients end and also the mono-log was shifted to the server.it seems the issue is been settled now and if it reappears i will handle it by sanctioning it to the core team and log.
update awscrt requirements by the team it appears that the corrupt coding is now being settled by the clients end and also thr mono log was shifted to the servent it seems the issue is been settled now and if it reappears i will handle it by sanctioning it to the core team in it and remaining log modules.
The awscrt ceiling was raised to 0.19.12 in #8324. This should now be resolved in v2.13.35+ (CHANGELOG for reference.) If anyone is still seeing this or related issues please let us know. Thanks!
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Activity
tim-finnigan commentedon Jul 3, 2023
Hi @dennis-glx thanks for reaching out. I think the
Illegal instruction (core dumped)could indicate a compatibility issue with your architecture. Have you tried installing on another system? It might also be worth opening in an issue in the aws-crt-python repository given the output shared above.andrewhop commentedon Jul 6, 2023
What CPU are you attempting to install the CLI on, can you run
lscpuand attach the output?andrewhop commentedon Jul 6, 2023
Based on the line number
cpu_aarch64_linux.c:132I believe you are hitting the same MIDR_EL1 issue that Valgrind was hitting. This was fixed in aws/aws-lc#1006 which was released in v1.10.0 of AWS-LC. The most recent version of the Python CRT includes aws-lc @ 80c3943 which is v1.11.0 which includes the fix. Can you try updating to a newer version of the AWS CLI?Dennis-Johnson commentedon Jul 7, 2023
Sure.
Dennis-Johnson commentedon Jul 7, 2023
If it helps, I ran the test code from the LC repo issue you mentioned.
Output
hwcap = 73727 HWCAP_CPUID = 2048 hwcap & HWCAP_CPUID = 2048 armv8_cpuid_probe = 1309605952ArivCR7 commentedon Jul 21, 2023
@andrewhop , I'm also getting the same issue when installing aws-cli v2 on arm64 processor. This is impacting our production. Can you please investigate and let us know the resolution.
jhussainx commentedon Jul 21, 2023
It appears we may have hit this issue and managed to workaround it by installing an earlier version of awscli . Tested with version 2.0.30 , 2.3.0, 2.4.0, 2.8.0, 2.11.0 , 2.11.10, 2.11.12 and 2.11.13 which appear to be working .
Issue appears to occurs from release 2.11.14 on wards .
curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64-2.11.13.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
tim-finnigan commentedon Jul 24, 2023
After further research by the team it appears that increasing the awscrt version ceiling should address this. Here is the PR for that: #8056. A related PR (aws/aws-lc#1006) was referenced in an earlier comment as well as awscrt v0.16.18.
amberkushwaha commentedon Sep 7, 2023
after further research by the team it appears that the corrupted coding is now being settled by the clients end and also the mono-log was shifted to the server.it seems the issue is been settled now and if it reappears i will handle it by sanctioning it to the core team and log.
amberkushwaha commentedon Oct 12, 2023
update awscrt requirements by the team it appears that the corrupt coding is now being settled by the clients end and also thr mono log was shifted to the servent it seems the issue is been settled now and if it reappears i will handle it by sanctioning it to the core team in it and remaining log modules.
tim-finnigan commentedon Nov 20, 2023
The
awscrtceiling was raised to 0.19.12 in #8324. This should now be resolved in v2.13.35+ (CHANGELOG for reference.) If anyone is still seeing this or related issues please let us know. Thanks!github-actions commentedon Nov 20, 2023
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.