globusconnectpersonal-3.1.6 for linux setup error

342 views
Skip to first unread message

Alyse Larkin

unread,
Apr 15, 2022, 7:25:15 PM4/15/22
to Discuss
Hello, 

I am attempting to install globusconnectpersonal-3.1.6 on a linux platform and I am running in to an error message. After running, "./globusconnectpersonal -setup --no-gui" and sucessfully entering the authorization code I receive the following message as recorded in my register.log: 

"...
[INFO] api_clients.py::91 [create_endpoint] endpoint create succeeded
[INFO] cli.py::196 [main] starting relaytool setup
[WARNING] relaytool.py::136 [invoke_relaytool] relaytool setup exit with status 1, indicating failure. use debug mode for full output
[INFO] cli.py::200 [main] relaytool stdout:
-----
('',)-----
[INFO] cli.py::201 [main] relaytool stderr:
-----
('[ssh stderr] ssh: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory\n',)
-----
[INFO] cli.py::202 [main] full trace of relaytool failure
Traceback (most recent call last):
  File "lib/cli.py", line 198, in main
  File "lib/relaytool.py", line 151, in run_relaytool_setup
  File "lib/relaytool.py", line 146, in invoke_relaytool
lib.relaytool.RelayToolFailureError: ('relaytool setup failed', CompletedProcess(args='/home/larkinsa/globusconnectpersonal-3.1.6/gt_amd64/bin/relaytool', returncode=1, stdout=b'', stderr=b'[ssh stderr] ssh: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory\n'))
[ERROR] cli.py::203 [main] relaytool failed, full error info available in register.log
"

I can see that "libcrypt.so.1.1" is present in the "lib" folder, so perhaps this is a versioning issue within relaytool.py? Any assistance on how to proceed is greatly appreciated. 

Best regards, 

Alyse Larkin

Alyse Larkin

unread,
Apr 15, 2022, 7:44:17 PM4/15/22
to Discuss
So I realized the file and associated link were actually named "libcrypto.so.1.1" in the "lib" folder. I just renamed the file as "libcrypt.so.1," made two new associated links pointing both "libcrypt.so.1" and "libcrypt.so.1.1" to the file, and the setup completed successfully. 

Best, 

Alyse 

Reply all
Reply to author
Forward
0 new messages