Mail Delivery Stats update? BUGS!!! BUGS!!! BUGS!!!

web-project

Well-Known Member
Nov 23, 2007
67
11
58
Why the Mail Delivery Stats (/scripts2/eximstats) don't update the dates:

my server shows the following:
Exim statistics from 2009-10-06 11:40:01 to 2009-12-31 17:04:09
but it should show the stats from last time I click for Mail Delivery Stats report!

I hope the developers will fix the bugs in unstable cpanel control panel (cPanel 11.24.5-S38506 - WHM 11.24.2 - X 3.9).

I hope to hear from you.

Regards, Alex
 

cPanelDon

cPanel Quality Assurance Analyst
Staff member
Nov 5, 2008
2,545
12
268
Houston, Texas, U.S.A.
cPanel Access Level
DataCenter Provider
Twitter
Why the Mail Delivery Stats (/scripts2/eximstats) don't update the dates:

my server shows the following:

but it should show the stats from last time I click for Mail Delivery Stats report!

I hope the developers will fix the bugs in unstable cpanel control panel (cPanel 11.24.5-S38506 - WHM 11.24.2 - X 3.9).

I hope to hear from you.

Regards, Alex
The "from" date and time is not based upon the last time the page was checked via WHM.

I would check to ensure that your Exim mail server logs are being rotated; I would suspect the date and time (from October) is identical to the oldest entry in your current Exim log files (e.g., "exim_mainlog").

Via root SSH access, what is the output displayed by the following command?
Code:
# head -n1 /var/log/exim_mainlog
 

web-project

Well-Known Member
Nov 23, 2007
67
11
58
Via root SSH access, what is the output displayed by the following command?
Code:
# head -n1 /var/log/exim_mainlog
2009-10-06 11:35:03 non-existent configuration file(s): /etc/exim.conf
I have tried to:
/scripts/eximup --force
/scripts/buildeximconf

and still getting the:
non-existent configuration file(s): /etc/exim.conf
after running the command:
head -n1 /var/log/exim_mainlog
 

web-project

Well-Known Member
Nov 23, 2007
67
11
58
I tried also to rotate the file via command line using the following command:

