[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Start HTCondor service under valgrind.
- Date: Wed, 02 Feb 2022 18:12:29 +0300 (MSK)
- From: "Sergey A. Komissarov" <sergey.komissarov@xxxxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Start HTCondor service under valgrind.
Thank you for this information. I added variable to the config and excluded procd_pipe and condor_shadow from traced children. Everything seems fine after this.
Senior Software Developer
This message may contain confidential information
constituting a trade secret of DATADVANCE. Any distribution,
use or copying of the information contained in this
message is ineligible except under the internal
regulations of DATADVANCE and may entail liability in
accordance with the current legislation of the Russian
Federation. If you have received this message by mistake
please immediately inform me of it. Thank you!
----- Original Message -----
From: "Greg Thain" <gthain@xxxxxxxxxxx>
To: "htcondor-users" <htcondor-users@xxxxxxxxxxx>
Sent: Tuesday, February 1, 2022 11:09:05 PM
Subject: Re: [HTCondor-users] Start HTCondor service under valgrind.
On 2/1/22 12:00, Sergey A. Komissarov via HTCondor-users wrote:
> I'm trying to envistigate why condor_schedd crashed with valgrind but HTCondor daemon just refuses to start. Does it need some options to work correctly under valgrind?
> HTCondor 9.0.9 is started inside Ubuntu docker container. When I replaced usual start command (/usr/sbin/condor_master) with valgrind HTCondor process just dies after 1.5 minutes.
> Condor start command: valgrind --tool=memcheck --verbose --trace-children=yes --child-silent-after-fork=yes --trace-children-skip=/usr/bin/*,/bin/* --time-stamp=yes /usr/sbin/condor_master
> Valgrind complete log:
We run condor under valgrind routinely, but usually not in a container,
on raw hardware.Â There is a known problem with running condor under
valgrind, which condor tries to work around.Â For the schedd to start a
shadow when running under valgrind, the config knob
USE_CLONE_TO_CREATE_PROCESSES must be set to false.Â Condor itself tries
to check that it is under valgrind, and if it detects this,
automatically sets the knob to false, and logs something like this to
Looks like we are under valgrind, forcing USE_CLONE_TO_CREATE_PROCESSES
Otherwise, is there anything interesting in the SchedLog when it exits?
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: