Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: A.Scott Pringle on November 30, 2000, 09:11:01 AM
-
we have a machine that has been running version 4.0 for a number of months
upon upgrading i have noticed some problems getting worse that i hoped would be fixed 8(
the admin account keeps receiving these 2 mails about 50 so far today
1.
Subject: Cron /etc/startmail
********************************************************************
2.
Subject: Cron /etc/startmail
fetchmail: another foreground fetchmail is running at 16801.
mail is set to be checked every 5 mins between 8am and 6pm
the second error would happen intermittently with 4.0 but has gotten regular
the 1st error is a new one
and we have also noticed since the upgrade that the connection is a little flaky and drops carrier a lot
and mail isnt sending half the time
any ideas what the problems can be?
hope somebody can shed some light on these ones
cya
Scott
-
a quick fix for the emails to admin requires some editing
redirect stderr and stdout to /dev/null eg.
*/10 * * * 0-6 root /usr/bin/isp-check 1>/dev/null 2>/dev/null
pico /etc/e-smith/templates/etc/crontab/email
and insert 1>/dev/null 2>/dev/null a few times
$result .= "*/5\t8-17\t*\t*\t1-5\troot\t/etc/startmail\n";
-
A.Scott Pringle wrote:
> we have a machine that has been running version 4.0 for a
> number of months upon upgrading i have noticed some problems
> getting worse that i hoped would be fixed 8( the admin account
> keeps receiving these 2 mails about 50 so far today 1.
> Subject: Cron /etc/startmail
>
>
> ********************************************************************
>
I am getting the same problem. It appears to occur everytime an email is redirected. ie for every redirected email I receive one of these emails to admin.
complete email source below.
Return-Path:
Delivered-To: admin@sages.iinet.net.au
Received: (qmail 19510 invoked by alias); 4 Dec 2000 06:55:08 -0000
Delivered-To: root@sages.iinet.net.au
Received: (qmail 19507 invoked by uid 0); 4 Dec 2000 06:55:08 -0000
Date: 4 Dec 2000 06:55:05 -0000
Message-ID: <20001204065505.19500.qmail@sages.iinet.net.au>
From: root@sages.iinet.net.au (Cron Daemon)
To: root@sages.iinet.net.au
Subject: Cron /etc/startmail
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
***********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
before the upgrade to 4.0.1 thid didn't occur.
I have seen stephen's reply but am not happy with his solution as it doesn't seem to resolve the real issue, only dump the result to null!
Rod
-
Rod wrote:
> [...]
> before the upgrade to 4.0.1 thid didn't occur.
We changed the fetchmail logging to extremely verbose in 4.0.1 to help
people who are having troubles with fetchmail.
> I have seen stephen's reply but am not happy with his solution as it
> doesn't seem to resolve the real issue, only dump the result to null!
> Rod
I think Stephen's fix is a reasonable workaround. The mail logs don't
provide anything useful. We are looking into suppressing these in
a later update.
Gordon