Community Forums
Connect with us on LinkedIn
+ Reply to Thread
Results 1 to 5 of 5
  1. #1
    Member
    Join Date
    Nov 2007
    Posts
    21

    Thumbs down Mail Delivery Stats update? BUGS!!! BUGS!!! BUGS!!!

    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

  2. #2
    cPanel Quality Assurance Analyst cPanelDon's Avatar
    Join Date
    Nov 2008
    Location
    Houston, Texas, U.S.A.
    Posts
    2,555
    cPanel/Enkompass Access Level

    DataCenter Provider

    Lightbulb

    Quote Originally Posted by web-project View Post
    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

  3. #3
    Member
    Join Date
    Nov 2007
    Posts
    21

    Default

    Quote Originally Posted by cPanelDon View Post
    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

  4. #4
    Member
    Join Date
    Nov 2007
    Posts
    21

    Default

    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

  5. #5
    cPanel Quality Assurance Analyst cPanelDon's Avatar
    Join Date
    Nov 2008
    Location
    Houston, Texas, U.S.A.
    Posts
    2,555
    cPanel/Enkompass Access Level

    DataCenter Provider

    Lightbulb

    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").

    Quote Originally Posted by web-project View Post
    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

Similar Threads & Tags
Similar threads

  1. BoxTrapper Bugs Last Update
    By Inndesign in forum cPanel and WHM Discussions
    Replies: 0
    Last Post: 11-01-2007, 01:48 PM
  2. problem/bugs with update disk-mail usage after clear spam box
    By xneme in forum cPanel and WHM Discussions
    Replies: 1
    Last Post: 11-15-2006, 01:02 PM
  3. Bugs, Bugs, Bugs!!!!
    By AbeFroman in forum cPanel and WHM Discussions
    Replies: 6
    Last Post: 08-13-2004, 08:03 PM
  4. Bugs in Last update, help requested
    By HostRod in forum cPanel and WHM Discussions
    Replies: 6
    Last Post: 08-18-2003, 03:24 PM
  5. Vertext Skin, will pay someone to update all bugs for me
    By XPerties in forum Themes and Branding
    Replies: 8
    Last Post: 05-08-2003, 11:40 AM
Tags for this Thread
Linkedin       Facebook       Twitter       RSS       Flickr       YouTube