• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 757
  • Last Modified:

Crontab: Set to run every hour but runs every 15 minutes. Why?

I have the following set in /etc/crontab

40 * * * * root wget -q -O - 'http://www.mydomain.info/script.php' >/dev/null

Open in new window

To me this command should run every hour at +40 minutes.

For some reason though it runs every 15 minutes.

Can anybody see why?
0
AdrianSmithUK
Asked:
AdrianSmithUK
  • 6
  • 5
  • 3
3 Solutions
 
woolmilkporcCommented:
Comment deleted.

wmp
0
 
AdrianSmithUKAuthor Commented:
Dear woolmilkporc

That's not what you told me in this post - See accepted solution.

http://www.experts-exchange.com/OS/Linux/Q_26977577.html
0
 
woolmilkporcCommented:
That's why I deleted my comment - I was totally on the wrong track - don't have much time at this very moment.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
woolmilkporcCommented:
Sorry again, I obviously confused root's crontab with the system crontab - I've been in a hurry.

Now that our meeting has been cancelled I'm back.

Your cron job should indeed run every 40 minutes. I don't see any obvious reason why it should do something else.

Maybe you should restart the cron daemon, just to be sure?
0
 
legolasthehansyCommented:
Check as root - "crontab -l"
See if the changes you made reflect on the Cron.
0
 
AdrianSmithUKAuthor Commented:
Nice to have you back.

I had is set to:

0 * * * *

And it fired every 15 minutes from the hour. (10:00,  10:15 ...etc)

I changed it to

40 * * * *

Now it fires like this (11:40, 11:55 ...etc)
0
 
AdrianSmithUKAuthor Commented:
Dear legolasthehansy

[root ~]# crontab -l
[root ~]# 

Open in new window


I'm using Centos 6. When I run the command I get nothing.
0
 
legolasthehansyCommented:
Strange!

Check Cron logs.
Recreate the cron by deleting the entries and restarting CRON and then re-entering it.
Check if another user is running the same script using cron.
0
 
woolmilkporcCommented:
"crontab -l" would only work on root's crontab, not on /etc/crontab

Same confusion as mine before.

Did you recycle crond?
0
 
AdrianSmithUKAuthor Commented:
Dear legolasthehansy

I looked in /var/log/cron

There is only a record for the hourly cron jobs.

I have Plesk installed. Do you think it could be to blame?
0
 
woolmilkporcCommented:
I once read a bug report saying that an empty line just above a job entry could inhbit the correct scheduling of the job.

Could this be the culprit here?
0
 
legolasthehansyCommented:
Not sure if Plesk has a utility to setup CRON's. But it should still show up on the files.

If you know the users allowed to access this server,
can you do this,

crontab -l <username1> (This would list the CRON's setup by username1)

You can get the list of users in the server by doing a cat on /etc/passwd and get the list of recent logged in users using the 'last' command.
0
 
AdrianSmithUKAuthor Commented:
Chaps,

Thanks for your help.

I never found the solution to the original problem. I tried removing the spare lines, but still had the same problem.

I noticed that plesk runs a backup manager every 15 minutes which might be a clue.

Mar 16 13:16:01 sXXXXXXXX CROND[3453]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
Mar 16 13:31:01 sXXXXXXXX CROND[3453]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)

Open in new window



In the end I gave up and I used the built in plesk feature.

http://myhosting.com/kb/How_to_Set_Up_Scheduled_Tasks_(Cron_Jobs)_in_Plesk_10

I couldn't get it to work though.

In the end I found the problem was that SSH access was switched off for the domain.

Here is the solution:

http://drupal.org/node/1192934
0
 
AdrianSmithUKAuthor Commented:
Great Support!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now