The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

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

Discussion in 'E-mail Discussions' started by web-project, Dec 31, 2009.

  1. web-project

    web-project Member

    Joined:
    Nov 23, 2007
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    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
     
  2. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    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. web-project

    web-project Member

    Joined:
    Nov 23, 2007
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    I have tried to:
    /scripts/eximup --force
    /scripts/buildeximconf

    and still getting the:
    after running the command:
     
  4. web-project

    web-project Member

    Joined:
    Nov 23, 2007
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    I tried also to rotate the file via command line using the following command:

    result:
    and it's worked:
     
  5. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    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").

    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
     
Loading...

Share This Page