Is your feature request related to a problem? Please describe.
The frontend dunegpfrontend01.fnal.gov is having a difficult problem trying to debug authentication with a remote condor_schedd.
We need to get _CONDOR_TOOL_DEBUG=D_SECURITY:2 D_FULLDEBUG set and get the debug output in the logs to figure this out. This is doubly confusing because as user "frontend" from the command line I can do condor_q against this schedd
and it works but the frontend using the python bindings can't do it.
Describe the solution you'd like
Add a configuration knob in the frontend.xml to enable debugging output if necessary.
Describe alternatives you've considered
The frontend doesn't respect the files in /etc/condor/config.d so we can't do it that way.
Info (please complete the following information):
Priority: Critical--DUNE global pool can't function until we get this in place (and then find and fix the auth error)
Stakeholders: Concerned stakeholder(s) DUNE
Components: Frontend
Additional context
The following patch works in the DE:
[root@hepcsvc03 publishers]# diff publisher.py publisher.py.1.7.4
91,96d90
< # S. Timm 10/27/22 add debugging
< htcondor.set_subsystem("TOOL")
< htcondor.param['TOOL_DEBUG'] = 'D_SECURITY:2 D_FULLDEBUG'
< htcondor.param['TOOL_LOG'] = '/tmp/tool.log'
< htcondor.enable_log()
< htcondor.enable_debug()
Those same things will have to be passed in the frontend to the routine that calls the binding but the structure of that code squire different.
Is your feature request related to a problem? Please describe. The frontend dunegpfrontend01.fnal.gov is having a difficult problem trying to debug authentication with a remote condor_schedd. We need to get _CONDOR_TOOL_DEBUG=D_SECURITY:2 D_FULLDEBUG set and get the debug output in the logs to figure this out. This is doubly confusing because as user "frontend" from the command line I can do condor_q against this schedd and it works but the frontend using the python bindings can't do it.
Describe the solution you'd like Add a configuration knob in the frontend.xml to enable debugging output if necessary.
Describe alternatives you've considered The frontend doesn't respect the files in /etc/condor/config.d so we can't do it that way.
Info (please complete the following information):
Additional context The following patch works in the DE:
[root@hepcsvc03 publishers]# diff publisher.py publisher.py.1.7.4 91,96d90 < # S. Timm 10/27/22 add debugging < htcondor.set_subsystem("TOOL") < htcondor.param['TOOL_DEBUG'] = 'D_SECURITY:2 D_FULLDEBUG' < htcondor.param['TOOL_LOG'] = '/tmp/tool.log' < htcondor.enable_log() < htcondor.enable_debug()
Those same things will have to be passed in the frontend to the routine that calls the binding but the structure of that code squire different.