[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 16:54:52 +0000
- From: Eric Abel <Eric.Abel@xxxxxxxxxx>
- Subject: Re: [Condor-users] not seeing Windows 7 CPUs
As mentioned in a previous post, I have a similar problem, perhaps with different symptoms? I haven't been able to reproduce Brad's observations. I would like to preface my question with the fact that I have a number of windows 7 machines and half of them work without any problems. The other half have always had intermittent functionality, but now seem to be "broken" altogether. Condor is running, but no slots show up in "condor_status". If I try a "condor_status -direct bad.hostname" I get an error indicating no startd was found. Now, if I log onto "bad.hostname", and do the same command as above "condor_status -direct bad.hostname", I can see all of the slots for this machine and their status. So, some how, startd is running, but the condor host doesn't know it. I can ping the condor host from "bad.hostname", and the reverse ping works as well, so the machines see eachother. I don't see anything abnormal in any of "bad.hostnames" logs, and I cannot find the ip address for "bad.hostname" in any of the condor host logs. What's truly troubling, is that the condor, network, AV/Firewall, and OS settings are nominally identical between "good.hostname" and "bad.hostname". I'm not really sure what else I can troubleshoot here. Any ideas?
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of brad.32@xxxxxxxxxxx
Sent: Monday, October 22, 2012 10:41 AM
Subject: Re: [Condor-users] not seeing Windows 7 CPUs
Quoting "Wilding, Kevan A" <kwilding@xxxxxxxxxxx>:
> We run a number of Windows 7 clients without any problem. The only
> thing which caused problems in the first place was the condor service
> starting before the firewall. There is a delayed start up for Condor
> which fixes this problem. There is also a programmatical way to do
> this, but in the first instance you can do this manually on one
> machine to check this.
> Another test would be to stop and start the condor service after the
> machine has rebooted, i.e. net stop condor, and net start condor. We
> used to have a script to do this on a bunch of XP machines to get
> around this problem, but the delayed start for Condor on Win7 should
> do the trick.
Restarting the service fixed the problem of the Windows 7 computer's CPUs not being recognized or used, ONCE. The CPUs appeared after following your procedure, but after seeing the CPUs listed and attempting to use them, I then restarted the master and repeated the stop and restart process and haven't been able to repeat the first
However, the attempt to use the Win7 CPUs while they were recognized in the pool was not successful. While I saw the execute directories being generated and removed as the jobs were submitted to and supposedly run on the computer, the results files were not sent back to the master and my monitoring program waited "forever" for them to complete, but the directories were long since removed from the execute directory.
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of
> Sent: 22 October 2012 14:59
> To: condor-users@xxxxxxxxxxx
> Subject: Re: [Condor-users] not seeing Windows 7 CPUs
> In the pool I have been asking about, the condor_cred mechanism is not
> currently enabled, which is apparently okay with Windows XP clients.
> The master runs Windows 7, but the Condor-working clients are Windows
> XP. The only computer that doesn't work with this Condor pool is
> running Windows 7.
> All the other potentially available machines are also Windows 7. If
> I'm to add any other machines to this Condor pool, I need to learn /
> figure out how to get Windows 7 computers to work within the Condor
> As I have mentioned before, when I run condor_status from the master,
> any of the XP, or the one Win7 computers that are supposedly in the
> pool, they all see the same information. The Win7 computer's CPU slots
> don't show up in any of the listings, so they are not used to run jobs
> If any Windows 7 machines are clients in a Condor pool, does the
> condor_cred mechanism have to be used due to, e.g., problems with the
> low-privilege account normally used?
> Are there any other log files or information I need to post to help
> all of you so we can understand why this Win7 computer is not working
> with Condor?
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: