Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Sat Oct 08, 2011 3:04 pm 
Offline
Newbie

Joined: Sat Oct 08, 2011 3:01 pm
Posts: 2
Dear members,


I have a quick question - cron used to send emails when any cron tasks/script was executed but just noticed that since a few days emails are not coming when cron runs. I can still send mailx emails from shell scripts though. But cron run per se isnt sending mails anymore. The mails used to come from "Cron Daemon root@<my_linode>.members.linode.com".

Any pointers please?

Thanks and regards,
Anshuman


Top
   
 Post subject:
PostPosted: Sat Oct 08, 2011 3:42 pm 
Offline
Senior Member
User avatar

Joined: Thu Jun 16, 2011 8:24 am
Posts: 412
Location: Cyberspace
Did you change the entries in your crontab just before the emails stop coming through? How about your mail server settings?

_________________
Kris the Piki Geeker


Top
   
 Post subject:
PostPosted: Sat Oct 08, 2011 3:59 pm 
Offline
Newbie

Joined: Sat Oct 08, 2011 3:01 pm
Posts: 2
I dont remember changing, but I noticed its been not sending emails since mid Sept, so not sure if I did do any upgrades.

I have some scripts which use mailx, if I run them manually they do send the email. So the mail system must be okay. However the emails which use to auto generate on cron runs have stopped. MAILTO variable is set properly too.

cat /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=admin@mydomain.com
HOME=/

# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly

Any pointers will be much appreciated.


Top
   
 Post subject:
PostPosted: Sat Oct 08, 2011 4:19 pm 
Offline
Senior Member
User avatar

Joined: Thu Jun 16, 2011 8:24 am
Posts: 412
Location: Cyberspace
Updates can occassionally break things. Some package managers will replace existing configuration files with a default one, and will rename the original configuration before hand. Sometimes it's even a mistake in the code that was missed when they release.

Make sure everything is up-to-date, then search through the config files for your mail server to make sure it didn't rename/replace your config files. If you know the name of the config files you need to look at, the following command can speed things up:
Code:
updatedb && locate something.conf | grep etc

You'll need either mlocate or slocate installed to do that, though most systems have one of those installed by default.

Replace something.conf with the name of the config file. The "| grep" ([pipe character] grep) part will act as a filter for locate, and will only let the results show that have etc in them, which is useful for config files since most of them are in /etc.

Only look at the stuff for your mail server and cron. It's unlikely anything else will have broken cron's ability to send emails.

_________________
Kris the Piki Geeker


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group