Either no error and it doesn't run (The scripts all run fine manually and in the cron.daily, cron.hourly, etc. directories.) If it does try to run it, it shows this: Feb 16 12:59:01 buddha crond[3638]: (*system*) BAD FILE MODE (/etc/crontab). Here's my crontab:
I am using Linux 64 bit Redhat Linux. I am trying to setup simple crontab as follow...1. Edited crontab file using crontab -e2. Listed the file once to verify it using crontab -l. This will display as.. 18 5 * * 2-3 ksh $HOME/testScript.sh > $HOME/testscript.out3. Logged in a root and restarted cron deamon using "/etc/init.d/crond restart"As per my understanding now my testScript should start running at 5:18 am Thuesday
In RHEL6 root's account I have crontab job: 30 6 18 4 1 /sbin/init 6 It worked fine on the 18th of April and properly restarted my system, BUT it also restarted my OS at 6:30 on next Monday - 25th of April.
I have a question about using crontab with /etc/crontab...
I had a cron job that I needed to run as root. At the time I thought that sticking it in /etc/crontab would be a good idea. However, I used the crontab command to edit /etc/crontab, which I guess is not standard procedure? Specifically, I configured /etc/crontab as my local user's crontab (i.e. sudo crontab /etc/crontab) then added my cron job as I would a local user crontab (i.e. sudo crontab -e).
Originally, my cron job looked like this:
30 * * * * root /my/batch/script &> /dev/null
After adding the new cron job I started seeing errors. Something to the effect of "can't find command root" or something similar. So I removed the 'root' user definition from the cron job and the job started running fine. However, because this is /etc/crontab, there are other system related cron jobs that have been defined to run under the root account (e.g. "17 * * * * root cd / && run-parts --report /etc/cron.hourly" runs as root, etc.). So these pre-existing system cron jobs, which up until now have been running smoothly, are now generating "can't find command root" errors. But I think that the system cron jobs _are_ successfully being run someplace because logrotate seems to be working.
So what I _think_ is happening is that /etc/crontab is being run twice: once as the system crontab, and once as my sudoed local user's crontab. When I run crontab -l I see nothing, but when I run sudo crontab -l I can see the contents of /etc/crontab. I am reluctant to delete my sudoed local user's crontab, because then in the process I would be deleting the system crontab, and I do not know how I should restore the system crontab's contents. (I am still not sure as to the most appropriate way to edit the system crontab).
How can I get out of this mess? I want /etc/crontab to go back to the way it was before--running _once_ as the system crontab. As for my new cron job, I'm willing to reconfigure it anywhere so long as I am still able to run it as root. Any ideas? (I am using Ubuntu 8.04 Server LTE)
is it possible disabling a crontab job without deleting the crontab description entry (by crontab -e)?I could also accept to change the entry itself. Now it's:0 0 * * 0-6 /home/me/cron/script.csh
I am scheduling a command for a specific time every day. Linux crontab format which I am using :- MIN HOUR DOM MON DOW CMD 30 08 10 06 * /home/mach/script.sh Some presetting is required?
I got some crontab records and everything works fine. I installed mail server recently and all cron notifications started to come into my inbox. I'd like to receive only notifications about cron errors. I would rather not filter all notifications off.
lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty
I am running ubuntu 10.04 as a web/file server. I have set up several cron jobs in the past which until recently were executing normally. However, a few days ago, cron jobs stopped executing after a restart. I was able to fix the problem by deleting and reentering the cron jobs, but only until the next restart. ps -ef lists cron.
Summary: 1.) Cron was working --jobs executed without error and restarts worked fine 2.) Cron jobs stopped executing after a restart about a week ago --ps -e still lists cron 3.) Removing all cron jobs and reentering them by copying and pasting fixes until next restart 4.) Cron job syntax is known to be correct since they were executing before this problem arose.
I have installed an application manager(monitoring application) on my linux server. Now, i need to have backup schedule for my application. The application itself has executive file to backup database.But when i put this file in my crontab to schedule the backup program it wont run!50 09 * * * root /opt/ME/AppManager9/bin/BackupMysqlDB.sh
If I configure a crontab like below.12 3 12 4 4 cat /etc/passwd I know that the cat command will get executed at the configured time. But where will the output of that command go?If it is something like below, then out put will be routed to /tmp/file1.12 3 12 4 4 cat /etc/passwd > /tmp/file1
I know crontab -e sets a cronjob in /var/spool/cron but how do I set a cronjob to run from /etc/crontab? Is there a command used for this or would I have to manually edit a certain file?
I want to set up a crontab so that from my machine {which is 192.168.0.99}whatever I create in a directory called "/information" {suppose some texts files}will be copied to 192.168.0.100 and 192.168.0.101's machine "/readinfo" directory at 5.30 pm. everyday."/readinfo" is directory which is accessible by all users on that machines {192.168.0.100 & 192.168.0.101}is this crontab right?30 5 * * * /bin/cp -rf /information/* 192.168.0.100:/readinfo30 5 * * * /bin/cp -rf /information/* 192.168.0.101:/readinfoI guess first these 100 and 101 machines should allow me {99} ssh connection without passowrd.
My laptop's clock (Acer Extensa 5220) seems to be slow. I've corrected it 5 minutes forward last week and now have just corrected minute forward again. Is there a program [apart from time servers] to correct clock properly, for example, by shifting it a bit every hour? Is there already a program to put it to crontab or I should hack up a script? Or I should check more things?
I have found that HW clock is right, but system time is slow: about a second each 2.1 hours. root@vi-notebook:~# dmesg | egrep 'clock|unstable' [ 0.103785] Switching to clocksource tsc [ 0.265274] Marking TSC unstable due to TSC halts in idle [ 0.265514] Switching to clocksource acpi_pm [ 1.321408] rtc_cmos 00:09: setting system clock to 2010-10-30 00:10:48 UTC (1288397448) Is placing "hwlock --hctosys" to crontab a right thing?
Im new to linux, using ubuntu 10.04. I have been playing around with crontab and have no problems scheduling a job which runs a script file containing the following command:
However, when I try to do the following in the script file nothing happens..
Similarly the following doesnt do anything either:
As you can see two of the lines are commented out. However, both commented out commands are still running. I get emails stating that the RALUS agent restarted (another mystery since it's supposed to go to dev null according to the line above), and I can see that the memmon script is also running daily. Am I missing a step? Some other place I should be looking? Commenting out lines in your crontab is pretty much a no-brainer, so I appear to have less than no brain as this is a mystery to me.
I'm running Ubuntu server 8.04.3 with eBox on a Dell GX280. I want to power off my box automatically every night, so as root I added a crontab entry "05 1 * * * /sbin/shutdown -P now". The command runs on schedule but most days the PC goes into a coma instead of powering off. It doesn't respond to key presses or mouse movement or Ctrl-Alt-Delete, I have to push its power button to complete the shutdown. I have tried a variety of alternatives such as "/sbin/shutdown -h" and "runlevel 0", they all behave the same way
I want to schedule a crontab for shutting down the oracle application services. I created crontab -e by login as oracleuser and added time and run-part(script path to execute the cron). But i unable to execute on the schedule time. exact procedure for creating and execution of cronjobs in RHEL-5.
I have set up my crontab and whilst Im logged in and it works (It runs my shell script), however when Im not logged in, the script does not run. Initially I set the time/date to 0 0 * * * (Midnight every day), as this did not work, I tested it with to 0 * * * * (every hour) whilst logged in and the script starts.
I use crontab -e to set it up under the root account..Im sure you dont have to be logged in for it to run?, but maybe im missing a step or just overdosing on Linux and need a holiday:-)