Re: [gentoo-user] logrotate ... won't!
On Sun, 12 Feb 2017 21:26:51 -0600, Dale wrote: > >> Thanks Alexander, it pays going back to basics ... for some reason my > >> cronie service was not running. o_O > >> > >> I added it to default runlevel and hopefully it will do its magic > >> from now on. > > I'm glad I'm not the only one prone to this kind of thing. :( > > > > You're not. ;-) You're part of a large group of people that make such mistakes and a much smaller group of those that admit to them ;-) -- Neil Bothwick One-seventh of life is spent on Monday. pgpYV2FrAIoHU.pgp Description: OpenPGP digital signature
Re: [gentoo-user] logrotate ... won't!
Peter Humphrey wrote: > On Sunday 12 Feb 2017 17:32:30 Mick wrote: > >> Thanks Alexander, it pays going back to basics ... for some reason my >> cronie service was not running. o_O >> >> I added it to default runlevel and hopefully it will do its magic from now >> on. > I'm glad I'm not the only one prone to this kind of thing. :( > You're not. ;-) Dale :-) :-)
Re: [gentoo-user] logrotate ... won't!
On Sunday 12 Feb 2017 17:32:30 Mick wrote: > Thanks Alexander, it pays going back to basics ... for some reason my > cronie service was not running. o_O > > I added it to default runlevel and hopefully it will do its magic from now > on. I'm glad I'm not the only one prone to this kind of thing. :( -- Regards Peter
Re: [gentoo-user] logrotate ... won't!
On Sunday 12 Feb 2017 19:11:23 Alexander Kapshuk wrote: > On Sun, Feb 12, 2017 at 6:57 PM, Mick wrote: > > I am perplexed why box of mine will not logrotate system logs, which have > > now grown into gigs. kern.log, syslog, messages, etc. are eating up > > space unconstrained, to the point where the partition run out of it. > > > > Trying to run /etc/cron.daily/logrotate from a terminal does not show > > anything in messages, or syslog. > > > > Particulars below: > > > > # ls -la /etc/cron.daily/logrotate > > -rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate > > > > > > # cat /etc/cron.daily/logrotate > > #!/bin/sh > > > > /usr/bin/logrotate /etc/logrotate.conf > > EXITVALUE=$? > > if [ $EXITVALUE != 0 ]; then > > > > /usr/bin/logger -t logrotate "ALERT exited abnormally with > > [$EXITVALUE]" > > > > fi > > exit 0 > > > > > > This is an installation I have not really changed much from default > > settings. Comparing with other systems which work as expected I can't see > > anything amiss. How could I troubleshoot/fix this problem? > > > > -- > > Regards, > > Mick > > I had a similar problem a while back, and Alex Corkwell suggested > removing the executable bit on /etc/cron.hourly/0anacron, which did > the trick for me. > > See gentoo-user archives for an email exchange with 'portage summary > logs not rotated any more' as the subject for full details. > > Hope this helps. Thanks Alexander, it pays going back to basics ... for some reason my cronie service was not running. o_O I added it to default runlevel and hopefully it will do its magic from now on. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] logrotate ... won't!
On Sun, Feb 12, 2017 at 6:57 PM, Mick wrote: > I am perplexed why box of mine will not logrotate system logs, which have now > grown into gigs. kern.log, syslog, messages, etc. are eating up space > unconstrained, to the point where the partition run out of it. > > Trying to run /etc/cron.daily/logrotate from a terminal does not show anything > in messages, or syslog. > > Particulars below: > > # ls -la /etc/cron.daily/logrotate > -rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate > > > # cat /etc/cron.daily/logrotate > #!/bin/sh > > /usr/bin/logrotate /etc/logrotate.conf > EXITVALUE=$? > if [ $EXITVALUE != 0 ]; then > /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" > fi > exit 0 > > > This is an installation I have not really changed much from default settings. > Comparing with other systems which work as expected I can't see anything > amiss. How could I troubleshoot/fix this problem? > > -- > Regards, > Mick I had a similar problem a while back, and Alex Corkwell suggested removing the executable bit on /etc/cron.hourly/0anacron, which did the trick for me. See gentoo-user archives for an email exchange with 'portage summary logs not rotated any more' as the subject for full details. Hope this helps.
[gentoo-user] logrotate ... won't!
I am perplexed why box of mine will not logrotate system logs, which have now grown into gigs. kern.log, syslog, messages, etc. are eating up space unconstrained, to the point where the partition run out of it. Trying to run /etc/cron.daily/logrotate from a terminal does not show anything in messages, or syslog. Particulars below: # ls -la /etc/cron.daily/logrotate -rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate # cat /etc/cron.daily/logrotate #!/bin/sh /usr/bin/logrotate /etc/logrotate.conf EXITVALUE=$? if [ $EXITVALUE != 0 ]; then /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" fi exit 0 This is an installation I have not really changed much from default settings. Comparing with other systems which work as expected I can't see anything amiss. How could I troubleshoot/fix this problem? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] logrotate won't rotate portage logs
Hi All,
I do not understand why the log files within /var/log/portage/ will
not rotate on my PC, while they rotate fine on my laptop. The
/etc/logrotate.conf is the same on both boxen:
==
# rotate log files weekly
weekly
#daily
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
compress
# packages can drop log rotation information into this directory
include /etc/logrotate.d
notifempty
nomail
noolddir
[snip . . . ]
# when /var/log/portage gets big
/var/log/portage/*.log
{
rotate 1
weekly
nocreate
ifempty
olddir /var/log/portage/old
postrotate
find /var/log/portage/old -maxdepth 1 -mtime +30 -exec /bin/rm -f {} \;
endscript
nocompress
}
==
The only difference I noticed (other than the fact that I have two
year old portage log files in /var/log/portage) between the two boxen
is that the access rights of the 'old' directory on the PC were:
drwxr-sr-x 2 rootroot 48 Dec 23 2005 old
while on the laptop which rotates without problems are:
drwx-- 2 rootroot 4256 Jan 13 11:20 old
This may be a bit of a red herring because even though I changed the
access rights as per the laptop, the PC still refuses to rotate the
portage log files.
Any ideas? How do I troubleshoot this one?
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
