Red Hat Bugzilla – Bug 846955
unexpected error message from condor init.d script
Last modified: 2013-03-06 13:45:03 EST
Description of problem: From time to time a condor init.d shell script prints something like this: cat: /var/run/condor/condor_master.pid: No such file or directory Probably the master.pid file is removed right after the test [ -f $1 ]; which leads to the error message. This can be easily prevented by changing line 151 in /etc/init.d/condor file from pid=`cat $1` &>/dev/null to pid=$(cat $1 2>/dev/null) Version-Release number of selected component (if applicable): condor-7.6.5-0.19 How reproducible: 30% Steps to Reproduce: 1. Restart condor continuously using init.d script 2. See error output Actual results: There's error output cat: /var/run/condor/condor_master.pid: No such file or directory Expected results: No error output will be presented when condor stops correctly Additional info:
Retested on RHEL5/6 - 32/64 with: condor-7.8.7-0.5 Relevant part of /etc/init.d/condor script: get_pid() { if [ -f $1 ]; then pid=$(cat $1 2>/dev/null) #pid=`cat $1` &>/dev/null if [ $? -ne 0 -o -z "$pid" ]; then return 2 fi echo -n $pid return 0 fi return 1 } >>> 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