Edit /etc/rsyslog.conf
$ sudo nano /etc/rsyslog.conf
Un-comment cron line
cron.* /var/log/cron.log
Save file and restart rsyslog
$ sudo systemctl restart rsyslog
Category: Cron
Sometimes you need to add an email to receive alerts and other emails for you system or business. WThen after a while the email account is full of emails. One method to automate this is to set up a cron in cpanel to remove the emails. Here is an example.
bin/find /home/cpaneluser/mail/domain.name/emailuser/new -type f -exec rm {} \;
The mail sent by your server’s cron jobs are refused by the recipient server due to:
"Action: failed Final-Recipient: user;user@domain.com Status: 5.0.0 Remote-MTA: dns; inbound.smtp.domain.com Diagnostic-Code: smtp; 553 5.1.8 ... Domain of sender address root@hostname.domain.com does not exist"
Crontab will by default send from $LINUX_USER@$HOSTNAME. You can change this by connecting to the server via SSH, running “crontab -e”, and adding “MAILFROM=VALID_ADDRESS_HERE”. Ideally, the MAILFROM will be set to a mail account hosted on your server, but if it is a valid domain, the recipient address will accept it.
Currently your messages log is filling up with errors and the system is unstable. Check the message log:
$ server# tail -f /var/log/messages Jul 28 08:57:30 mail kernel: EXT4-fs warning (device sda3): ext4_dx_add_entry: Directory index full!
Check the sessions directory
$ server# php -i | grep session.save_path session.save_path => /var/lib/php/session => /var/lib/php/session
$ server# du -shcx /var/lib/php/session 1000.0M /var/lib/php/session 1000.0M total
A cron job similar to the following ran every day, or periodically, should prevent those files from accumulating.
# find /var/lib/php/session -type d -mtime -15 -delete
Manually
# find /var/lib/php/session -depth -mindepth 1 -maxdepth 1 -type f -cmin +120 -delete;
Sometimes the loads on apache can be high:
Set up th efollowin cron job.
#MAILTO=admin@coldriverdata.com #02 12 * * 1 /usr/bin/killall -9 httpd && /sbin/service httpd restart
Check you cron job. Make sure the path are okay.
This is likely due to Plesk using a chrooted environment. The user that is executing the script doesn’t have access to PHP. You have a few options:
1. Add PHP to the user’s chroot – http://kb.sp.parallels.com/en/115842
2. Disable the chrooted environment entirely – http://blog.blums.eu/2013/01/25/parallels-plesk-panel-11-non-chrooted-cronjobs
3. Run the script as root because root does have access to PHP (not recommended but if the script is trusted it might be ok).
How do I view currently setup or all running cron jobs under Linux operating systems?
The cron service searches its spool area (usually /var/spool/cron/crontabs) for crontab files (which are named after user accounts); crontabs found are loaded into memory. cron also reads /etc/crontab, which is in a slightly different format. Additionally, cron reads the files in /etc/cron.d: it treats the files in /etc/cron.d as in the same way as the /etc/crontab file. The intended purpose of /etc/cron.d/ directory feature is to allow packages that require finer control of their scheduling than the /etc/cron.{daily,weekly,monthly} directories to add a crontab file to /etc/cron.d.View Users Cronjob
Use the following syntax to view username users cronjob:
crontab -u userName -l crontab -u username -l
View Root User Cronjob
Just type the following command:
crontab -l
View /etc/crontab
A cronjob can be also run from /etc/crontab file. To view it, enter:
# less /etc/crontab
View Daily Cronjob
Type the following commands:
cd /etc/cron.daily/ ls -l cat filename
View Hourly Cronjobs
Type the following commands:
cd /etc/cron.hourly/ ls -l cat filename
View Weekly Cronjobs
Type the following commands:
cd /etc/cron.weekly/ ls -l cat filename
View Monthly Cronjobs
Type the following commands:
cd /etc/cron.monthly/ ls -l cat filename
View Software (Package) Specific Cronjobs
Type the following commands
cd /etc/cron.d/ ls -l cat filename