Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a way to enable high condor debugging on the Frontend #297

Open
StevenCTimm opened this issue May 23, 2023 · 2 comments
Open

Need a way to enable high condor debugging on the Frontend #297

StevenCTimm opened this issue May 23, 2023 · 2 comments
Labels
BUG For BUGS Critical **Needs urgent/immediate addressing** FEATURE For FEATURES frontend for affected component other-sh

Comments

@StevenCTimm
Copy link

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.

@github-actions github-actions bot added BUG For BUGS Critical **Needs urgent/immediate addressing** FEATURE For FEATURES frontend for affected component other-sh labels May 23, 2023
@mambelli
Copy link
Contributor

@StevenCTimm There are a couple of commands in the aliases defined in the dev-tools that run condor_q and condor_advertise using the configuration used by the Frontend and do that with debug flags enabled (feccq, fecca)

alias feccq='su -c "CONDOR_CONFIG=/var/lib/gwms-frontend/vofrontend/frontend.condor_config _CONDOR_TOOL_DEBUG=D_FULLDEBUG,D_SECURITY condor_q -debug -global -allusers" -s /bin/bash - frontend'
alias fecca='su -c "CONDOR_CONFIG=/var/lib/gwms-frontend/vofrontend/frontend.condor_config _CONDOR_TOOL_DEBUG=D_FULLDEBUG,D_SECURITY condor_advertise -debug" -s /bin/bash - frontend'

Did you try using these? Would they do what you need?

@StevenCTimm
Copy link
Author

StevenCTimm commented Oct 14, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG For BUGS Critical **Needs urgent/immediate addressing** FEATURE For FEATURES frontend for affected component other-sh
Projects
None yet
Development

No branches or pull requests

2 participants