Ругается /etc/cron.daily/exim4-base. Что может быть и как это исправить?

Question

[Евгений Зотов]

ОС: Debian 8
Ошибка:

/etc/cron.daily/exim4-base:
LOG: MAIN
  Warning: purging the environment.
 Suggested action: use keep_environment.
/etc/cron.daily/logrotate:
error: skipping "/var/log/iptraf/ip_traffic-1.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log /var/log/mysql/error.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

Comments

[t_q_l]

Что может быть: это может быть неверно выставленные права на директорию с логами

Как это исправить: выставить права на директорию с логами

[Евгений Зотов]

t_q_l, А какие права должны стоять и путь к логу можно?

[t_q_l]

Zhenya_Zotov, боюсь, что нет. Все пути и логи находятся на вашей стороне.
Могу лишь порекомендовать посмотреть в /etc/cron.daily/exim4-base.

Заодно посмотрите, какие права стоят на директорию /var/log/iptraf/

[Galdar Turin]

Zhenya_Zotov, в самой ошибке есть путь к логу

[Евгений Зотов]

t_q_l , права на директори. /var/log/iptraf/ 777

Содержимое файла

#!/bin/sh

if [ -n "$EX4DEBUG" ]; then
  echo "now debugging $0 $@"
  set -x
fi


# set this to some other value if you don't want the panic log to be
# watched by this script, for example when you're using your own log
# checking mechanisms or don't care.

E4BCD_DAILY_REPORT_TO=""
E4BCD_DAILY_REPORT_OPTIONS=""
E4BCD_WATCH_PANICLOG="yes"
# Number of lines of paniclog quoted in warning email.
E4BCD_PANICLOG_LINES="10"
E4BCD_PANICLOG_NOISE=""

# Only do anything if exim4 is actually installed
if [ ! -x /usr/lib/exim4/exim4 ]; then
  exit 0
fi

[ -f /etc/default/exim4 ] && . /etc/default/exim4

SPOOLDIR="$(exim4 -bP spool_directory | sed 's/.*=[[:space:]]\(.*\)/\1/')"

# The log processing code used in this cron script is not very
# sophisticated. It relies on this cron job being executed earlier than
# the log rotation job, and will have false results if the log is not
# rotated exactly once daily in the daily cron processing. Even in the
# default configuration, it will ignore log entries made between this
# cron job and the log rotation job.

# Patches for more sophisticated processing are appreciated via the
# Debian BTS.

E4BCD_MAINLOG_NOISE="^[[:digit:][:space:]:-]\{20\}\(\(Start\|End\) queue run: pid=[[:digit:]]\+\|exim [[:digit:]\.]\+ daemon started: pid=[[:digit:]]\+, .*\)$"

if [ -n "$E4BCD_DAILY_REPORT_TO" ]; then
  if [ -x "$(command -v eximstats)" ] && [ -x "$(command -v mail)" ]; then
    if [ "$(< /var/log/exim4/mainlog grep -v "$E4BCD_MAINLOG_NOISE" | wc -l)" -gt "0" ]; then
      < /var/log/exim4/mainlog grep -v "$E4BCD_MAINLOG_NOISE" \
                | eximstats $E4BCD_DAILY_REPORT_OPTIONS \
                | mail -s"$(hostname --fqdn) Daily e-mail activity report" \
		    $E4BCD_DAILY_REPORT_TO
    else
      echo "no mail activity in this interval" \
                | mail -s"$(hostname --fqdn) Daily e-mail activity report" \
		    $E4BCD_DAILY_REPORT_TO
    fi
  else
    echo "The exim4 cron job is configured to send a daily report, but eximstats"
    echo "and/or mail cannot be found. Please check and make sure that these two"
    echo "binaries are available"
  fi
fi

log_this() {
  TEXT="$@"
  if ! logger -t exim4 -p mail.alert $TEXT; then
    RET="$?"
    echo >&2 "ALERT: could not syslog $TEXT, logger return value $RET"
  fi
}

