-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on Amazon Linux for JWT Authentication #2545
Comments
Hello @thunderpycode 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
{ |
Hello @thunderpycode 👋 None of the versions of Shared: Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue. After updating, share the full output of |
Hello @thunderpycode 👋 None of the versions of Shared: Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue. After updating, share the full output of |
@thunderpycode I've googled that error and doesn't seem to be caused by node. Also remember that node 16 is no longer supported: #1985 |
Running sf 14.6 with node 16
On Running : sf org list, getting the error as:
Running sf 14.6 with node 18
node: /lib64/libm.so.6: version
/root/.local/share/sf/client/2.14.6-1f2724e/bin/node: /lib64/libm.so.6: version
|
@thunderpycode oh I think it's because the CLI tries to use
yeah, node 18 only runs on newer kernels, see: #1788 |
Hi @cristiand391 thanks, it's resolved in a local instance but while running Jenkins we are having an error like "unable to convert undefined or null objects". Also the above mentioned variable is also set at the env level inside Jenkins. Please help in this if possible |
I'm pretty sure you are hitting this bug: forcedotcom/sfdx-core#969 the fix is available in the current RC (sf v2.15.9), install RC instructions: or you can wait a few hours until it gets promoted to latest stable today. |
this error was fixed in sf v2.15.9, see: https://github.com/forcedotcom/cli/tree/main/releasenotes/#2159-nov-1-2023-stable |
Hi @cristiand391 thanks for the help, that rc version actually helped in Jenkins CI/CD. |
Hello,
While running new sf authentication command in JWT on Amazon Linux facing the error. Details are given below:
Operating System: Amazon Linux 2
CPE OS Name: cpe:2.3:o:amazon:amazon_linux:2
Kernel: Linux 4.14.109-99.92.amzn2.x86_64
Architecture: x86-64
Error Details :*
We encountered a JSON web token error, which is likely not an issue with Salesforce CLI. Here’s the error: Command failed with response:
(secret-tool:31942): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY
{
"architecture": "linux-x64",
"cliVersion": "@salesforce/cli/2.13.9",
"nodeVersion": "node-v16.20.2",
"osVersion": "Linux 4.14.109-99.92.amzn2.x86_64",
"rootPath": "/root/.nvm/versions/node/v16.20.2/lib/node_modules/@salesforce/cli",
"shell": "bash",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.3.9 (core)",
"@oclif/plugin-commands 2.2.28 (core)",
"@oclif/plugin-help 5.2.20 (core)",
"@oclif/plugin-not-found 2.4.3 (core)",
"@oclif/plugin-plugins 3.9.1 (core)",
"@oclif/plugin-search 0.0.23 (core)",
"@oclif/plugin-update 3.2.4 (core)",
"@oclif/plugin-version 2.0.1 (core)",
"@oclif/plugin-warn-if-update-available 2.1.1 (core)",
"@oclif/plugin-which 2.2.34 (core)",
"@salesforce/cli 2.13.9 (core)",
"apex 2.3.19 (core)",
"auth 2.8.20 (core)",
"data 2.5.16 (core)",
"deploy-retrieve 1.19.0 (core)",
"info 2.6.49 (core)",
"limits 2.3.38 (core)",
"login 1.2.35 (core)",
"marketplace 0.3.0 (core)",
"org 2.10.12 (core)",
"schema 2.3.29 (core)",
"settings 1.4.33 (core)",
"sobject 0.2.11 (core)",
"source 2.10.40 (core)",
"telemetry 2.3.6 (core)",
"templates 55.5.14 (core)",
"trust 2.6.18 (core)",
"user 2.3.36 (core)"
]
}
The text was updated successfully, but these errors were encountered: