Were you using wallaby to configure the JobServer?

If not, you must specify JOB_SERVER_LOG in configuration yourself.

Note:
 o The condor-qmf package could lay down config that has JOB_SERVER_LOG set
 o The core probably comes from ABORT_ON_EXCEPTION, please verify

I am aware of not using wallaby. The main reason for reporting
it is the coredump. I do not think condor_job_server operates
accordingly to the problem and that it uses the right way to
say a line in config file is missing.

Yes, it is exception, GDB backtrace says:

Thread 1 (Thread 3965):
#0  0x00002b673e927265 in raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00002b673e928d10 in abort () at abort.c:88
#2  0x00000000004a2d31 in _EXCEPT_ (
    fmt=0x546513 "No '%s' parameter specified.") at except.c:89
#3  0x00000000004a4c5a in dprintf_config (subsys=0x4f27c90 "JOB_SERVER")
    at dprintf_config.c:161
#4  0x000000000049dbf5 in main (argc=1, argv=0x7fffe2a454e8)
    at daemon_core_main.cpp:1850

core is a false positive because of ABORT_ON_EXCEPTION=TRUE

The condor-qmf package should provide config that avoids this EXCEPT.

Aah, thank you for explanation. Closing as NOTABUG.

Sorry, only when you wrote about it I realized that lately
I added line "ABORT_ON_EXCEPTION=True" to the config file...

Ressurecting as this bug will serve "as an RFE for better OOTB config"
as Matt wrote.

*** Bug 616727 has been marked as a duplicate of this bug. ***

Related - https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=61

Following patch will be in a build post 7.4.4-0.17, with the next pull of the V7_4-QMF-branch

commit 490ff70cd9cb56e7f2574ca677fc2d2843d0c760
Author: Matthew Farrellee <matt@redhat>
Date:   Thu Nov 18 11:58:14 2010 -0500

    Added a JOB_SERVER_LOG default to 60condor-qmf.conf, for BZ624999

diff --git a/src/condor_examples/60condor-qmf.config b/src/condor_examples/60condor-qmf.conf
index d6303af..1351268 100644
--- a/src/condor_examples/60condor-qmf.config
+++ b/src/condor_examples/60condor-qmf.config
@@ -18,3 +18,8 @@ SCHEDD.PLUGINS = $(LIB)/plugins/MgmtScheddPlugin-plugin.so
 
 # condor_startd: advertises slots
 STARTD.PLUGINS = $(LIB)/plugins/MgmtStartdPlugin-plugin.so
+
+
+# Defaults needed for the JOB_SERVER
+JOB_SERVER_LOG = $(LOG)/JobServerLog
+

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C: No default exists for JOB_SERVER_LOG
C: The condor_job_server will exit without a configured JOB_SERVER_LOG
F: The packaged /etc/condor/config.d/60condor-qmf.config provides a default JOB_SERVER_LOG of $(LOG)/JobServerLog
R: There is no need to configure a JOB_SERVER_LOG

Verified in condor-qmf-7.4.5-0.6.el5

$ cat /etc/condor/config.d/60condor-qmf.config | grep JOB
# Defaults needed for the JOB_SERVER
JOB_SERVER_LOG = $(LOG)/JobServerLog

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1 @@
-C: No default exists for JOB_SERVER_LOG
+Previously, condor_job_server could have exited with an exception. This occurred if no JOB_SERVER_LOG value was defined. With this update, JOB_SERVER_LOG contains a default setting and there is no need to configure the parameter.-C: The condor_job_server will exit without a configured JOB_SERVER_LOG
-F: The packaged /etc/condor/config.d/60condor-qmf.config provides a default JOB_SERVER_LOG of $(LOG)/JobServerLog
-R: There is no need to configure a JOB_SERVER_LOG

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0217.html