It seems that cron is not upgrading my Ubuntu 8.04 LTS Server, no GUI installed. I changed /etc/crontab and watched apt running:
Code:
ps -A | grep apt
showed it for a long time,
Code:
sudo tcpdump tcp
showed communication with canonical sites,
but:
Code:
top
did not show any apt using CPU
[code].....
I have added some executable scripts to /etc/cron.daily but don't get the stdout/stderr output from them as mail (or anywhere else I have found). At least one of them is running (because I can see that it has added a file to the disk).
The peculiar thing is that I do get the output from /etc/cron.daily/0logwatch (part of the logwatch package) as an email each day.
The MAILTO line in /etc/crontab is "MAILTO=root" (unchanged from default). Same for /etc/anacrontab.
I do have an alias at the end of /etc/aliases which redirects root's mail to my own account, but this alias works fine for mail I send manually. (It also appears to work fine for the output from the file /etc/cron.daily/0logwatch.)
I am running on a laptop and cron.daily is set to run at 0625 So I wonder what happens if my machine is not turned on at that time.. At that rate it could also be off for the other periods as well (weekly, monthly) Is there solution that will allow them to run once they are online after the appointed time? using a cron entry that runs every 15 or 5 or 1 minute.
View 2 Replies View Relatedsince I setup my system so that I'd receive system errors via email, I get an email each day from /etc/cron.daily/apt.Just wondering why this is, how I can fix it, or if I can just remove apt from cron.daily?uote:
To: root@jon-desktop
Subject: fcron <systab@jon-desktop> run-parts --report /etc/cron.daily
/etc/cron.daily/apt:
[code]....
I'm with Ubuntu server 10.10. I created a script and put it in /etc/cron.daily. But looks it doesn't run (it didn't generate any log). The following is all I did.
Code:
root@chonseng1:/var/log# cat /etc/crontab
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab' command to install the new version when you edit this file and files in /etc/cron.d. These files also have username fields, that none of the other crontabs do.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#
root@chonseng1:/var/log# ls -l /etc/cron.daily/ntpdate
-rwxr-xr-x 1 root root 52 2011-02-18 13:22 /etc/cron.daily/ntpdate
root@chonseng1:/var/log# cat /etc/cron.daily/ntpdate
ntpdate ntp.ubuntu.com >>/var/log/ntpdate.log 2>&1
I have an issue, it doesn't happen every day, I can't seem to trace it down. It happens at 4:02am the cron.daily kicks of at 4AM.. The following is from the /var/log/messages. I receive an panic error then the server shuts down.
View 1 Replies View RelatedI'm having a very strange issue with cron on centos 5.3 64-bit. I have 3 cron scripts in /etc/cron.daily which run backups. They are as follows:
script1:
#!/bin/bash
/usr/local/bin/backup-script1
script2:
#!/bin/bash
/usr/local/bin/backup-script2
script3:
#!/bin/bash
/usr/local/bin/backup-script3
The contents of the 3 /usr/local/bin scripts are ...
/usr/local/bin/backup-script1:
#!/bin/bash
synbak -s srv1 -m rsync
rsync -av --delete /data/backup/srv1/* root@::share/srv1/
To explain this, the 1st active line does a synbak backup and the 2nd active line rsyncs the backup data to a remote server.
/usr/local/bin/backup-script2:
#!/bin/bash
synbak -s srv2 -m rsync
rsync -av --delete /data/backup/srv2/* root@::share/srv2/
[code]....
My backup script works fine after some effort to get it where I wanted it. So the script is fine when I run it.
sudo bash backup.sh
now I have a sym-link to /etc/cron.daily but I do not see any new backups
I made a big rookie mistake in a script in cron.daily, which emptied the directory when I tested it... now I'm left with an empty cron.daily directory, and from what I know there definitely were more scripts there than only my own. Does anybody know what scripts CentOS 5.4 (Final) needs in the cron.daily?
View 3 Replies View RelatedI have noticed that in the /etc directory there are some subdirectories of /etc/cron.daily and /etc/cron.hourly. Also I have determined that there is a service included as part of the Fedora OS 'crond' which I have started with the use of 'service crond start'. My question is this. If I drop an executable file into the '/etc/cron.daily' directory will it just run? If not what configuration files should I go about editing to run my executable daily? There seems to be a pretty large network of cron related files. I'm trying to make sense out of all of it.
View 9 Replies View RelatedI have two custom tasks running daily. How do you give priority to one over the other?One of them is configured via the logrotate.conf. The other sits directly in cron.daily.I'd like the one in cron.daily to run after the script that is in logrotate.Please can you advise how to do this...
View 3 Replies View RelatedCan anyone tell me how i change the default domain name for cron?everything i cron runs it emails from and to user@com.com
this leaves me with a massive list of failed mails in postfix.i have mailto on my main crontab but i cant do it on all of them.
I put in my cron entries to run my backup script which rsyncs my data to my 2nd drive, however on a hunch I checked my backup drive which mounts automatically via fstab and I realize it had not ran in a while. I checked cron and there were no entries for it. I got to wondering if I should ever be worried about a cron update coming down and over-writing my existing cron file with the backup entries in it to run.
View 2 Replies View RelatedI have set up a cron in /var/spool/cron/root
*/15 * * * * /usr/bin/phplist.sh
I can see in /var/log/cron that it is running every 15 minutes but it has no effect. It is not doing the commands in the bash script.
If I run /usr/bin/phplist.sh right in the shell it works great.
Is my vixie-cron broken? i have "0-59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf" but it is not running in /etc/cron.d.
Code:
After upgrading Ubuntu from 9.10 to 10.04, the cron daemon no longer runs automatically upon starting up the machine; I need to enter "sudo service cron start" to get it running. Is there a way to get it to start up by itself?
View 3 Replies View RelatedHopefully a simple question but one I have had a hard time finding:I am using cron-apt to automate updates as follows:
Code:
graham@graham-desktop:~$ sudo cat /etc/cron.d/cron-apt
#
[code]....
I have this script:
#!/bin/bash
## cifro un fichero
/usr/bin/gpg --encrypt --batch --no-tty --yes --recipient Mypubkey /home/joseba/salida.txt > /home/joseba/logcronjob.txt
#EOF
If I use the line
joseba@server$ /usr/bin/gpg --encrypt --batch --no-tty --yes --recipient Mypubkey /home/joseba/salida.txt > /home/joseba/logcronjob.txt
I dont have problems, salida.txt has encrypted
But by crontab -e (for user joseba) dont work and dont encrypt nothing If I use 'sudo crontab -e' same result, dont work
Mypubkey exists
On logcronjob.txt nothing, 0 bytes I think env its ok for the users
I've been trying to accomplish this on my own, but I can't seem to figure it out...
All I'm trying to do (for learning purposes) is to get a message to print out to a log file every 5 minutes.
This is on Ubuntu Server 6.06.
Logged in as root ( I know, I know, should have sudo'd, oh well... )
Created a new file with this in it:
Code:
Added this line:
Code:
( I wasn't sure the proper command to try every 5 minutes, but this is my latest iteration. I also started with just */5, and that didn't seem to work either. )
Saved and exited crontab.
Console reports:
Quote:
Using command: ps -ef | grep cron
Quote:
So I waited 10 minutes to be safe.... and saw no log file appear.
I checked this page here: [url]
I wasn't sure what it meant by the PATH= variable they wanted me to set, my /etc/crontab file states:
Code:
But I didn't know if it meant there, or in my crontab -e location, so after the first failed attempt, I added the line from that webpage as well to crontab -e:
Code:
Waited another 10 minutes to be safe, still nothing.
why my second cron job isn't running? The first one runs fine but the second one does not run at all. If I manually run the script using ./check.sh then it does what it is supposed to but will not run from cron. It should run every weekday at 9:45am, it looks good to me but clearly I am doing something wrong.
Code:
# m h dom mon dow command
#This will backup my hosted websites.
0 2 * * * /home/bob/scripts/websitebakscript.sh
#This will run check and upload it's contents to the net.
45 9 * * 1,2,3,4,5 /home/bob/scripts/check.sh
I'm trying to set up my pc to power off at 00:30 everynight. I'm using webmin's Scheduled Cron Jobs tool. I've tried (running as root):
halt
shutdown -h now
and neither have powered off the pc using webmin. Am I missing something?
How do I run a script in cron? would I do it like this:
Code:
* * * * * script.sh
Cron refuses to work for a newbie.I am trying to setup a cron job to backup a folder in my home directory ('/home/scratch') to a folder ('home/internet_backup') that is mounted (using nfs) to a network folder.the folder ('home/internet_backup') is mounted correctly to the network folder upon system startup, so this part works.
View 4 Replies View RelatedAfter I create a cron job to shred some documents it seems to start and then immediately stop. What am I doing wrong? For instance, here is my cron:
#!/bin/sh
DISPLAY=:0.0
PATH = /usr/local/bin:/usr/bin:/usr/sbin:/bin:/sbin:
[code]....
I have a working bash script to do backup - it runs fine from the terminal. During the backup it makes a log file in my home area. I transferred it to root, and set it up to run as a cron job as root. It runs fine as long as I am logged in with my normal user name. It does not run if I am not logged in. Logs show the script was called by cron, but there is no output and no backing up is done.
Here is the script
Code:
#!/bin/bash
for i in `cat /proc/mounts | cut -d' ' -f2`; do
if [ "$i" = "/media/Elrond" ]; then
[code]....
I am making a webpage which is to be automatically generated every minute. I've created a cron job in crontab like this:
Code:
0-59 * * * * /usr/bin/php /var/www/site/updatestatistics.php > /dev/null
When I refresh the page 'updatestatistics.php' in my webbrowser it does generate a new page ('statistics.html', which is included in 'statistics.php'). But when I let this cron job do the job, nothing happens. I looked into the log file, it shows this:
Code:
(root) CMD (/usr/bin/php /var/www/site/updatestatistics.php > /dev/null)
I have this symlinked into my /etc/cron.d folder:
Code:
*/5 * * * * python /srv/bidsite/manage.py send_mail
* * * * * echo `date` >> /home/bidsite/what.txt
but it does nothing. What I really want to happen is the first line. The second line is just for testing.
After saving a few sample scripts in crontab, I discovered that cron is not running properly on my Ubuntu 9.10 (32 bit), after a recent reinstallation. Please note that the files "/var/log/cron" and "/etc/defaults/rc.conf" are empty in my system.
View 4 Replies View RelatedI'm trying to get this script, which normally works fine, to run from cron. This is far from my first custom cron script, but it's the first to give trouble! I've added PATH directives (never had to do that before) but it still didn't work. I also tried setting absolute paths, that didn't help either. If I add a line that echoes a string to a file as a test at the end of the script, the file appears, so I know the script is executing, it just looks like the cpufreq-set commands aren't working. The purpose of this script is to adjust the maximum SpeedStep setting on my now passively-cooled home server to keep the CPU from getting too toasty.
Code:
#! /bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin
# set temp above which to drop the maximum frequency
scaledowntemp=`echo -n "62"`
# set temp below which to reset the maximum frequency
scaleuptemp=`echo -n "59"`
# get cpu temperature
cputemp=`sensors | grep "Core 0" | gawk '{print $3 }' | sed -e 's/+//g' | sed 's/....$//'`
if [ $cputemp -lt $scaleuptemp ] # if temp is in acceptable range, set max frequencies free
then
cpufreq-set -c 0 -u 2.81Ghz
cpufreq-set -c 1 -u 2.81Ghz
fi
if [ $cputemp -gt $scaledowntemp ] # if temp is too high, limit cores to 1.6Ghz
then
cpufreq-set -c 0 -u 1.61Ghz
cpufreq-set -c 1 -u 1.61Ghz
fi
I have this in my crontab (along with another line before it):
Code:
* * * * * /bin/echo "Does this work?" > ~/test
...and the file doesn't show up. I have a blank line after that one in the crontab. I have no /etc/cron.allow or /etc/cron.deny files. I'm running Ubuntu 11.04. /var/log/syslog shows "BEGIN EDIT" and "END EDIT" etc. when I run crontab -e, but doesn't say anything about trying to run commands. Anything I might be missing?