condor-7.2.2-0.1.el5 and related to BZ486462 From /var/log/condor/MasterLog: 2/19 11:00:08 Sending obituary for "/usr/sbin/condor_schedd" 2/19 11:00:08 Forking Mailer process... 2/19 11:00:08 Failed to email /var/log/condor/SchedLog: cannot open file The Schedd failed in the middle of a log rotation. The Master was not able to email an obituary because the new SchedLog had not been created. In such a case the Master should attempt to mail part of the SchedLog.old instead.
Is there an easy repro condition?
I would expect setting MAX_SCHEDD_LOG to a small number then sending SIGKILL to the condor_schedd would assist in reproducing.
(In reply to comment #2) > I would expect setting MAX_SCHEDD_LOG to a small number then sending SIGKILL to > the condor_schedd would assist in reproducing. Is this still the suggested way to reproduce it?
------------------------------------------------------- To repro: 1.) Navigate to your LOG locations && `rm -f SchedLog*` 2.) set SCHEDD = /some/path/to/a/script/like/the/old/below in your config 3.) drop a script which ~= the one below #!/bin/sh echo "MASSIVE FAIL OBIT TEST" >> /your/LOG/loc/SchedLog.old exit 1 4.) Start condor. before fix you'll see a fail to open like in comment #1 after fix you'll see it fork the daemon and email. ------------------------------------------------------- Tracking changes upstream.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: When the condor master daemon sends an obituary during a log rollover event of the failed daemon. C: The obituary will not be sent. F: Update logic to check for rollover log, and send. R: The master should send an obituary email when a daemon fails during a log rollover.
Tested on RHEL 5.9/6.4 x i386/x86_64 with condor-7.8.8-0.4.1 and it works. -->VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0564.html