Re: [HTCondor-users] condor_tail & remote submit

[Cole Bollig <cabollig@xxxxxxxx>]

Hi Christoph,

You should be able to run a remote Schedd query for condor_tail with the -name <schedd name> to the actual Schedd managing the job. Otherwise, condor_tail tries to query the local Schedd. There is also a -pool <CM name> option if you want to tail a file of a job running in another pool.

For more context, condor_tail queries the Schedd for information about the specified job to use to make a connection to the remote condor_starter. The tool actually receives the file data directly from the EP.

Hope this helps,

Cole Bollig

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Beyer, Christoph <christoph.beyer@xxxxxxx>
Sent: Friday, January 12, 2024 4:13 AM
To: htcondor-users <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] condor_tail & remote submit

 

Hi,

we are using exclusively remote submits, hence the AP is nt the sched but a workgroup server that is doing a remote submit.

I suspect that is why I can not use condor_tail to check my job <STDOUT> similar to what is described in the manual (?)

I thought maybe 'when_to_transfer_output' would give me an option to realize a 'live-scheme' but it does not seem to be the case.

Is there any other option than using a custom construct with condor_chirp etc ?

best
christoph

--
Christoph Beyer
DESY Hamburg
IT-Department

Notkestr. 85
Building 02b, Room 009
22607 Hamburg

phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/