[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] a segfault at the very onset

On 23/05/17 14:30, Greg Thain wrote:
On 05/23/2017 03:18 AM, lejeczek wrote:
hi there

normally segfault means a buggy code/compiler stack, right?
But I'm hoping I'm doing something wrong, though I follow "quickstart".
I do:
$ condor_submit ./sleep.sub
and I get:
condor_submit[624588]: segfault at 0 ip (null) sp 00007ffc38b5df78 error 14 in condor_submit[400000+34000]

If condor_submit with no arguments also segfaults, it is probably an installation problem. condor_submit with no arguments should just hang, waiting for input on stdin.

Can you run ldd condor_submit, and send us that output?

HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

yep, for those of us who just try to kickstart it, but maybe for everybody - selinux selinux pray to your selinux and listen what it says.
selinux kicks condor so hard that it segfaults.
On centos7 though there is a module in default policy, 'dontaudit' reveals more denials, and a quick fix is to "permissive condor_schedd_t"