Re: [HTCondor-users] debug mode - for CredMon - based on AbstractCredentialMonitor.py

[Jason Patton <jpatton@xxxxxxxxxxx>]

Ben,

Glad to hear! In case it helps for the next time you're troubleshooting, adding the -v flag to condor_config_val will helpfully point you to the config file and line that is currently responsible for a config value, for example:

[root@adfa6a7c99d0 /]# condor_config_val -v ENABLE_KERNEL_TUNING
ENABLE_KERNEL_TUNING = False
Â# at: /etc/condor/config.d/01-misc.conf, line 2
Â# raw: ENABLE_KERNEL_TUNING = False

Jason

On Tue, Mar 5, 2024 at 8:29âAM Benoit Roland <benoit.roland@xxxxxxx> wrote:

Hi Jason,

I found my mistake, sorry for the noise...

Still, your feedback was useful for me.

I forgot that I have a default config in "src/condor_credd/condor_credmon_oauth/examples/config/condor/40-mytoken-credmon.conf".

This configuration was overwritting my new one, setting the D_FULLDEBUG mode for the CredMon.

Thanks a lot again!

Cheers,
ben

On 04/03/2024 22:51, Jason Patton via HTCondor-users wrote:

Hi Ben,

By chance have you set ALL_DEBUG (condor_config_val ALL_DEBUG) to D_FULLDEBUG or similar? Since we made the change to the credmon to use the HTCondor logging functionality, the debug level for the credmon will inheritÂfrom ALL_DEBUG.

Also, did you restart or reconfig condor after making the config file change? condor_reconfig sends daemons a SIGHUP, but since the credmon hijacks SIGHUP for non-config-reloading behavior (but rather for credential refresh behavior), changes to the credmon require a restart... though the restart can be limited to the credmon, e.g. "condor_restart --daemon CREDMON_OAUTH". (Which reminds me, we should really document this caveat!)

Jason

On Mon, Mar 4, 2024 at 3:34âPM Benoit Roland <benoit.roland@xxxxxxx> wrote:

Dear all,

I complied some weeks ago with the "new" AbstractCredentialMonitor.py for my Helmholtz AAI CredMon [1].

Before that, I was using my own logger, for which I could specify different log levels (info, error, debug,...)

I used to run my credmon with the flag:
CREDMON_OAUTH_DEBUG = D_FULLDEBUG
when testing the code.

Now that I am migrating to the production environment, I removed this flag.

The information processed through "self.log.debug(...)" in [2] is nevertheless displayed in the corresponding logfile, exposing what should be limited to admins.

Is it expected, or am I doing something completely stupid?

Thanks a lot in advance for your help!

Cheers,
ben

[1] https://github.com/benoitroland/C4P-HTCondor/blob/devel_rhel8/src/condor_credd/condor_credmon_oauth/condor_credmon_mytoken
[2] https://github.com/benoitroland/C4P-HTCondor/blob/devel_rhel8/src/condor_credd/condor_credmon_oauth/credmon/CredentialMonitors/MytokenCredmon.py

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/