Re: [HTCondor-users] condor_chirp throwing error from interactive jobs

[John M Knoeller <johnkn@xxxxxxxxxxx>]

the job execution sandbox has a  file  .chirp.config  which has the IP, PORT and secret  that condor_chirp should use to connect to the starter for the purpose of sending chirp commands. 

when you say session token,  do you mean the secret in the .chirp.config file?

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Thomas Hartmann <thomas.hartmann@xxxxxxx>
Sent: Monday, May 26, 2025 5:28 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] condor_chirp throwing error from interactive jobs

 

Hi all,

I just stumbled over an issue, where condor_chirp throws an error when
being run from the command line in an interactive job. The same
condor_chirps work, when run from an non-interactive script as executable.

In principle, I can talk to the starter from within the interactive job
on its port using the job's session token (grabbed from strace) [1]. At
least the authz with the job token against the listening starter seems
to work, but all the chirp commands just get "-8" thrown back. The
behaviour is the same when entering the starter's namespaces from root
and talking from there to the starter

Is this an expected behaviour? ð
(Condor is on 24.3.0)

Cheers,
   Thomas

[1]
[hartmath@batch1057 tmp]$ telnet 127.0.0.1 38971
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
cookie condorsessiontokenstring
0
whoami
-8
whoami 5120
-8
ulog "test baz foo zworp"
-8
^]
telnet> Connection closed.