[HTCondor-users] Segmentation fault running condor_history

[Angel de Vicente <angel.vicente.garrido@xxxxxxxxx>]

Hello,

in our HTCondor Pool (Ubuntu 20.04, CondorVersion: 10.0.1 + Ubuntu
18.04, CondorVersion: 9.12.0) I've found that using the condor_history
command to query a remote scheduler for a particular job gives me
segmentation fault.

To be clear, both these commands run without problems:

+ condor_history  (from machine cruise)
+ condor_history -name cruise (from another machine)

But if I want the details of a given job, running from another machine
gives me segmentation fault, i.e.:

+ condor_history 61.4540 (from machine cruise: OK)
+ condor_history -name 61.4540 (from another machine: it returns the
details of the job apparently OK, but then it ends with "Segmentation
fault (core dumped)")


I'm not sure if this is related to the following, but I also found that
condor_history from the remote machine seems to have a limit of 10000
jobs:

+ condor_history | wc -l (from machine cruise: 11013 jobs)
+ condor_history -name cruise | wc -l (from another machine: 10000 jobs)

By the way, I try the option -scanlimit, but it seems to only work when
running condor_history in the local machine. When querying a remote
scheduler, it didn't have any impact (-scanlimit 500 or -scanlimit 11000
always returned 10000 jobs history).

[By the way, https://github.com/htcondor/htcondor doesn't accept issues,
so is the mailing list the best place nowadays to report issues like
these, or is there some other preferred channel?]

Cheers,
-- 
Ãngel de Vicente                 -- (GPG: 0x64D9FDAE7CD5E939)
 Research Software Engineer (Supercomputing and BigData)
 Instituto de AstrofÃsica de Canarias (https://www.iac.es/en)