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.

Logwatch issue

Discussion in 'General Discussion' started by arhs, Nov 10, 2005.

  1. arhs

    arhs Well-Known Member

    Joined:
    Jul 4, 2003
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    Hi

    I’m having problems with Log watch lately, it is not sending out any further logs other then this e-mail (see below), and I have tried upgrading to the latest version of Log watch and again with the latest version I do not get any furthers logs.

    I’m currently running:
    -CentOS 4.2
    -WHM 10.8.0 cPanel 10.8.1-S31

    Can any one let me know how to fix this issue?


    Thanks


    PHP:
     ################### LogWatch 6.1 (05/17/05) #################### 
            
    Processing InitiatedThu Nov 10 11:07:13 2005
            Date Range Processed
    yesterday
                                  
    2005-Nov-09 )
                                  
    Period is day.
          
    Detail Level of Output0
                  Type of Output
    unformatted
               Logfiles 
    for Host: ************
      
    ################################################################## 
     
     
    --------------------- clam-update Begin ------------------------ 

     
    The ClamAV updated process was started 2 time(s)
     
     
    Last ClamAV update process started at Wed Nov  9 13:08:34 2005
     
     Last Status
    :
        
    main.cvd is up to date (version34sigs39625f-level5
    buildertkojm)
        
    daily.cvd is up to date (version1166sigs1607f-level6
    buildertomek)
     
     ---------------------- 
    clam-update End ------------------------- 

     
     --------------------- 
    Disk Space Begin ------------------------ 

     /
    dev/sda1                              99M    16M    79M  17%  /boot
     
    /dev/mapper/VolGroup00-LogVol00       146G   2.6G   136G   2%  /
     /
    usr/tmpDSK                           485M    11M   449M   3%  /tmp
     
    /tmp                                  485M    11M   449M   3%  
    /var/
    tmp
     
     
     
    ---------------------- Disk Space End ------------------------- 

     
     
    ###################### LogWatch End ######################### 

     
  2. Zaf

    Zaf Well-Known Member

    Joined:
    Aug 22, 2005
    Messages:
    119
    Likes Received:
    0
    Trophy Points:
    16
    Edit your config (probably is /etc/log.d/logwatch.conf) & change the parameter 'Detail' and set it to High.
     
  3. arhs

    arhs Well-Known Member

    Joined:
    Jul 4, 2003
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    I already tried that, still I’m getting the same e-mail.

    PHP:
    ################### LogWatch 6.1 (05/17/05) #################### 
            
    Processing InitiatedThu Nov 10 11:43:15 2005
            Date Range Processed
    yesterday
                                  
    2005-Nov-09 )
                                  
    Period is day.
          
    Detail Level of Output10
                  Type of Output
    unformatted
               Logfiles 
    for Host: ******
      
    ################################################################## 
     
     
    --------------------- clam-update Begin ------------------------ 

     
    The ClamAV updated process was started 2 time(s)
     
     
    Last ClamAV update process started at Wed Nov  9 13:08:34 2005
     
     Last Status
    :
        
    main.cvd is up to date (version34sigs39625f-level5
    buildertkojm)
        
    daily.cvd is up to date (version1166sigs1607f-level6
    buildertomek)
     
     ---------------------- 
    clam-update End ------------------------- 

     
     --------------------- 
    Disk Space Begin ------------------------ 

     /
    dev/sda1                              99M    16M    79M  17%  /boot
     
    /dev/mapper/VolGroup00-LogVol00       146G   2.6G   136G   2%  /
     /
    usr/tmpDSK                           485M    11M   449M   3%  /tmp
     
    /tmp                                  485M    11M   449M   3%  
    /var/
    tmp
     
     
     
    ---------------------- Disk Space End ------------------------- 

     
     
    ###################### LogWatch End ######################### 
     
  4. Zaf

    Zaf Well-Known Member

    Joined:
    Aug 22, 2005
    Messages:
    119
    Likes Received:
    0
    Trophy Points:
    16
    I'm not 100% sure, but you should probably wait for a day to see the effect.
     
  5. arhs

    arhs Well-Known Member

    Joined:
    Jul 4, 2003
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    I had the 'Detail' parameter set to 'High' few days ago and still getting the same e-mail. :confused:
     
  6. Aric1

    Aric1 Well-Known Member

    Joined:
    Oct 15, 2003
    Messages:
    324
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    DataCenter Provider
    Did you try updating to the latest stable version and see if that helps you?
     
  7. sawbuck

    sawbuck Well-Known Member

    Joined:
    Jan 18, 2004
    Messages:
    1,367
    Likes Received:
    5
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Do you have "Service = All" in the default.conf?

    Also the directory structure of the latest logwatch has been changed to /usr/share/logwatch/.

    To check after making config changes try running it like this:
    "/usr/share/logwatch/scripts/logwatch.pl --range today" and see what the output looks like.
     
  8. arhs

    arhs Well-Known Member

    Joined:
    Jul 4, 2003
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    [1] Yes

    [2] Same thing....

    PHP:
     ################### LogWatch 7.0 (10/12/05) #################### 
            
    Processing InitiatedThu Nov 10 17:09:02 2005
            Date Range Processed
    today
                                  
    2005-Nov-10 )
                                  
    Period is day.
          
    Detail Level of Output10
                  Type of Output
    unformatted
               Logfiles 
    for Host: *********
      
    ################################################################## 
     
     
    --------------------- clam-update Begin ------------------------ 

     
    The ClamAV updated process was started 1 time(s)
     
     
    Last ClamAV update process started at Thu Nov 10 01:37:12 2005
     
     Last Status
    :
        
    main.cvd is up to date (version34sigs39625f-level5
    buildertkojm)
        
    daily.cvd is up to date (version1166sigs1607f-level6
    buildertomek)
     
     ---------------------- 
    clam-update End ------------------------- 

     
     
    ###################### LogWatch End ######################### 

     
  9. sawbuck

    sawbuck Well-Known Member

    Joined:
    Jan 18, 2004
    Messages:
    1,367
    Likes Received:
    5
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Not knowing exactly how you got here (pervious version, upgrade choice, etc.) my inclination would be to tear it out and start over. Generally logwatch is an application that runs well with very little intervention.
     
  10. arhs

    arhs Well-Known Member

    Joined:
    Jul 4, 2003
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    The reason I upgraded from the pervious version to the latest version was that I was not receiving the Log watch e-mails at all and now I have reverted back to the pervious version (5.2.2) and I'm still not receiving any e-mails, I have checked the exim (exim_mainlog ) log file and there is no log listed for logwatch ........? :confused:


    PS: It fairly a new server , set up over a week ago.
     
  11. arhs

    arhs Well-Known Member

    Joined:
    Jul 4, 2003
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    Problem resolved :)

    By restarting the server and then uninstalling log watch, then reinstalling it.


    Thanks to those who tried to help.
     
Loading...

Share This Page