8.2 Stable Release Series 6.6

This is a stable release series of Condor. It is based on the 6.5 development series. All new features added or bugs fixed in the 6.5 series are available in the 6.6 series. The details of each version are described below.

8.2.1 Version 6.6.0

New Features:

• The condor_ dagman debugging log now reports the total number of ``Un-Ready'' Nodes (i.e. those waiting for unfinished dependencies) in its periodic summaries. In the past, the omission of this state led to confusion because the total of all reported job states didn't always match the total number of jobs in the DAG.

• Most Condor commands (condor_ on, condor_ off, condor_ restart, condor_ reconfig, condor_ vacate, condor_ checkpoint, condor_ reschedule) now support a -all command-line option to specify which daemons to act on. This is more efficient and much easier to use than previous methods for accomplishing the same effect. Using -all with condor_ off correctly leaves the existing condor_ master processes running on each host, so that a subsequent condor_ on would work. See section 3.9.1 on page  for more details on proper use of -all with condor_ off and condor_ on

Bugs Fixed:

• Fixed a bug under Solaris 8 with Update 6+, and Solaris 9 where Condor would incorrectly report the console and mouse idle times as zero.

• The standard-universe fetch_files feature was not cleaning up temporary files on the execution machine.

• In rare circumstances, a Linux kernel bug results in conflicting information about system boot time (/proc/stat and /proc/uptime). Specifically, the "btime" field in /proc/stat suddenly jumps to the present moment and then stays at that value. This was resulting in incorrect estimation of process ages, which caused Condor's estimation of CondorLoadAvg to be completely wrong. A more robust heuristic is now being used.

• A long configuration line with with continuation lines can cause the config file parser to not properly skip the leading whitespace from the continued lines. This has been corrected.

• The Grid Monitor now will automatically probe for and work with ``unknown'' batch systems.

• Fixed a bug where under certain circumstances condor_ dagman would fail to detect an unsuccessful invocation of condor_ submit, and would instead report the job as successfully submitted with job id 0.0.

• Fixed a bug which was causing problems when a periodic_remove expression for a scheduler universe job evaluates to true. Under these conditions, the schedd did not log the job terminiation to the job log. Addtionally, the schedd would exit with an error status.

• Fixed a recently-introduced condor_ dagman bug where the number of node retries (specified with the RETRY keyword) wasn't being updated after some failures; instead, the node would be allowed to retry indefinitely if it kept failing.

• Fixed a recently-introduced bug where shutting down the condor_ schedd caused condor_ dagman to remove all its jobs from the queue and write a rescue file, rather than simply exiting so that it could recover automatically upon restart.

• Changed the default ``Periodic Expression Interval'' parameter (PERIODIC_EXPR_INTERVAL) from 60 seconds to 300 seconds.

• Whenever condor_ reconfig was used to re-configure multiple daemons which included the condor_ collector for a pool, the command would start to fail after the condor_ collector was reconfigured due to problems with security sessions in Condor's strong authentication code. This situation no longer causes problems for the condor_ reconfig tool, and it can properly re-configure multiple daemons at once, even if one of them is the condor_ collector for a pool.

• Most Condor commands (condor_ on, condor_ off, condor_ restart, condor_ reconfig, condor_ vacate, condor_ checkpoint, condor_ reschedule) now check to make sure they are not sending a duplicate command if the user specifies the same target machine or daemon twice. For example:

       condor_reconfig hostname1 hostname2 hostname1
  

  will only send a single reconfig command to hostname1.

• Fixed a bug in the HPUX version of Condor which was causing the startd to occasionally abort operation. This has been in Condor since version 6.1.1.

• The Condor daemons will no longer overwhelm NIS servers when large numbers of daemons are running. Condor now caches uid and group information internally, and refreshes the cache entries on a specified interval (which defaults to 5 minutes). See section 3.3.2 on page  for more details.

Known Bugs:

• The condor_ preen program does not know about Computing on Demand (COD) claims. If there are no regular Condor jobs on a given machine, but there are COD claims, and condor_ preen is spawned, it will remove files related to the COD claims. In version 6.6.0, sites using COD are encouraged to disable condor_ preen by commenting out the PREEN setting in the config files. This bug has been fixed in Condor version 6.6.1.

• Normally, if a user's job crashes and creates a core file on a remote execution machine, the condor_ starter will automatically transfer the core file back to the submit machine. However, beginning in Condor version 6.5.2, if a vanilla, Java, or MPI universe job creates a core file, the condor_ starter will fail to transfer it back. This bug will be fixed in version 6.6.1.

• There are a few bugs related to Condor tools failing to correctly locate the condor_ negotiator daemon. These bugs usually show up if a site is using non-standard ports for the central manager daemon. However, some of the bugs show up regardless of if the negotiator is listening on the standard port or not.
  • condor_config_val -negotitator queries the condor_ collector, instead of querying the condor_ negotiator like it should.

  • Using the -pool option to condor_q -analyze will not work. The tool will fail to find and query the condor_ negotiator for user priorities which it needs to determine why jobs may not be running.

  • The Condor tools that support either the -negotiator or -collector options do not work when a user also specifies the -pool to define a remote pool to communicate with. The tools print a somewhat confusing message in this case.

  • Most Condor tools that support -pool hostname will also recogize -pool hostname:port if the remote condor_ collector is listening on a non-standard port. However, the condor_ findhost tool does not work if given a -pool option that includes a port.

Table 8.1: Condor version 6.6.0 supported platforms

Architecture	Operating System
Hewlett Packard PA-RISC (both PA7000 and PA8000 series)	HPUX 10.20
Sun SPARC Sun4m,Sun4c, Sun UltraSPARC	Solaris 2.6, 2.7, 8, 9
Silicon Graphics MIPS (R5000, R8000, R10000)	IRIX 6.5
Intel x86	Red Hat Linux 7.1, 7.2, 7.3
	Red Hat Linux 8 (clipped)
	Red Hat Linux 9 (clipped)
	Windows NT 4.0 Workstation and Server (clipped)
	Windows 2000 Professional and Server, 2003 Server (clipped)
	Windows XP Professional (clipped)
ALPHA	Digital Unix 4.0
	Red Hat Linux 7.1, 7.2, 7.3 (clipped)
	Tru64 5.1 (clipped)
PowerPC	Macintosh OS X (clipped)
Itanium	Red Hat Linux 7.1, 7.2, 7.3 (clipped)