Re: [Globus Discuss] Starting globus compute on reboot

[Lei Wang]

Hi Anthony,

The installation process should have asked you to authenticate during the setup process when enabling systemd, and the tokens generated (stored locally in ~/.globus_compute) will refresh themselves accordingly unless there was a specific timeout policy associated.

If there are no abnormal circumstances, the refresh tokens should have lasted up to a year.

Try stopping the service, globus-compute-endpoint logout and then globus-compute-endpoint login then restarting the service after refreshing the credentials.

Lei

On Mon, Mar 3, 2025 at 9:26 AM Anthony Weaver <awea...@fandm.edu> wrote:

I am setting up my globus compute endpoint to try to start automatically on reboot and it keeps failing.  Looking at the logs the startup is trying do an authentication (prints a link and waits for the authentication).  The instructions here

https://globus-compute.readthedocs.io/en/2.6.0/endpoints.html#restarting-endpoint-when-machine-restarts

do not mention how to handle this.  Any help would be appreciated

[Lei Wang]

Hi Anthony,

For additional context other than the generic 'turn it off and on again' fix, there may be some other scenarios, common or otherwise, that can generate auth related errors.

* If you are using systemctl to enable the service, ensure that the user who configured the endpoint is the same uid that is running it.  ie. Not running the systemd service as root while the endpoint was created/logged in using your own credentials.

* That this is a single user, not multi-user endpoint.  The latter should mostly be run as root, as running as a non-privileged user is a special case

* The endpoint was not intended to run using a Client ID/Secret, which is the normal recommendation to avoid credential timeout

If none of these apply and the issue persists, then I suggest creating an official support ticket so we can look into your diagnostic logs to find the actual cause.

Lei

[Anthony Weaver]

Lei,

I made some adjustments to the compute endpoint to make it a multi-user endpoint instead of a single user endpoint and the enable on boot for that was fine.

I needed a MEP anyway for the flow I was working on to work for other users.  My guess is, if I had done the authentication first like you said, then I wouldn't have had an issue

with the single user endpoint. 

As always, thank you for responding

Tony