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.

log files are empty

Discussion in 'General Discussion' started by iCARus, Jul 15, 2005.

  1. iCARus

    iCARus Well-Known Member

    Joined:
    Apr 8, 2003
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    16
    Hello.

    On one server with CentOS 4.1 and cpanel 10.2.0 C131 we got strange problems. System has empty logs like messages,secure,maillog.... all files from /etc/syslog.conf

    Log files for exim,bfd,..are work ok and are logged like they should. So we compare syslog.con file with other working server and nothing wrong.

    Can aynone help with this puzzle? I would be appreciated to anyone to help me fix this.

    syslog.conf


    /etc/logrotate.d/syslog

    Regards.
     
  2. nickb

    nickb Well-Known Member

    Joined:
    Feb 25, 2005
    Messages:
    347
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    India
    what about syslog service..is it running?
     
  3. iCARus

    iCARus Well-Known Member

    Joined:
    Apr 8, 2003
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    16
    Yes it's runing.

     
  4. ffeingol

    ffeingol Well-Known Member
    PartnerNOC

    Joined:
    Nov 9, 2001
    Messages:
    215
    Likes Received:
    1
    Trophy Points:
    18
    cPanel Access Level:
    DataCenter Provider
    we're having a similar problem on centos 4.1. The logs get rotated, but syslogd never gets hupped (eventhough it's in the logroate file) so the log file never gets closed and it keeps logging to the .1 file.

    Anyone else seeing this?

    Frank
     
  5. iCARus

    iCARus Well-Known Member

    Joined:
    Apr 8, 2003
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    16
    We fixed this this with restarting syslog. After that things are fixed and works ok.

    Regards.
     
  6. ffeingol

    ffeingol Well-Known Member
    PartnerNOC

    Joined:
    Nov 9, 2001
    Messages:
    215
    Likes Received:
    1
    Trophy Points:
    18
    cPanel Access Level:
    DataCenter Provider
    We know that restarting syslogd (actually kill -s HUP PID) "fixes" it. The problem is that the kill command IS in the /etc/logrotate.d/syslog file and it should happen automagically. It's not a CentOS 4.1 issue either becuase we have non-cpanel CentOS 4.1 boxes and it works properly.

    Frank
     
  7. pross

    pross Well-Known Member

    Joined:
    Mar 14, 2005
    Messages:
    75
    Likes Received:
    0
    Trophy Points:
    6
    i have exact same problem centos 4.1 cPanel 10.5.0-C49
     
  8. brentp

    brentp Well-Known Member

    Joined:
    Mar 11, 2004
    Messages:
    324
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Ayr, North Queensland, Australia
    I have a centos 4.1 box and i have had no recent problems with syslogd, and im running edge.

    Regards,
    Brent
     
  9. pross

    pross Well-Known Member

    Joined:
    Mar 14, 2005
    Messages:
    75
    Likes Received:
    0
    Trophy Points:
    6
    i upgraded to edge last week...and noticed today that again they havent rotated..had to restart sysklogd...
     
  10. Rooter

    Rooter Well-Known Member

    Joined:
    Apr 23, 2003
    Messages:
    146
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    Root Administrator
    I am also experiencing this, but on both RHEL4 and CentOS4, both with the latest CURRENT builds of cPanel/WHM. I am still searching for a permanent solution instead of restarting syslogd manually.
     
  11. forlinuxsupport

    forlinuxsupport Well-Known Member
    PartnerNOC

    Joined:
    Dec 22, 2004
    Messages:
    386
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    Root Administrator
    hey all

    Looks like the command in the logrotate fields isnt working like it should.

    if i run that command , then logging into the file /var/log/maillog just stops.

    if i then run /etc/init.d/syslogd restart it willl start logging again.

    very weird..

    cheers
    andy
     
  12. etecc

    etecc Member

    Joined:
    Apr 9, 2003
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    I have a FC2 machine and I also come across this issue about every week. Is there a solution?
     
  13. ffeingol

    ffeingol Well-Known Member
    PartnerNOC

    Joined:
    Nov 9, 2001
    Messages:
    215
    Likes Received:
    1
    Trophy Points:
    18
    cPanel Access Level:
    DataCenter Provider
    At least for us, it was the logrotate program not linking the fact that we have /tmp (and /var/tmp) mounted noexec. We created a dummy /tmp file elsewhere and then added this to /etc/cron.daily/logrotate:

    #!/bin/sh

    TMPDIR=/somewhere/tmp
    export TMPDIR


    /usr/sbin/logrotate /etc/logrotate.conf

    (the 2 bolded lines are the lines added).

    Frank
     
  14. etecc

    etecc Member

    Joined:
    Apr 9, 2003
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Ah; I see. That is most likely the problem (noexec).

    Thank you for the reply.

    - derek
     
  15. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Yup, that's a long standing bug in FC2 which the OS developers said they weren't going to fix shortly after FC2 went EOL.
     
  16. etecc

    etecc Member

    Joined:
    Apr 9, 2003
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Actually that is something we configured. The default is to have /tmp mounted just as any other directory... with no security precautions at all.

    FC2 still has security updates so its not quite End of Life yet.

    - derek

     
  17. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    No, FC2 was EOL at the beginning of this year. Any support for it passed to FedoraLegacy which is not very responsive at all to fixing major bugs or indeed security vulnerabilities. It's the main reason that Fedora is a bad OS to choose for production servers. If you do run Fedora Core ytou should be upgrading your OS at least every 6 months to the latest release.
     
  18. etecc

    etecc Member

    Joined:
    Apr 9, 2003
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    We have our reasons for choosing FC. And our systems are extremely secure, and as up to date as possible.

    But hey, thanks for your opinion chirpy.

    - derek

     
  19. iCARus

    iCARus Well-Known Member

    Joined:
    Apr 8, 2003
    Messages:
    113
    Likes Received:
    0
    Trophy Points:
    16
    Well, is there any fix for that. We have 2 new CentOS 4.2 machines and both dont work with rotating logs. Both machines have postrotate broken.

    Regards.
    iCARus
     
  20. etecc

    etecc Member

    Joined:
    Apr 9, 2003
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Yes, either remount /tmp without noexec. Or setup another noexec tmp dir and have logrotate use that for its logs.
     
Loading...

Share This Page