if [ "$E4BCD_WATCH_PANICLOG" != "no" ]; then
  if [ -s "/var/log/exim4/paniclog" ]; then
    if [ -x "/usr/local/lib/exim4/nonzero_paniclog_hook" ]; then
      /usr/local/lib/exim4/nonzero_paniclog_hook
    fi
    if [ -z "$E4BCD_PANICLOG_NOISE" ] || grep -vq "$E4BCD_PANICLOG_NOISE" /var/log/exim4/paniclog; then
      log_this "ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly broken"
      if ! printf "Subject: exim paniclog on %s has non-zero size\nTo: root\n\nexim paniclog /var/log/exim4/paniclog on %s has non-zero size, mail system might be broken. The last ${E4BCD_PANICLOG_LINES} lines are quoted below.\n\n%s\n" \
      "$(hostname --fqdn)" "$(hostname --fqdn)" \
      "$(tail -n "${E4BCD_PANICLOG_LINES}" /var/log/exim4/paniclog)" \
      | exim4 root; then
        log_this "PANIC: sending out e-mail warning has failed, exim has non-zero return code"
      fi
      if [ "$E4BCD_WATCH_PANICLOG" = "once" ]; then
        logrotate -f /etc/logrotate.d/exim4-paniclog
      fi
    fi
  fi
fi

# run tidydb as Debian-exim:Debian-exim.
if [ -x /usr/sbin/exim_tidydb ]; then
  cd $SPOOLDIR/db || exit 1
  if ! find $SPOOLDIR/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' \
    -or -type f -printf '%f\0' | \
      xargs -0r -n 1 \
      start-stop-daemon --start --exec /usr/sbin/exim_tidydb \
      --chuid Debian-exim:Debian-exim -- $SPOOLDIR > /dev/null; then
    # if we reach this, invoking exim_tidydb from start-stop-daemon has
    # failed, most probably because of libpam-tmpdir being in use
    # (see #373786 and #376165)
    find $SPOOLDIR/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' \
    -or -type f -printf '%f\0' | \
    su - --shell /bin/bash \
         --command "xargs -0r -n 1 /usr/sbin/exim_tidydb $SPOOLDIR > /dev/null" \
         Debian-exim
  fi
fi

[t_q_l]

Евгений Зотов
chown -R Debian-exim /var/log/iptraf/

[Евгений Зотов]

t_q_l, сделал, права остались 777

[t_q_l]

Евгений Зотов, разумеется, только владелец теперь другой - Debian-exim

[Евгений Зотов]

ls -l /var/log/ | grep iptraf:

drwxrwxrwx 2 root        root        4096 мар 19 06:25 iptraf

ls -l /var/log/iptraf

-rwxrwxrwx 1 root root     0 мар 19 06:25 ip_traffic-1.log
-rwxrwxrwx 1 root root 11905 мар 18 08:21 ip_traffic-1.log.1.gz
-rwxrwxrwx 1 root root 20622 янв  2  2019 ip_traffic-1.log.2.gz
-rwxrwxrwx 1 root root 27501 дек 29  2018 ip_traffic-1.log.3.gz
-rwxrwxrwx 1 root root  5663 дек 10  2018 ip_traffic-1.log.4.gz
-rwxrwxrwx 1 root root  5889 ноя 29  2018 ip_traffic-1.log.5.gz
-rwxrwxrwx 1 root root  2180 ноя  1  2018 ip_traffic-1.log.6.gz
-rwxrwxrwx 1 root root  8721 окт 23  2018 ip_traffic-1.log.7.gz

[Valentin Barbolin]

Ну как бы вот и ответ
drwxrwxrwx 2 root root 4096 мар 19 06:25 iptraf

Все могу писать в эту папку.

sudo chmod 770 -R /var/log/iptraf - должно помочь.

[Евгений Зотов]

Andrey Barbolin, t_q_l, не помогло. И то и то

[Valentin Barbolin]

Евгений Зотов, Ошибка та же? У вас в вопросе изначально 2 ошибки.

[Евгений Зотов]

/etc/cron.daily/exim4-base:
LOG: MAIN
  Warning: purging the environment.
 Suggested action: use keep_environment.
/etc/cron.daily/logrotate:
error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log /var/log/mysql/error.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

@dronmaxman,

[Евгений Зотов]

Andrey Barbolin,

/etc/cron.daily/exim4-base:
LOG: MAIN
  Warning: purging the environment.
 Suggested action: use keep_environment.
/etc/cron.daily/logrotate:
error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log /var/log/mysql/error.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

[Valentin Barbolin]

Евгений Зотов, ну так, на одну ошибку меньше. Осталась ошибка с sql.

Эта проблема по сложнее, похоже на незавершенную процедуру обновления sql сервера.

https://www.whitebyte.info/general/how-to-fix-logr...

logrotate после ротации должен сделать reload в sql, у него это не получается по какой-то причине, предполагаю, что пароль для доступа к базе устарел (/etc/mysql/debian.cnf ).