Re: [HTCondor-users] Sudden death of a Rooster

[Tim Theisen <tim@xxxxxxxxxxx>]

My apologies. I did not realize that the links to github pull requests 
(and commits) are not in the public view of Jira tickets. I'll ask if 
that can be changed.

...Tim

On 12/9/25 02:53, Steffen Grunewald wrote:
> Good morning Tim,
>
> On Mon, 2025-12-08 at 09:46:04 -0600, Tim Theisen wrote:
> > Hello Steffen,
> >
> > You can create a patch directly from the github pull request:
> >
> > https://urldefense.com/v3/__https://patch-diff.githubusercontent.com/raw/htcondor/htcondor/pull/3882.patch__;!!Mak6IKo!PUspZHOHkVbF_Eu7Krw8hdq4Gvv9kEhkPDNQ8zLR0EGn9kXI7K9ah15pjmMo1V0m9MhL8oPiDcZqHwC6e0EDGmqc2djt$
> >
> > ...Tim
> root@hypatia3:/data/amd64/buildpackages.LSC/BUILD/condor-24.6.1# patch -p1 </data/amd64/buildpackages.LSC/3882.patch  --dry-run
> checking file src/condor_power/rooster.cpp
> checking file src/condor_utils/compat_classad_util.cpp
> checking file src/condor_utils/compat_classad_util.h
> checking file src/defrag/defrag.cpp
> checking file docs/version-history/v24-version.hist
> Hunk #1 FAILED at 8.
> 1 out of 1 hunk FAILED
> checking file docs/version-history/v24-version.hist
> Hunk #1 FAILED at 8.
> 1 out of 1 hunk FAILED
> checking file docs/version-history/v24-version.hist
> Hunk #1 FAILED at 9.
> 1 out of 1 hunk FAILED
>
> I'll ignore the failed ones for now... Thanks!
>
> > P.S. You just need to add .patch to any pull request URL:
> I know... ;) I just couldn't find a link to the PR (and still can't in Jira)
>
> >  ÂÂÂÂ https://urldefense.com/v3/__https://github.com/htcondor/htcondor/pull/3882__;!!Mak6IKo!PUspZHOHkVbF_Eu7Krw8hdq4Gvv9kEhkPDNQ8zLR0EGn9kXI7K9ah15pjmMo1V0m9MhL8oPiDcZqHwC6e0EDGinVUavY$
> Trying to avoid a full restart of the master, with
> # ldd /usr/libexec/condor/condor_rooster
> 	linux-vdso.so.1 (0x00007ffe3ddf9000)
> 	libcondor_utils_24_6_1.so => /lib/libcondor_utils_24_6_1.so (0x00007f26a61f1000)
> 	libclassad.so.24.6.1 => /lib/libclassad.so.24.6.1 (0x00007f26a6130000)
>          ...
> I'll have to replace the binary with the two libraries - anything else?
> (Performing a package upgrade will likely come with an ungraceful restart
> which I'd eagerly avoid.) Defrag isn't an issue for us at the moment.
>
> Thanks, S

--
Tim Theisen (he, him, his)
Release Manager
Center for High Throughput Computing
University of Wisconsin - Madison
3695 Morgridge Hall
1205 University Ave
Madison, WI 53706