Where is rotation policy of logs under /var/log/messages-*

log-fileslog-rotationlogginglogrotate

I would like to know how messages log file /var/log/messages are rotated.

I checked in /etc/logrotate.conf file and inside /etc/logrotate.d/ directory but nothing that could explain the rotation.

Eg: This is a small part of messages file:

Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added datanode[tcp-2:tcp]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added JobHistoryServer[tcp-0:tcp]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added JobHistoryServer[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added JobHistoryServer[http-2:http]-2> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added journalnode[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added journalnode[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added journalnode[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added journalnode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added journalnode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added journalnode[tcp-1:tcp]-1> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added mesos-slave[http-0:http]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added DFSZKFailoverController[tcp-0:tcp]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added DFSZKFailoverController[tcp-0:tcp]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added NodeManager[tcp-0:tcp]-0> to health table
Oct 23 04:03:29 node2 grootd: DEBUG [groot.core.healthcheck.reactor] - added NodeManager[tcp-0:tcp]-0> to health table

Best Answer

Just type
sudo grep messages /etc/logrotate.d/*

On my system this returns
/etc/logrotate.d/rsyslog:/var/log/messages

Related Solutions

Linux – logrotate does not compress /var/log/messages

Adding delaycompress to the configuration section for /var/log/messages solved the problem.

From man logrotate:

   delaycompress
          Postpone  compression of the previous log file to the next rota‐
          tion cycle.  This only has effect when used in combination  with
          compress.   It  can  be used when some program cannot be told to
          close its logfile and thus might continue writing to the  previ‐
          ous log file for some time.

I guess sysklogd, my syslog daemon, cannot be told to close its logfile, and thus this is necessary.

Interestingly, the original configuration I had (without the delaycompress directive), came straight out of man logrotate (except I changed weekly to daily):

   # sample logrotate configuration file
   compress

   /var/log/messages {
       rotate 5
       weekly
       postrotate
           /usr/bin/killall -HUP syslogd
       endscript
   }

Centos – Logrotate Mysql – No rotate happens

Threre is no rotation, because you are using -d option. From manual:

-d Turns on debug mode and implies -v. In debug mode, no changes will be made to the logs or to the logrotate state file.

I have two suggestions:

Upgrade OS to x86_64 if possible, because you have 2,5GB memory limit per process
Don't use -pPassword parameter with mysql for security reasons, it's better to use --defaults-extra-file=path_to_extra, which is readable only by root. When somebody, who has access to server execute ps -ef | grep mysql, it will see root password for database.

Here is my logrotate /etc/logrotate.d/mysql script for mysql on CentOS 5 (mysql Ver 14.12 Distrib 5.0.77, for redhat-linux-gnu (x86_64) using readline 5.1):

# If the root user has a password you have to create a
# /.my.cnf configuration file with the following
# content:
#
# [mysqladmin]
# password = <secret>
# user = <username>
#
# where "<secret>" is the password and <username> is user.
#
# ATTENTION: This /.my.cnf should be readable ONLY
# for root !
/var/log/mysqld.log {
        create 640 mysql mysql
        notifempty
        missingok
        postrotate
                # just if mysqld is really running
                if test -x /usr/bin/mysqladmin && \
                   /usr/bin/mysqladmin --defaults-extra-file=/root/mysql/logrotate.cnf ping &>/dev/null
                then
                   /usr/bin/mysqladmin --defaults-extra-file=/root/mysql/logrotate.cnf flush-logs
                fi
                /usr/bin/chcon -u system_u -r object_r -t mysqld_log_t /var/log/mysqld.log
        endscript
}

Best Answer

Related Solutions

Linux – logrotate does not compress /var/log/messages

Centos – Logrotate Mysql – No rotate happens

Related Topic