Adding new DTNs to existing Endpoints

[Ken Carlile]

Hi folks, 

I'm curious, what steps do you take when you add new new DTN to an existing endpoint to test/ensure that the new node is working correctly? I know I could run self-diagnostic, but that doesn't show the whole picture, and with multiple DTNs, one that is slightly misconfigured seems to be a recipe for very confusing random issues as the endpoint round robins between them. 

Thanks!

--Ken

[Karl Kornel]

Hi Ken,

On our big Lustre environment, those Globus DTNs have a Systemd drop-in, which sets `Require=shine.service` and `After=Shine.service`.  That ensures GridFTP isn’t running until Lustre is online.

For new DTNs that are being deployed, Globus installation is sequenced to happen after everything else is installed.

But honestly, pre-DTN-installation tests could be as simple as: Check storage (check your Mapped Collection base paths are present & listing correctly) and Check LDAP (check `getent some_username` works).  If you use NHC, that’s even better: Make sure the `nhc` command is showing everything is good, before you start DTN installation.

~ Karl

From: dis...@globus.org <dis...@globus.org> on behalf of Ken Carlile <kcar...@gmail.com>
Date: Tuesday, August 11, 2026 at 3:04 PM
To: Discuss <dis...@globus.org>
Subject: [Globus Discuss] Adding new DTNs to existing Endpoints

To unsubscribe from this group and stop receiving emails from it, send an email to discuss+u...@globus.org.