Negotiator Assert Workaround

Not logged in

• Browse
• Help
• Home
• Login
• Reports
• Search
• Timeline
• Wiki

• Contents
• No-Diff
• Text

-*Do not upgrade from Condor 7.8.4 to 7.9.0.*
+*Do not upgrade from Condor 7.8.4 to 7.9.X.*
 
 Condor 7.8.4 contains a bug that causes the negotiator daemon to write malformed entries in its =Accountantnew.log=. When a 7.8 negotiator reads the =Accountantnew.log= on startup, it ignores these entries. If any jobs complete while the negotiator wasn't running, their accumulated runtime won't be charged to their owner when calculating user priorities.
 
-But in Condor 7.9.0, the negotiator is less tolerant of malformed entries in the =Accountantnew.log=. It will abort upon seeing one. The master will periodically attempt to restart the negotiator, and each time, the negotiator will abort and exit. As a result, no jobs will run in the local pool, as no matches will be made.
+But in Condor 7.9.X, the negotiator is less tolerant of malformed entries in the =Accountantnew.log=. It will abort upon seeing one. The master will periodically attempt to restart the negotiator, and each time, the negotiator will abort and exit. As a result, no jobs will run in the local pool, as no matches will be made.
 
-Condor version 7.8.5 (and future releases) will not produce these malformed entries and will remove them from the =Accountantnew.log=. Condor version 7.9.2 (and future releases) will not abort when reading malformed entries and will remove them from the =Accountantnew.log=.
+Condor version 7.8.5 (and future releases) will not produce these malformed entries and will remove them from the =Accountantnew.log=.
 
-Thus, upgrading from Condor 7.8.4 to 7.9.0 will render your pool unable to run jobs. But any other upgrade path is unaffected.
+Thus, upgrading from Condor 7.8.4 to 7.9.X will render your pool unable to run jobs. But any other upgrade path is unaffected.
 
 Condor 7.9.1 includes =accountant_log_fixer= in the libexec directory. This tool can correct the malformed entries. It should be run with a single command line argument: the path to your =Accountantnew.log=.  For example "=accountant_log_fixer Accountantnew.log=", assuming your =Accountantnew.log= is in the current working directory, and the =accountant_log_fixer= is in your path.

This work is supported by NSF under Cooperative Agreement OAC-2030508 as part of the PATh Project. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF. Site built using CVSTrac.