UDT not working about gct HOT 2 CLOSED

Running strace server side shows that UDT lib is loaded:

openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libfakeroot/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/local/lib/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libglobus_xio_udt_driver.la", O_RDONLY) = -1 ENOENT (No such file or directory)
access("/usr/lib/x86_64-linux-gnu/libglobus_xio_udt_driver.so", R_OK) = 0
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libglobus_xio_udt_driver.so", O_RDONLY|O_CLOEXEC) = 12
openat(AT_FDCWD, "/usr/lib/libudt.so.0", O_RDONLY|O_CLOEXEC) = 12

Running strace client side shows that the "-udt" argument isn't used/processed/...:

execve("~/tools/gct62_selfcompiled/bin/globus-url-copy", ["globus-url-copy", "-dbg", "-udt", "file:/dev/zero", "sshftp://SERVER-IP/dev/null"], 0x7ffc07bc3470 /* 24 vars */) = 0

from gct.

I know that this worked in the past with earlier Globus Toolkit versions (i.e. 5.x or so). But I wonder if this works with sshftp:// and/or using file:/// URLs (which performs a two-party transfer directly between client and server instead of a 3rd party transfer between two servers orchestrated by the client).

Could you try using UDT in a 3rd-party transfer and using gsiftp:// instead?

I think it could be enough to use one GridFTP service/server only, because you can do transfers between the same server and these are not transformed into local copies then AFAIK and you should be also able to have server and client on the same host to simplify things.

You'll need host and client credentials for such a configuration, please follow the Basic Security Configuration to obtain these.

UPDATE: I just recognized that you were using --disable-gsi when configuring the toolkit build. You'll have to rebuild the toolkit without this option during the config run to be able to test with gsiftp://.

from gct.