Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I look into a lot of answers about this subject, but something is wrong here, let me explain. I create this script, to make my cron cleaner :)


cd /home/valter.silva/Development/git/valter/ 
/usr/bin/git add -A 
/usr/bin/git commit -am "update `date`"
/usr/bin/git push

Then add it at my cron, valter.silva's cron, not my root cron:

00 * * * * /home/valter.silva/Development/git/valter/scripts/git/

Restart my cron

sudo service cron restart
cron stop/waiting
cron start/running, process 6047

Aaand .. nothing happens..

But if I execute my script in command line, everything works fine. I know for a fact that sometimes if you don't put the whole path at cron scripts won't work correctly. And that I should use my cron to do that, not root's cron.

So what's wrong here ? Any ideas ? Thank you!


I follow Terdon suggestion, into log the operation, but it seems everything is okay, but not the push process though. Why ?

[master ad5d001] update Fri Aug  9 11:00:01 BRT 2013
 9 files changed, 1224 insertions(+), 364 deletions(-)
 create mode 100644 scripts/centreon/4.answers~
 create mode 100644 scripts/centreon/6.importing database
 create mode 100644 scripts/centreon/6.importing database~
 create mode 100755 scripts/centreon/
 create mode 100755 scripts/centreon/
 create mode 100644 scripts/centreon/8.answers
 create mode 100644 scripts/centreon/8.answers~
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
nothing to commit (working directory clean)
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
nothing to commit (working directory clean)
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
nothing to commit (working directory clean)
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
nothing to commit (working directory clean)
share|improve this question
How did you add this to your user's crontab (you should use crontab -e)? What does crontab -l report? You can try to add SHELL=/bin/bash and MAILTO="valter.silva" into your user's crontab. Especially the latter might give you some error messages in your local mail (/var/spool/mail/valter.silva) if local mail system is working. And IMHO there is no need to restart the cron service. – mpy Aug 9 '13 at 12:09
crontab -e, not sudo crontab -e. The crontab -l is exactly that entry that I post it, there's only this entry in my cron. – Valter Henrique Aug 9 '13 at 12:44
Is the remote git server protected by an ssh key with a password by any chance ? – user2313067 Jun 24 '14 at 6:00

I am not an git master, but I make some git tests on my local git test repo. When I run git push, then output is:

fatal: No configured push destination.
Either specify the URL from the command-line or configure a remote repository using

git remote add <name> <url>

and then push using the remote name

git push <name>

Q: Have you configured remote repository using git remote add command? If yes, try run git push with name of remote repository. If no, configure one, or use git push with remote repository url on command line (git push git://host.xz[:port]/path/to/repo.git/ ).

share|improve this answer
I did configure with git remote add, I will look into it. – Valter Henrique Aug 19 '13 at 14:00

Why would you expect something to happen? You have told cron to run your script every hour, on the hour. If you modified your crontab at, say, 13:02 nothing is going to happen until 14:00.

Try waiting a while, until the time hits XX:00, your script should run. Oh, and there is no need to restart cron, it will read the new crontab and run it next time it should be run.

If you have waited long enough and your script is still not being run, try redirecting the error output to check if anything is happening:

00 * * * * /home/valter.silva/Development/git/valter/scripts/git/ 2> /home/valter.silva/error.txt

Also try setting up a dummy cron job to see if that works:

00 * * * * date > /home/valter.silva/date.txt
share|improve this answer
I'm trying to run this over a week now, trying to figure out what is happening to not commit my changes. – Valter Henrique Aug 9 '13 at 12:42
@ValterHenrique see updated answer for a couple of suggestions. – terdon Aug 9 '13 at 12:53
Ok, terdon, will do that. I'm cloning my repo in a different computer now :) – Valter Henrique Aug 9 '13 at 13:01
I update my post, could you please take a look ? – Valter Henrique Aug 9 '13 at 14:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.