log files are empty

[iCARus]

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

# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages

# The authpriv file has restricted access.
authpriv.* /var/log/secure

# Log all the mail messages in one place.
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog


# Log cron stuff
cron.* /var/log/cron

# Everybody gets emergency messages
*.emerg *

# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler

# Save boot messages also to boot.log
local7.* /var/log/boot.log

/etc/logrotate.d/syslog

/var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron {
sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true
/etc/rc.d/init.d/antirelayd restart
endscript
}

{

Regards.

[nickb]

what about syslog service..is it running?

[iCARus]

Yes it's runing.

syslogd (pid 2078) is running...
klogd (pid 2082) is running...

[ffeingol]

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

[iCARus]

We fixed this this with restarting syslog. After that things are fixed and works ok.

Regards.

[ffeingol]

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

[pross]

i have exact same problem centos 4.1 cPanel 10.5.0-C49

[brentp]

I have a centos 4.1 box and i have had no recent problems with syslogd, and im running edge.

Regards,
Brent

[pross]

i upgraded to edge last week...and noticed today that again they havent rotated..had to restart sysklogd...

[Rooter]

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.

[forlinuxsupport]

hey all

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

/usr/bin/killall -HUP syslogd

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

[etecc]

I have a FC2 machine and I also come across this issue about every week. Is there a solution?

[ffeingol]

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

[etecc]

Ah; I see. That is most likely the problem (noexec).

Thank you for the reply.

- derek

[chirpy]

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.