Why is cron not running my sh script?

November 13, 2015 3k views
Configuration Management

Hi Digital Ocean forum!

I have a script running every minute with crontab. The script looks like this:


UP=$(pgrep node | wc -l);

dt=`date '+%d/%m/%Y_%H:%M:%S'`;

if [ "$UP" -lt 1 ];


        pushserver -c /var/www/config.json

        echo"$dt Node is down.";


        echo "$dt Node is all good.";


So I'm checking if node is running, if it is, it's all good, if not it starts it. It works when I fire the script by running sh scriptname.sh

So, i've put this into my crontab:

* * * * * sh /home/pushCheck.sh& >> /home/pushCheck.log
* * * * * echo ‘Run this command every minute’ >> /home/crontab.log
* * * * * cd /home/ && sh pushCheck.sh>>pushCheck.log

It's not really working, but the echo to the logfile, is being logged. So crontab should be up and running.
I've tried the * * * * * sh pushCheck.sh too, but it doesn't seem to work and I'm out of ideas.

Hope someone can help me out here :-)

  • Kasper
  • I've got a couple questions about your configuration:

    1.) Is pushCheck.sh marked as executable? chmod +x pushCheck.sh

    2.) is /home/pushCheck.sh the correct directory? Normally the only thing that should be in /home is the individual user's home directories.

  • I've marked it executable chmod +x, but i'm sure it was like that before. I've also removed the file one level up to the root, but it's still not working unfortunately. Also thank you very much for the quick response :)

  • Could it possibly be that the environment path is wrong?

  • I just want to say I got it fixed. The solution was to add the following in my script:


    Thanks for your help ryanpq, that was much appreciated :-)

1 Answer


Just for future reference, it's often better to use

#!/usr/bin/env bash



This is for portability since paths often vary from one OS to another depending on how the package maintainer has it setup at installation. Debian & Ubuntu will likely always use the same paths, much like how CentOS and Fedora most likely will, though when you bounce from one OS to an entirely different one, that's when the differences make a difference :-).

IIRC, you should be able to use it in a cronjob script as well.

Have another answer? Share your knowledge.