-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
area/docdbYugabyteDB core featuresYugabyteDB core featureskind/improve-uxIssues relating to improving user experience.Issues relating to improving user experience.priority/mediumMedium priority issueMedium priority issuestatus/awaiting-triageIssue awaiting triageIssue awaiting triage
Description
Jira Link: DB-20302
Description
Due to an oversight on my part, when I was running through the Linux install instructions here I copied the x86 rather than aarch64 command. I am running on an M4 Mac so this was definitely user error.
When I ran post_install.sh I received an error (naturally). The error I received, however, was not immediately clear about what the issue could be:
vscode ➜ /workspace $ cd yugabyte-2025.2.1.0/
vscode ➜ /workspace/yugabyte-2025.2.1.0 $ ./bin/post_install.sh
OpenSSL binary: ./bin/../bin/../bin/openssl
FIPS module: ./bin/../bin/../lib/ossl-modules/fips.so
rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2
./bin/../bin/fips_install.sh: line 44: 21348 Trace/breakpoint trap "$openssl_bin" fipsinstall -out "$out_dir/fipsmodule.cnf" -module "$fips_provider"
It was only when I paid attention and noticed the x86-64 above that I realized my error. Right at first I actually thought it was an error with my machine not being FIPS ready.
Ideally post_install.sh should either error out or at least provide a clear warning about architecture mismatch.
Issue Type
kind/improve-ux
Warning: Please confirm that this issue does not contain any sensitive information
- I confirm this issue does not contain any sensitive information.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/docdbYugabyteDB core featuresYugabyteDB core featureskind/improve-uxIssues relating to improving user experience.Issues relating to improving user experience.priority/mediumMedium priority issueMedium priority issuestatus/awaiting-triageIssue awaiting triageIssue awaiting triage