Hi John,
The trailing blank is the cause of the warning that I was focused on,
but otherwise not a problem.
I do recall an issue with a filesystem that squashed group permissions,
causing a failed permission check on some of the files in the config dir.
Try moving ~/.globusonline to a local filesystem and pointing to it when
starting GCP: ./globusconnectpersonal -dir /local/path
I'm hoping the move will preserve the correct permissions, but if not it
may be easiest to recreate the endpoint. In that case you can remove
the endpoint and ~/.globusonline, and then pass -dir /local/path before
-setup to create the new configuration in the desired path.
Mike
On 6/2/2022 1:33 PM, John Bollinger wrote:
>
> Hi Mike,
>
> Thanks for the response. I had not modified any config files by hand,
> but I /had/ added an access path via the File->Preferences panel in
> <
http://relay.globusonline.org:2223>
> > #gridftp 0
> > #relaytool connecting
> > [ssh stderr] Allocated port 45953 for remote forward to
>
127.0.0.1:45683 <
http://127.0.0.1:45683>
> > RELAYTOOL=1 status=CONNECTED ep_display_name=dmiller-personal
> > web_ux_url=https%3A//
app.globus.org <
http://app.globus.org>