Shell script not running in crontab

Question

Following is my crontab entry

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
* * * * *  /FinalSync.sh $(date --date="5 days ago" +%d_%m_%Y) || echo $? >> log

Got no error in log file also

Shell Script

#! /bin/sh

source=/Source/$1
destination=/Destination
folderParam=$(basename $source)
if /usr/bin/rsync -avh -r $source $destination; then
   cp /FolderCopyStatus/Success   /Status/Success_$folderParam
else
   cp /FolderCopyStatus/Failure   /Status/Failure_$folderParam
fi

Script run perfectly when I use in command line as under

sh /FinalSync.sh  $(date --date="5 days ago" +%d_%m_%Y)

score 5 · Accepted Answer · answered Oct 17 '16 at 10:51

5

cron converts % to newline for any crontab entry. You need to escape the %s with \:

* * * * *  /FinalSync.sh "$(date --date="5 days ago" +\%d_\%m_\%Y)"

answered Oct 17 '16 at 10:51

heemayl

56,300

changed but didn't work.. – HDev007 Oct 17 '16 at 10:56
I wonder what's the history of using the percent sign for that... – ilkkachu Oct 17 '16 at 10:56
Got 126 error code in log file – HDev007 Oct 17 '16 at 10:59
@ilkkachu probably just carried over from printf and similar functions. – terdon Oct 17 '16 at 11:00
@HadoopDev007 then that's a different issue. Please edit your question and update it with the current situation. – terdon Oct 17 '16 at 11:01
Return code 126 seems to imply a permission problem. Maybe you have exclusive execution rights on the script. Try chmod +x FinalSyn.sh. – Valentin B. Oct 17 '16 at 11:04
@terdon after escaping I started to get error 126 which means (command not executable)..my cronjob still didnot run – HDev007 Oct 17 '16 at 11:05
1

@HadoopDev007 yes, I understand that but that is a different problem. So, ideally, accept this answer which solved your original issue and then ask a new question about the 126 error. – terdon Oct 17 '16 at 11:17

Shell script not running in crontab

1 Answers1

Linked

Related