Ежедневно получаю уведомления от cron, что logrotate не смог упаковать логи munin и mysql. Попробовал поставить su в соответствующие файлы /etc/logrotate.d, но это результатов не дало. Может дать логам root? Как это отразится на работе munin и mysql? Надо что-то сделать пока логи не забили весь диск)
Сообщение от cron:
/etc/cron.daily/logrotate:
error: munin:2 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-cgi-graph.log , skipping
error: munin:11 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-cgi-html.log , skipping
error: munin:20 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-graph.log , skipping
error: munin:29 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-html.log , skipping
error: munin:38 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-limits.log , skipping
error: munin:47 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-update.log , skipping
error: mysql:2 unknown user 'mysql:mysql'
error: found error in /var/log/mysql/*.log
, skipping
error: skipping "/var/log/munin-node/munin-node.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: skipping "/var/log/mysql/error.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: skipping "/var/log/mysql/slow.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.
И ещё вопрос про cron. Приходит оповещение от /opt/webdir/bin/bx_backup.sh
2020/06/14 06:14:28 24336 Delete sql file=/home/bitrix/mysql_dump_sitemanager_14.06.2020_XK53LVwB.sql
2020/06/14 06:14:28 24336 Delete sql file=/home/bitrix/mysql_dump_sitemanager_14.06.2020_XK53LVwB_after_connect.sql
Я так понял это нормально, просто после упаковки удаляются не нужные дампы баз. Я прав?
Сообщение от cron:
/etc/cron.daily/logrotate:
error: munin:2 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-cgi-graph.log , skipping
error: munin:11 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-cgi-html.log , skipping
error: munin:20 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-graph.log , skipping
error: munin:29 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-html.log , skipping
error: munin:38 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-limits.log , skipping
error: munin:47 unknown user 'munin:bitrix'
error: found error in /var/log/munin/munin-update.log , skipping
error: mysql:2 unknown user 'mysql:mysql'
error: found error in /var/log/mysql/*.log
, skipping
error: skipping "/var/log/munin-node/munin-node.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: skipping "/var/log/mysql/error.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: skipping "/var/log/mysql/slow.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.
И ещё вопрос про cron. Приходит оповещение от /opt/webdir/bin/bx_backup.sh
2020/06/14 06:14:28 24336 Delete sql file=/home/bitrix/mysql_dump_sitemanager_14.06.2020_XK53LVwB.sql
2020/06/14 06:14:28 24336 Delete sql file=/home/bitrix/mysql_dump_sitemanager_14.06.2020_XK53LVwB_after_connect.sql
Я так понял это нормально, просто после упаковки удаляются не нужные дампы баз. Я прав?