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.

Missing info in LogWatch

Discussion in 'General Discussion' started by carteluo, Jul 28, 2005.

  1. carteluo

    carteluo Member

    Joined:
    Jun 25, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Porlamar
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hi there

    In every day logwatch mail I only get disk space info, nothing more.. I've upgrade it to 6.1.2 but no luck.

    My Detail Level of Output is set to 5, service = all.

    The server is running Centos 4.1

    Anyone knows how to fix that?

    Thanks
     
  2. mtbwacko

    mtbwacko Well-Known Member

    Joined:
    Nov 30, 2004
    Messages:
    54
    Likes Received:
    0
    Trophy Points:
    6
    This just happened to me today, exact smae problem out of the blue, only I am using version 7.1. Anyone have any clues about this??
     
  3. mohdyasar

    mohdyasar Active Member

    Joined:
    Jun 27, 2004
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    6
    Wierd

    SAME HERE ,, using 7.3 just gives clanav and nothing esle
     
  4. tata13

    tata13 Active Member

    Joined:
    Feb 8, 2006
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Jakarta
    same here to,, use Logwatch 7.1 , email suddenly send no information
     
    #4 tata13, Nov 12, 2006
    Last edited: Nov 12, 2006
  5. Giannis

    Giannis Well-Known Member

    Joined:
    Jun 22, 2005
    Messages:
    54
    Likes Received:
    0
    Trophy Points:
    6
    Hello
    i am having the same problem with version Logwatch 7.3

    email shows only info about Clam and space used on server???

    Any help Please??
    Thank You
     
  6. crisdias

    crisdias Member

    Joined:
    Dec 8, 2005
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Boy oh boy

    Same here... using version 7.3.1.

    Oh boy, here we go...
     
  7. crisdias

    crisdias Member

    Joined:
    Dec 8, 2005
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Any update on this? I still get limited information on my daily logwatch...
     
  8. Danny_T

    Danny_T Well-Known Member

    Joined:
    Jul 19, 2005
    Messages:
    181
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Netherlands
    Is logwatch running before logrotatings?
    It must be the first to be run before all other daily things are run.

    Also i have also not much info from logwatch reports for 2 years.

    Logwatch works fine on a non cpanel server. logwatch looks at default logfiles.
    As cpanel uses also other logfiles , i think logwatch is not compatible with cpanel runing servers.
    My /var/log/messages is since cpanel install always empty.

    Danny.
     
  9. mctDarren

    mctDarren Well-Known Member

    Joined:
    Jan 6, 2004
    Messages:
    664
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    New Jersey
    cPanel Access Level:
    Root Administrator
    Danny, something is probably wrong with your syslogd if it's not writing to /var/log/messages - look in /etc/syslog.conf and see where it is pointing your log files toward. For others, do "service syslog status" and make sure syslog and your kernel log are running. Try restarting: "service syslog restart", see if that helps. Logwatch simply parses your log files and reports the findings. If you get empty results it usually means that something is wrong and your log files are empty. Hope that helps
     
  10. crisdias

    crisdias Member

    Joined:
    Dec 8, 2005
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Well, I simply tried logging in via SSH and then running logwatch manually with "period=today" (or whatever the paramenter is that parses today's logs). Go the same limited results. :(
     
  11. crisdias

    crisdias Member

    Joined:
    Dec 8, 2005
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    OK, looks like I solved it. Syslogd was not running properly, my /var/log/secure was empty. Killing it brought the logs back.

    It may be a coincidence or not, but I had a Mambo CMS security problem that let someone run a bot on my system. So the nasty thing must have shut Syslogd off to cover its tracks... :(
     
Loading...

Share This Page