Re: [HTCondor-users] SECMAN:2011 Error with condor_status on Windows (condor v24.9.0)

[John M Knoeller <johnkn@xxxxxxxxxxx>]

It is normal for condor_config.local to be empty after installation,  the installer will put the configuration settings into c:\condor\condor_config  which condor_config.local can override.

Are you running condor_status on the same machine and as the same user that ran the installer?  The issue may be authentication rather than authorization. 

If condor_status is failing,  you can look in c:\condor\log\CollectorLog to see why it is refusing,  The server side of the condor_status query will have more information. 

To make sure we see the right messages, we need to run condor_status in a way that prints a timestamp for the commands.   so run this

   condor_status -debug:D_SECURITY

This will print the client side of the command, which might be interesting, but mostly we are looking for the timestamp on the command.

Then look in C:\condor\log\CollectorLog  for that timestamp range,  there should be messages in the collector log that indicate why it is refusing the condor_status query. 

The most likely reason is that condor_status cannot authenticate and therefore refuses to accept the command regardless of what ALLOW_READ is set to. 

It might also help if you run

   condor_config_val -summary 

and send us the output,  that will tell us what your effective security configuration is. 

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of aravind.saligram@xxxxxx <aravind.saligram@xxxxxx>
Sent: Monday, May 19, 2025 1:26 AM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] SECMAN:2011 Error with condor_status on Windows (condor v24.9.0)

 

Hello to all experienced HT Condor users,

 

I am experiencing a persistent issue after installing HTCondor on Windows using the instructions from your official documentation (Install Windows as Administrator). I am using the 24.9.0 snapshot version from the repository.

After installation, when I run condor_status, I receive the following error:

Error: communication error

SECMAN:2011:Connection closed during command authorization. Probably due to an unknown command

 

My local config file was initially empty; after searching through the internet, I found this to be the ideal config, but it does not seem to work:

ALLOW_WRITE = *

ALLOW_READ = *

ALLOW_NEGOTIATOR = *

 

I have followed all the steps in the official guide, including accepting the default access permission settings during installation. Despite this, the error persists, and I am unable to get status information from the pool.

Could you please advise on how to resolve this issue? If you need any additional logs or configuration details, I am happy to provide them.

 

I initially plan to test condor on my laptop and then try extending on my local cluster of standalone windows CPU’s. But somehow, I am stuck at the very basic step.

 

Thank you for your assistance.