logrotate -v /etc/logrotate.conf
result:
rotating pattern: /var/log/exim_mainlog weekly (4 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/exim_mainlog
log needs rotating
rotating log /var/log/exim_mainlog, log->rotateCount is 4
renaming /var/log/exim_mainlog.4.gz to /var/log/exim_mainlog.5.gz (rotatecount 4, logstart 1, i 4),
old log /var/log/exim_mainlog.4.gz does not exist
renaming /var/log/exim_mainlog.3.gz to /var/log/exim_mainlog.4.gz (rotatecount 4, logstart 1, i 3),
old log /var/log/exim_mainlog.3.gz does not exist
renaming /var/log/exim_mainlog.2.gz to /var/log/exim_mainlog.3.gz (rotatecount 4, logstart 1, i 2),
old log /var/log/exim_mainlog.2.gz does not exist
renaming /var/log/exim_mainlog.1.gz to /var/log/exim_mainlog.2.gz (rotatecount 4, logstart 1, i 1),
old log /var/log/exim_mainlog.1.gz does not exist
renaming /var/log/exim_mainlog.0.gz to /var/log/exim_mainlog.1.gz (rotatecount 4, logstart 1, i 0),
old log /var/log/exim_mainlog.0.gz does not exist
log /var/log/exim_mainlog.5.gz doesn't exist -- won't try to dispose of it
renaming /var/log/exim_mainlog to /var/log/exim_mainlog.1
creating new log mode = 0640 uid = 47 gid = 12
running postrotate script
compressing log with: /bin/gzip

rotating pattern: /var/log/exim_paniclog weekly (4 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/exim_paniclog
log needs rotating
rotating log /var/log/exim_paniclog, log->rotateCount is 4
renaming /var/log/exim_paniclog.4.gz to /var/log/exim_paniclog.5.gz (rotatecount 4, logstart 1, i 4),
old log /var/log/exim_paniclog.4.gz does not exist
renaming /var/log/exim_paniclog.3.gz to /var/log/exim_paniclog.4.gz (rotatecount 4, logstart 1, i 3),
old log /var/log/exim_paniclog.3.gz does not exist
renaming /var/log/exim_paniclog.2.gz to /var/log/exim_paniclog.3.gz (rotatecount 4, logstart 1, i 2),
old log /var/log/exim_paniclog.2.gz does not exist
renaming /var/log/exim_paniclog.1.gz to /var/log/exim_paniclog.2.gz (rotatecount 4, logstart 1, i 1),
old log /var/log/exim_paniclog.1.gz does not exist
renaming /var/log/exim_paniclog.0.gz to /var/log/exim_paniclog.1.gz (rotatecount 4, logstart 1, i 0),
old log /var/log/exim_paniclog.0.gz does not exist
log /var/log/exim_paniclog.5.gz doesn't exist -- won't try to dispose of it
renaming /var/log/exim_paniclog to /var/log/exim_paniclog.1
creating new log mode = 0640 uid = 47 gid = 12
running postrotate script
compressing log with: /bin/gzip

rotating pattern: /var/log/exim_rejectlog weekly (4 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/exim_rejectlog
log needs rotating
rotating log /var/log/exim_rejectlog, log->rotateCount is 4
renaming /var/log/exim_rejectlog.4.gz to /var/log/exim_rejectlog.5.gz (rotatecount 4, logstart 1, i 4),
old log /var/log/exim_rejectlog.4.gz does not exist
renaming /var/log/exim_rejectlog.3.gz to /var/log/exim_rejectlog.4.gz (rotatecount 4, logstart 1, i 3),
old log /var/log/exim_rejectlog.3.gz does not exist
renaming /var/log/exim_rejectlog.2.gz to /var/log/exim_rejectlog.3.gz (rotatecount 4, logstart 1, i 2),
old log /var/log/exim_rejectlog.2.gz does not exist
renaming /var/log/exim_rejectlog.1.gz to /var/log/exim_rejectlog.2.gz (rotatecount 4, logstart 1, i 1),
old log /var/log/exim_rejectlog.1.gz does not exist
renaming /var/log/exim_rejectlog.0.gz to /var/log/exim_rejectlog.1.gz (rotatecount 4, logstart 1, i 0),
old log /var/log/exim_rejectlog.0.gz does not exist
log /var/log/exim_rejectlog.5.gz doesn't exist -- won't try to dispose of it
renaming /var/log/exim_rejectlog to /var/log/exim_rejectlog.1
creating new log mode = 0640 uid = 47 gid = 12
running postrotate script
compressing log with: /bin/gzip
and it's worked:
Exim statistics from 2010-01-02 18:11:53 to 2010-01-02 18:14:48
 

cPanelDon

cPanel Quality Assurance Analyst
Staff member
Nov 5, 2008
2,545
12
268
Houston, Texas, U.S.A.
cPanel Access Level
DataCenter Provider
Twitter
The command I showed was only needed to display the first entry in the Exim mainlog to obtain the date and time for comparison with the Exim stats information in WHM; this command was only needed for information gathering to diagnose the issue:
Code:
# head -n1 /var/log/exim_mainlog
2009-10-06 11:35:03 non-existent configuration file(s): /etc/exim.conf
As seen by the first line of the exim mainlog, the log file was not rotated since October ("2009-10-06 11:35:03").

I tried also to rotate the file via command line using the following command:
logrotate -v /etc/logrotate.conf
result:
and it's worked:
Manually rotating the log is an option as you've noted; logrotate, installed with your OS distribution, is the tool normally used to manage rotation of the Exim logs.

To help ensure logrotate runs in the future, I would check to ensure that "crond" is installed and running, and then verify the crontab configuration has an entry for logrotate (as installed by the logrotate software package).

On CentOS and RHEL crond is included in the software package (RPM) named "vixie-cron"; the following command will check if both vixie-cron and logrotate are installed:
Code:
# rpm -q logrotate vixie-cron
If one or both are missing, the following command could be used to ensure both RPMs are installed:
Code:
# /scripts/ensurerpm logrotate vixie-cron
The following command could be used to check if crond is running:
Code:
# /etc/init.d/crond status
The following will check if the logrotate cron entry exists:
Code:
# stat /etc/cron.daily/logrotate
It may also help to check the contents of the following file: /etc/crontab; here is an example of how to do this (using the command "cat"):
Code:
# cat /etc/crontab
Here is an example using the above command showing the resulting output of what the file may contain (at "/etc/crontab"):
Code:
# cat /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/

# run-parts
10 * * * * root run-parts /etc/cron.hourly
51 3 * * * root run-parts /etc/cron.daily
50 3 * * 0 root run-parts /etc/cron.weekly
49 2 30 * * root run-parts /etc/cron.monthly