[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] not seeing Windows 7 CPUs
- Date: Wed, 24 Oct 2012 21:59:13 +0000
- From: Eric Abel <Eric.Abel@xxxxxxxxxx>
- Subject: Re: [Condor-users] not seeing Windows 7 CPUs
Thanks for the tips.
I ran the condor_advertise command below, and it just hung with the following output:
'10/24/12 14:54:47 Locale: English_United States.1252'
My Collector_Debug is set to D_ALL, and I see no Collector.log entries from bad.hostname, either by name or IP address.
Machines are all on the same domain, and my allow write includes *.my.domain.com, and the allow_read was set to * . I've tried explicitly adding *.my.domain.com to allow_read, but it made no difference.
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ziliang Guo
Sent: Wednesday, October 24, 2012 11:16 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] not seeing Windows 7 CPUs
In your case, I want to say that your machine is for some reason unable to talk to the central manager, hence why they are currently not visible and why running condor_status returns nothing on those machines. We can try running the following on the bad.hostname machine.
condor_advertise -debug UPDATE_STARTD_AD
and see what that says. This will tell your machine to advertise its startd to the central manager. Also, on the central manager, I'd look at the collector log to see what it says. You might want to jack up the debug level considerably to catch more output.
I know I've mentioned this before, but we want to make sure that domain wise, if you lookup the hostname/domain using the IP address of one of the bad machines on the central manager, we want to make sure that domain is actually in the ALLOW_READ/WRITE lists in the central manager's config file.
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: