[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Condor is still writing temp data to /var/opt/condor



-af is short for -autoformat, and it's definitely a valid option for condor_status.  the problem is probably that complext regexps() expression.  try just using

condor_status -master -af Name MyAddress


-tj

-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Mobley, Nate (Millennium)
Sent: Tuesday, January 9, 2018 3:51 PM
To: Todd Tannenbaum <tannenba@xxxxxxxxxxx>; HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Condor is still writing temp data to /var/opt/condor

Thanks, not a problem getting my node names to display. However, when I try to connect via SSH with Putty, it tells me "Unable to open connection to "hostname.local" Host not found."

When I ran "condor_status -master -af Name 'regexps("<([^:]*)",MyAddress,"\1")'" I received the error "Unknown option -af" and when I eliminated the "-af," the command ran but didn't return anything...

I appreciate your time! 

Nate Mobley
Millennium Engineering & Integration Company
ISSO/Systems Administrator
Desk: 256-489-7847
Cell (Voice Only): 256-655-5570
MEI Help Desk:Â 703-413-7771 
nmobley@xxxxxxxxxxxxxx
www.meicompany.com


-----Original Message-----
From: Todd Tannenbaum [mailto:tannenba@xxxxxxxxxxx] 
Sent: Tuesday, January 09, 2018 2:02 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>; Mobley, Nate (Millennium) <nmobley@xxxxxxxxxxxxxx>
Subject: Re: [HTCondor-users] Condor is still writing temp data to /var/opt/condor

On 1/9/2018 12:36 PM, Mobley, Nate (Millennium) wrote:
> This is great news, now I think I know exactly what's causing the data to still go to "/var/opt/condor". My challenge now is how to change the config file on each compute node...I've never logged into them before. I'm having trouble determining what their IP addresses are, or else I think I could SSH into them with putty and modify the config files. I assume the " condor_config_val -v -startd -name compute-0-0.local EXECUTE" will show me the IP addresses, so I'll start there. Thank you all for your time.
> 

Run "condor_status -master" to see all the hosts (nodes) in your pool.   Note this will display hostnames, like:

   Name                 Version        Cpus   Memory      Uptime    

   node1.wisc.edu       8.6.9.427508      8    15.5 GB   20+02:31:06
   node2.wisc.edu       8.6.9.427508      8     7.7 GB   20+02:31:41
   node3.wisc.edu       8.6.9.427508      8    15.5 GB   20+02:31:58


If you really need IP addresses instead of hostnames, you could do something like:

   condor_status -master -af Name 'regexps("<([^:]*)",MyAddress,"\1")'

which will give output like:

   node1.wisc.edu 10.0.5.22
   node2.wisc.edu 10.0.5.23
   node3.wisc.edu 10.0.5.24
   ..


regards
Todd




> Nate Mobley
> Millennium Engineering & Integration Company ISSO/Systems 
> Administrator
> Desk: 256-489-7847
> Cell (Voice Only): 256-655-5570
> MEI Help Desk:Â 703-413-7771
> nmobley@xxxxxxxxxxxxxx
> www.meicompany.com
> 
> 
> -----Original Message-----
> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On 
> Behalf Of htcondor-users-request@xxxxxxxxxxx
> Sent: Tuesday, January 09, 2018 12:00 PM
> To: htcondor-users@xxxxxxxxxxx
> Subject: HTCondor-users Digest, Vol 50, Issue 24
> 
> Send HTCondor-users mailing list submissions to
> 	htcondor-users@xxxxxxxxxxx
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> or, via email, send a message with subject or body 'help' to
> 	htcondor-users-request@xxxxxxxxxxx
> 
> You can reach the person managing the list at
> 	htcondor-users-owner@xxxxxxxxxxx
> 
> When replying, please edit your Subject line so it is more specific than "Re: Contents of HTCondor-users digest..."
> 
> 
> Today's Topics:
> 
>     1. Re: Condor is still writing temp data to /var/opt/condor even
>        though I specified otherwise (John M Knoeller)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 9 Jan 2018 17:05:28 +0000
> From: John M Knoeller <johnkn@xxxxxxxxxxx>
> To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>,	Todd
> 	Tannenbaum	<tannenba@xxxxxxxxxxx>
> Subject: Re: [HTCondor-users] Condor is still writing temp data to
> 	/var/opt/condor even though I specified otherwise
> Message-ID:
> 	
> <CY1PR0601MB2021D37279EF641838EAB62A96100@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> d.outlook.com>
> 	
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Yes, there is a separate config for each node.  Also, daemons will only see changes to the config when you condor_reconfig (or restart) them.
> 
> The - before the name of your compute node is messing things up. you want this command.
> 
> condor_config_val -v -startd -name compute-0-0.local EXECUTE
> 
> not this
> 
> condor_config_val -v -startd -compute-0-0.local EXECUTE
> 
> The -startd and -name <name> arguments tell condor_config_val to ask the condor_startd daemon what its current config is.   This will be what the config files on that node contained at the time the condor_startd was last started or reconfiged - which might be older than what the config files say now.
> 
> -tj
> 
> -----Original Message-----
> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On 
> Behalf Of Mobley, Nate (Millennium)
> Sent: Tuesday, January 9, 2018 10:20 AM
> To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>; Todd 
> Tannenbaum <tannenba@xxxxxxxxxxx>
> Subject: Re: [HTCondor-users] Condor is still writing temp data to 
> /var/opt/condor even though I specified otherwise
> 
> Thanks again Todd. So when I ran " condor_config_val -v execute" it did show me the file I was expecting. But I got to thinking after that, is there a separate config file for each node?
> 
> I'm unfamiliar with what the config knob is, could you explain that a 
> little more? I did run " condor_config_val -v -startd 
> -compute-0-0.local" (where compute-0-0.local is the name of one of my 
> compute nodes) and the error I received was "Can't connect to startd 
> on head1.domainname.com <192.***.***.*: *****>" (domainname instead of 
> my actual domain name)
> 
> 
> Nate Mobley
> Millennium Engineering & Integration Company ISSO/Systems 
> Administrator
> Desk: (256) 489-7847
> Cell (Voice Only): (256) 655-5570
> MEI Help Desk:? (703) 413-7771
> nmobley@xxxxxxxxxxxxxx
> www.meicompany.com
> 
> 
> -----Original Message-----
> From: Todd Tannenbaum [mailto:tannenba@xxxxxxxxxxx]
> Sent: Monday, January 08, 2018 4:57 PM
> To: Mobley, Nate (Millennium) <nmobley@xxxxxxxxxxxxxx>
> Cc: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
> Subject: Re: [HTCondor-users] Condor is still writing temp data to 
> Condor is still writing temp data to /var/opt/condor even though I 
> specified otherwise
> 
> On 1/8/2018 4:55 PM, Todd Tannenbaum wrote:
>> On 1/8/2018 4:25 PM, Mobley, Nate (Millennium) wrote:
>>> Thanks. They were not overwritten, Ive already triple checked that.
>>> Can I run "condor_config_val -v execute" from my head node? That is 
>>> the only one I am able to log into (I don't know the IP addresses of 
>>> the compute nodes).
>>>
>>
>> If by "head node" you mean the HTCondor Central Manager, then yes, you can use condor_config_val to view configuration settings for any node in your compute pool (unless your installation changed the default authorization rules).
>>
>> You will want to use
>>     condor_config_val -v -startd -name <name_of_execute_node> 
>> <name_of_config knob>
>>
>> So to see your execute nodes, enter "condor_status", and then use a name you see there with condor_config_val.
>>
>> So for example, the sample session below tells me my execute nodes 
>> apparently have EXECUTE undefined, which means they will use the 
>> default value of $(LOCAL_DIR)/execute, and LOCAL_DIR is set to /var in condor_config.global on line 26.
>>
>>
>>     $ condor_status -wide | head
>>     Name                               OpSys      Arch   State     Activity     LoadAv Mem      ActvtyTime
>>
>>     slot1@xxxxxxxxxxxxxxx              LINUX      X86_64 Unclaimed Idle          0.000   43883  0+05:13:41
>>     slot1@xxxxxxxxxxxxxxx              LINUX      X86_64 Unclaimed Idle          0.000   43883  0+05:13:41
>>     slot1@xxxxxxxxxxxxxxx              LINUX      X86_64 Unclaimed Idle          0.000   43883  0+05:13:41
>>     ...
>>
>>     $ condor_config_val -v -startd -name slot1@xxxxxxxxxxxxxxx EXECUTE
>>     EXECUTE =
>>      # at: /etc/condor/condor_config.global, line 44
>>      # raw: EXECUTE =
>>      # default: $(LOCAL_DIR)/execute
>>
>>     $ condor_config_val -v -startd -name slot1@xxxxxxxxxxxxxxx 
>> EXECUTE
> 
> Meant this line to be
> 
> condor_config_val -v -startd -name slot1@xxxxxxxxxxxxxxx LOCAL_DIR
> 
> regards,
> Todd
> 
> 
> 
>>     LOCAL_DIR = /var
>>      # at: /etc/condor/condor_config.global, line 26
>>      # raw: LOCAL_DIR = /var
>>
>>
>> Hope the above helps
>> Todd
>>
>>
>> _______________________________________________
>> 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/
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> HTCondor-users mailing list
> HTCondor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> ------------------------------
> 
> End of HTCondor-users Digest, Vol 50, Issue 24
> **********************************************
> 
> _______________________________________________
> 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/