Cron Errors

One of our user accounts has a cron job setup to run every 15 minutes. However, on completion of the cron job they are getting emailed the following:


produced the following output:

/opt/bin/[31]: cut:  not found
/opt/bin/[37]: sleep:  not found
/opt/bin/[40]: grep:  not found
/opt/bin/[40]: cat:  not found
/opt/bin/[40]: wc:  not found
/opt/bin/[41]: expr:  not found
/opt/bin/[42]: test: argument expected
/opt/bin/[26]: cut:  not found
/opt/bin/[27]: cut:  not found
/opt/bin/[29]: test: argument expected
/opt/bin/[26]: cut:  not found
/opt/bin/[27]: cut:  not found
/opt/bin/[29]: test: argument expected
/opt/bin/[26]: cut:  not found
/opt/bin/[27]: cut:  not found
/opt/bin/[29]: test: argument expected

The user's crontab is as follows:

# Check Databases and Listener are running
00,15,30,45 08-18 * * 1-5 /opt/bin/
00,15,30,45 08-18 * * 1-5 /opt/bin/

When they run the script manually it works fine with no errors - it's only returning this when run from the cron.

Who is Participating?
tfewsterConnect With a Mentor Commented:
You can insert "set -x" in the script to trace what it is doing at each stage; However, the errors start at line 31 and then loop:

26:  DB=`echo ${LNE} | cut -f1 -d:`
27:  AUTO_START=`echo ${LNE} | cut -f3 -d:`
29:  if test $AUTO_START = "Y"
30:  then
31:    . /opt/bin/ora_${DB}.env

I suspect that the first ora_${DB}.env call is overwriting the default PATH so the path to sleep, cut, grep etc. is lost
To help answer this there are two more pieces of information for starters.

(i) The text in the shell script needs to be shown to us so please append this to the question


(ii) The result of echo $PATH


Grass-hopperAuthor Commented:
Body of Script:

# ***************************************************************************
# * File    @(#):                                    *
# * Date        : 06-MAY-2004                                               *
# * Version     :                                                   *
# * Author      : PSG                                                       *
# * Purpose @(#): UNIX Environment administration for Oracle.               *
# *                                                                         *
# *               This script checks connections to databases. Send email   *
# *               alert if connections not being accepted.                  *
# *                                                                         *
# * Parameters  :                                                           *
# ***************************************************************************
# * Change History                                                          *
# *                                                                         *
# *    Date     Done By           Vers  Description                         *
# * ---------   ----------------  ----  ------------------------------------*
# ***************************************************************************

cd /opt/bin

for LNE in `cat /var/opt/oracle/oratab | grep -v '^#' | grep -v '*' | grep -v 'i
ds' `
  DB=`echo ${LNE} | cut -f1 -d:`
  AUTO_START=`echo ${LNE} | cut -f3 -d:`

  if test $AUTO_START = "Y"
    . /opt/bin/ora_${DB}.env

    # Submit the Oracle task in the background
    nohup /opt/bin/ > /tmp/check_$ORACLE_SID.ora 2>&1 &

    # Wait for 30 seconds
    sleep 30

    # Check for ORA- errors
    check_stat=`cat /tmp/check_$ORACLE_SID.ora | grep -i ORA- | wc -l`
    oracle_num=`expr $check_stat`
    if [ $oracle_num -gt 0 ]
      cnt=`cat /tmp/check_$ORACLE_SID.ora | wc -l`

      cp -p /tmp/check_$ORACLE_SID.ora /tmp/check_$ORACLE_SID.ora.wrk


      while [ $lne -le $cnt ]
        head -1 /tmp/check_$ORACLE_SID.ora.wrk > /tmp/line
        err_chk=`cat /tmp/line | grep -i ORA- | wc -l`
        if [ $err_chk -gt 0 ]
          ora_err=`cat /tmp/line | grep -i ORA- | cut -c5-9`
          oerr ORA $ora_err >> /tmp/connect.err
          echo "" >> /tmp/connect.err
          echo "Log in as Oracle and run the Oracle Administration menu by typin
g at the command prompt." >> /tmp/connect.err
          echo "" >> /tmp/connect.err
          echo "Select the $ORACLE_SID    Database Administration Menu and selec
t Start $ORACLE_SID Database NORMAL option" >> /tmp/connect.err
        sed '1d' /tmp/check_$ORACLE_SID.ora.wrk > /tmp/check_$ORACLE_SID.ora.tmp
        mv /tmp/check_$ORACLE_SID.ora.tmp /tmp/check_$ORACLE_SID.ora.wrk
        lne=`expr $lne + 1`
      rm /tmp/check_$ORACLE_SID.ora 2>/dev/null

    if [ -f /tmp/connect.err ]
      #mailx -s "HIDDEN"< /tmp/connect.err
      mailx -s "SERVER: WARNING - $ORACLE_SID not accepting connections" HIDDEN
 < /tmp/connect.err
      rm /tmp/connect.err 2>/dev/null
      #rm /tmp/check_$ORACLE_SID.ora 2>/dev/null
      #rm /tmp/line 2>/dev/null
      #rm /tmp/check_$ORACLE_SID.ora.wrk 2>/dev/null

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

I would suggest you try this

crontab -l > /tmp/cron
crontab -l > /tmp/cron_b                                                               (N.B Just as a backup of the original)
vi /tmp/cron

Edit the file so that it looks like this:

00,15,30,45 08-18 * * 1-5 /bin/sh -c '/opt/bin/'
00,15,30,45 08-18 * * 1-5 /bin/sh -c '/opt/bin/'

save the file {ESC}:wq!

crontab < /tmp/cron

This should give the cron the same environment as running it from a prompt.

It is the ENV seting, the PATH setting for cron is in the /etc/default/cron

man cron
man crontab
to learn more details.

You can modify the script to FULL path for commands, eg:
use "/usr/bin/cut" instead of "cut", OR defind PATH etc in the sctipt before
all the command. OR, "source" a ENV setting file (eg a login script):

. /path-to/.profile        # a Dot SPACE then /path-to/.profile
# following by the script body
#End of script.

If you are 100% sure that the script works in the user (eg fred's) login
ENV, you can also use root's crontab to run the script as user fred, see
the example in:

Grass-hopperAuthor Commented:
Cheers guys - I'll give your suggestions a try and get back to you to how it goes.
Grass-hopperAuthor Commented:
Cheers for all your replies guys - its appreciated.

It turns out it was exactly what tfewster said about the ora_${DB}.env call overwriting the default PATH. When we traced it to the related script - thats exactly what it was doing and we were able to sort it.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.