Error Setting Owner Of /var/log/portage/elog/summary.log
error setting owner of /var/log/portage/elog/summary.log-20110809.gz: Operation not permitted as you can see # cat /etc/logrotate.d/elog-save-summary # Copyright 1999-2011 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # Rotate the log created by the save_summary elog module. /var/log/portage/elog/summary.log { su portage portage missingok nocreate delaycompress } and # ll /var/log/portage/elog/summary.log-20110809 -rw-rw-r-- 1 root portage 1280 Aug 8 09:29 /var/log/portage/elog/summary.log-20110809 owner of file is root and logrotate use portage user, so it can can't rotate this file the solution of this problem is: change files owner: chown portage /var/log/portage/elog/summary.log-20110809 Posted by Володя at Monday, October 31, 2011 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: gentoo Reactions: No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Total Pageviews Tags apache (12) backup (1) bash (2) bind (1) cd (2) cdrecord (2) centos (1) contol panel (1) cron (1) crypt (1) database (2) ddos (6) django (2) dns (3) dvd (2) eth (1) exim (1) fail2ban (1) fax (1) filesystem (1) firewall (1) flask (1) FreeBSD (2) ftp (6) gentoo (8) gimp (1) gnugp (1) grub (1) gunicorn (1) html (1) http (1) imap (1) internet (1) iptables (1) javascript (1) linux (6) locale (1) lxc (1) mail (1) mongo (1) monitor (4) munin (3) mysql (15) nagios (7) named (1) nginx (16) nmap (1) openssl (1) opensuse (1) opera (2) optimization (3) performance (1) perl (1) pf (1) php (8) php. lamp (1) postgresql (1) programming (2) proxy (1) python (4) raid (2) rsync (1) samba (1) security (5) sms (1) sqlite (1) squid proxy (3) ssh (3) ssl (3) sudo (1) supervisor (1) svn (3) syslog (1) tcp (1) tips_tricks (2) trabble (1) trac (1) traffic (1) tshark (1) tuning (1) ubuntu (6) update (1) vim (1) virtualbox (1) virtuali
Message-ID: 4E5B9740.8050904 () binarywings ! net [Download message RAW] Am 28.08.2011 20:44, schrieb Florian Philipp: > Am 28.08.2011 13:14, schrieb Mick: >> On Sunday 07 Aug 2011 16:20:18 Florian Philipp wrote: >>> Am 07.08.2011 02:22, schrieb Mick: >>>> On Friday 05 Aug 2011 23:08:38 Neil Bothwick wrote: >>>>> On Fri, 05 Aug 2011 17:59:00 +0200, Florian Philipp wrote: >>>>>> Yes, this was introduced in 3.8.0 to fix http://vova-zms.blogspot.com/2011/10/error-error-setting-owner-of.html security issues [1]. Change >>>>>> your config to look like this: >>>>>> /var/log/portage/elog/summary.log { >>>>>> su portage portage >>>>>> ... >>>>>> } >>>>>> >>>>>> Disclaimer: I've not really tried this (yet) but I think I'm able to >>>>>> read changelogs and man-pages. ;-) >>>>> >>>>> Yes that fixes it. https://marc.info/?l=gentoo-user&m=131462544914601 The latest portage ebuilds include an updated config >>>>> file. >>>> >>>> Hmm ... it still complains here! >>>> >>>> error: error setting owner of >>>> /var/log/portage/elog/summary.log-20110801.gz: Operation not permitted >>>> >>>> >>>> This is my /etc/logrotate.d/elog-save-summary: >>>> =================================== >>>> /var/log/portage/elog/summary.log { >>>> >>>> su portage portage >>>> >>>> missingok >>>> nocreate >>>> delaycompress >>>> >>>> } >>>> =================================== >>>> >>>> # ls -la /var/log/portage/elog/summary.log >>>> -rw-rw-r-- 1 root portage 4326 Aug 6 09:44 >>>> /var/log/portage/elog/summary.log >>>> >>>> Can you see anything amiss? >>> >>> At least on my system, /var/log/portage has the following permissions: >>> drwxr-xr-x root root >>> >>> Only root can write, therefore the config must read >>> >>> /var/log/portage/elog/summary.log { >>> su root portage >>> missingok >>> nocreate >>> delaycompress >>> } >> >> The latest logrotate update wanted to change the above line from su root >> portage to su po
20120625235610.1a725d9d () khumba ! net [Download message RAW] On Mon, 25 Jun 2012 18:20:22 -0400 Michael Mol
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top logrotate doesn't work for munin after last update on OpenSUSE 11.4 up vote 5 down vote favorite I'm using munin 1.4.5 on OpenSUSE 11.4. Lately logrotate was updated to fix some permission problems and after that complained with Mar 3 12:15:05 lucien logrotate: error: "/var/log/munin" has insecure permissions. It must be owned and be writable by root only to avoid security problems. Set the "su" directive in the config file to tell logrotate which user/group should be used for rotation. Mar 3 12:15:05 lucien logrotate: error: error reading /var/log/munin/munin-html.log: Bad file descriptor Mar 3 12:15:05 lucien logrotate: error: error reading /var/log/munin/munin-limits.log: Bad file descriptor Mar 3 12:15:05 lucien logrotate: error: error reading /var/log/munin/munin-update.log: Bad file descriptor Mar 3 12:15:05 lucien logrotate: error: error reading /var/log/munin/munin-graph.log: Bad file descriptor Mar 3 12:15:05 lucien logrotate: error: error reading /var/log/munin/munin-node.log: Bad file descriptor So I addded su directives to /etc/logrotate.d/munin and /etc/logrotate.d/munin-node: /var/log/munin/munin-html.log /var/log/munin/munin-nagios.log /var/log/munin/munin-limits.log /var/log/munin/munin-update.log { su munin munin daily missingok rotate 7 compress copytruncate notifempty create 640 munin munin } /var/log/munin/munin-graph.log { su munin www daily missingok rotate 7 compress copytruncate notifempty create 660 munin www } /var/log/m