1 |
On Sunday 12 Feb 2017 19:11:23 Alexander Kapshuk wrote: |
2 |
> On Sun, Feb 12, 2017 at 6:57 PM, Mick <michaelkintzios@×××××.com> wrote: |
3 |
> > I am perplexed why box of mine will not logrotate system logs, which have |
4 |
> > now grown into gigs. kern.log, syslog, messages, etc. are eating up |
5 |
> > space unconstrained, to the point where the partition run out of it. |
6 |
> > |
7 |
> > Trying to run /etc/cron.daily/logrotate from a terminal does not show |
8 |
> > anything in messages, or syslog. |
9 |
> > |
10 |
> > Particulars below: |
11 |
> > |
12 |
> > # ls -la /etc/cron.daily/logrotate |
13 |
> > -rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate |
14 |
> > |
15 |
> > |
16 |
> > # cat /etc/cron.daily/logrotate |
17 |
> > #!/bin/sh |
18 |
> > |
19 |
> > /usr/bin/logrotate /etc/logrotate.conf |
20 |
> > EXITVALUE=$? |
21 |
> > if [ $EXITVALUE != 0 ]; then |
22 |
> > |
23 |
> > /usr/bin/logger -t logrotate "ALERT exited abnormally with |
24 |
> > [$EXITVALUE]" |
25 |
> > |
26 |
> > fi |
27 |
> > exit 0 |
28 |
> > |
29 |
> > |
30 |
> > This is an installation I have not really changed much from default |
31 |
> > settings. Comparing with other systems which work as expected I can't see |
32 |
> > anything amiss. How could I troubleshoot/fix this problem? |
33 |
> > |
34 |
> > -- |
35 |
> > Regards, |
36 |
> > Mick |
37 |
> |
38 |
> I had a similar problem a while back, and Alex Corkwell suggested |
39 |
> removing the executable bit on /etc/cron.hourly/0anacron, which did |
40 |
> the trick for me. |
41 |
> |
42 |
> See gentoo-user archives for an email exchange with 'portage summary |
43 |
> logs not rotated any more' as the subject for full details. |
44 |
> |
45 |
> Hope this helps. |
46 |
|
47 |
Thanks Alexander, it pays going back to basics ... for some reason my cronie |
48 |
service was not running. o_O |
49 |
|
50 |
I added it to default runlevel and hopefully it will do its magic from now on. |
51 |
-- |
52 |
Regards, |
53 |
Mick |