The gquery client suite is now supported on eRI.
Summary
login-0$ kinit login-0$ module load gquery login-0$ gquery -t sources login-0$ gquery -t accessions D70077
To use gquery from a Slurm job it is necessary to have acquired the Kerberos ticket and module loaded gquery on the login node first.
Explanation
Historically on legacy HPC, database credentials were stored in the filesystem, and users were probably oblivious to the fact that they were being fetched on their behalf to authenticate with the database.
On eRI authentication is fine-grained per-user, making use of Kerberos tickets. Therefore a Kerberos ticket is required before attempting to run gquery.
The current Kerberos tickets may be viewed using klist. To obtain a ticket in the first instance, it is necessary to pass it through with ssh -o GSSAPIDelegateCredentials=yes (which may only work on WSL, not native Windows ssh nor putty nor MobaXTerm) or request after login with kinit.
Tickets are made available to compute nodes via a Kerberos credentials cache in the user’s home directory, which is set up during module load gquery. The updated cache location is visible in klist.