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

Re: [Condor-users] condor_status



Its is usually only temporary.

It might indicate whose time is slightly out with respect to the others, maybe worth checking.

JK

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx on behalf of Dimitri Maziuk
Sent: Mon 17/09/2007 21:59
To: Condor-Users Mail List
Subject: [Condor-users] condor_status
 

Anyone seen this:

vm1@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991  0+01:02:26
vm2@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991  0+01:02:31
vm3@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.020  1991  0+00:00:03
vm4@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991  0+01:02:32
vm1@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991[?????]
vm2@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991[?????]
vm3@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991[?????]
vm4@xxxxxxxxx LINUX       X86_64 Unclaimed  Idle       0.000  1991[?????]

lark and sparow are identical 2x2 AMD, FC6 linux machines. Condor is v 6.8.3, 
both machines are getting it from NFS-mounted /opt/condor, configs are 
identical. 

Activity time works on one and comes up as [?????] on the other.

An ideas?

Dimitri
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

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