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

[John M Knoeller <johnkn@xxxxxxxxxxx>]

I think you need to use the chirp client  and not telnet,  -8 is the error code for invalid request, which most likely means that telnet is sending characters with the comand that the server is not expecting. 

if you enable D_SYSCALLS in STARTER_DEBUG,  you will see the lines with " IOProxyHandler: request:"   logged for each chirp command.  

-tj

---

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

Hi Tj

On 27/05/2025 19.45, John M Knoeller via HTCondor-users wrote:
> 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?

yes, I had picked the port and the secret from the file as debug, why
using condor_chirp from within an interactive job failed. For
handshaking via telnet I sent the secret to the starter and got a
response, that I interpreted as success; however all the following
condor_chirp commands failed for me (only getting a "-8"s as responses).
 From a non-interactive job, I was able to chirp successful.

Cheers,
   Thomas