On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Anne
Anne Wilson wrote:
On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Anne
Are you receiving any mail from the box in question? If not, did you run newaliases and restart sendmail after you made the changes to the aliases file?
On Thursday 25 January 2007 13:33, Randy Kelsoe wrote:
Anne Wilson wrote:
On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Anne
Are you receiving any mail from the box in question?
Yes, I can send myself messages as anne@lydgate.lan and they get to the imap server without problems.
If not, did you run newaliases and restart sendmail after you made the changes to the aliases file?
Yes.
Anne
Anne Wilson wrote:
On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Stupid question -- you are running a mail server on the third box, aren't you?
What do its logs say?
James.
On Thursday 25 January 2007 13:38, James Wilkinson wrote:
Anne Wilson wrote:
On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Stupid question -- you are running a mail server on the third box, aren't you?
What do its logs say?
Haven't checked lately, and can't get to it just now. I'll check up on the logs as soon as I can.
Anne
On Thursday 25 January 2007 13:38, James Wilkinson wrote:
Anne Wilson wrote:
On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Stupid question -- you are running a mail server on the third box, aren't you?
What do its logs say?
Darn it - I can't believe it, but there was a typo in the /etc/postfix/transport file. Can't believe that I didn't spot that before. Now we'll see whether the next report comes through, and whether the old ones are queued.
Thanks
Anne
On Thursday 25 January 2007 16:23, Anne Wilson wrote:
On Thursday 25 January 2007 13:38, James Wilkinson wrote:
Anne Wilson wrote:
On two boxes I get messages sumarising completion, sent to root and forwarded to me. A third box, running FC4 like one of the other two, must be running the cron jobs, because the ssh accesses are reported by logwatch, yet I don't get the reports from that box. /etc/aliases names me for receiving root's mail. Have I forgotten somewhere else that it has to be enabled? I've a feeling that there is somewhere else, but I can't think of it.
Stupid question -- you are running a mail server on the third box, aren't you?
What do its logs say?
Darn it - I can't believe it, but there was a typo in the /etc/postfix/transport file. Can't believe that I didn't spot that before. Now we'll see whether the next report comes through, and whether the old ones are queued.
Unfortunately that has only partially solved the problem. I'm now getting logwatch messages, but no cron ones. There is a small backup job due to run twice daily, and I haven't seen any message for it yet. The job clearly ran this afternoon, as I can see files on the backup drive that were not created until this morning.
Anne
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now getting | logwatch messages, but no cron ones. There is a small backup job due to run | twice daily, and I haven't seen any message for it yet. The job clearly ran | this afternoon, as I can see files on the backup drive that were not created | until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Is there a /var/log/maillog file tracing mail delivery? (Possibly another syslog file.)
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup job | due to run twice daily, and I haven't seen any message for it yet. The | job clearly ran this afternoon, as I can see files on the backup drive | that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Is there a /var/log/maillog file tracing mail delivery? (Possibly another syslog file.)
Hi, Cameron. I can't understand what's happening. I have been through every logfile that might have the remotest connection with this, and can find no sign of the messages. For that matter, I can find no sign that the cron job has actually run today - except that files created as late as 11:40 today are on the backup disk.
I'm totally foxed!
Anne
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup job | due to run twice daily, and I haven't seen any message for it yet. The | job clearly ran this afternoon, as I can see files on the backup drive | that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Is there a /var/log/maillog file tracing mail delivery? (Possibly another syslog file.)
Hi, Cameron. I can't understand what's happening. I have been through every logfile that might have the remotest connection with this, and can find no sign of the messages. For that matter, I can find no sign that the cron job has actually run today - except that files created as late as 11:40 today are on the backup disk.
I'm totally foxed!
Anne, do you see anything relevant in /var/log/cron? (Sorry if this has already been covered...)
Cheers, Terry.
On Monday 29 January 2007 17:19, T. Horsnell wrote:
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup | job due to run twice daily, and I haven't seen any message for it yet. | The job clearly ran this afternoon, as I can see files on the backup | drive that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Is there a /var/log/maillog file tracing mail delivery? (Possibly another syslog file.)
Hi, Cameron. I can't understand what's happening. I have been through every logfile that might have the remotest connection with this, and can find no sign of the messages. For that matter, I can find no sign that the cron job has actually run today - except that files created as late as 11:40 today are on the backup disk.
I'm totally foxed!
Anne, do you see anything relevant in /var/log/cron? (Sorry if this has already been covered...)
I didn't, this morning, but it could have been overlooked, because I found one a short while ago for 16:30.
Anne
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup job | due to run twice daily, and I haven't seen any message for it yet. The | job clearly ran this afternoon, as I can see files on the backup drive | that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Bingo! This time I found a cron log entry for the run, so knew it had happened at a specific time. It is showing 'from david@localhost.localdomain' and 'to david@localhost.localdomain'. This sounds like a postfix problem to me. More digging is in order :-)
Anne
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup job | due to run twice daily, and I haven't seen any message for it yet. The | job clearly ran this afternoon, as I can see files on the backup drive | that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Light has suddenly dawned! The messages are arriving in David's mailbox - which he hasn't been checking :-) Looking back, these cron messages are always sent to the owner of the job - logical. There are two ways that I can deal with this. I can use kmail filters to redirect the message I think, or I can run the job as root, in which case the message will come to me.
I'll try the redirect first. If there are any problems, I'll go for the second.
Anne
On 31/01/07, Anne Wilson cannewilson@tiscali.co.uk wrote:
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup job | due to run twice daily, and I haven't seen any message for it yet. The | job clearly ran this afternoon, as I can see files on the backup drive | that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Light has suddenly dawned! The messages are arriving in David's mailbox - which he hasn't been checking :-) Looking back, these cron messages are always sent to the owner of the job - logical. There are two ways that I can deal with this. I can use kmail filters to redirect the message I think, or I can run the job as root, in which case the message will come to me.
Or tell cron to send the mail to you. As the first line in whosoever's crontab:
MAILTO=anne
On Wednesday 31 January 2007 11:50, Mark Knoop wrote:
On 31/01/07, Anne Wilson cannewilson@tiscali.co.uk wrote:
On Sunday 28 January 2007 23:19, Cameron Simpson wrote:
On 26Jan2007 19:25, Anne Wilson cannewilson@tiscali.co.uk wrote: | Unfortunately that has only partially solved the problem. I'm now | getting logwatch messages, but no cron ones. There is a small backup | job due to run twice daily, and I haven't seen any message for it | yet. The job clearly ran this afternoon, as I can see files on the | backup drive that were not created until this morning.
Are they being delivered to the machine itself instead? I have noticed that some jobs deliver to root@localhost or some icky variant like that, and some do not. Annoying.
Light has suddenly dawned! The messages are arriving in David's mailbox
- which he hasn't been checking :-) Looking back, these cron messages
are always sent to the owner of the job - logical. There are two ways that I can deal with this. I can use kmail filters to redirect the message I think, or I can run the job as root, in which case the message will come to me.
Or tell cron to send the mail to you. As the first line in whosoever's crontab:
Even better, thanks
Anne
-
Anne Wilson -
Cameron Simpson -
James Wilkinson -
Mark Knoop -
Randy Kelsoe -
Terry Horsnell