Patrick, Dan, On Friday 07 January 2005 05:58, Patrick Shanahan wrote:

* Dan [01-07-05 07:48]:

...

I have just noticed a problem with my logs files. Usually they are automatically compressed (gziped) regularly (usually every second day) depending on how large they are. However I have just noticed that they have stopped being compressed, so my logs are HUGE.

Have you modified one of the xxxx.local files under /etc/logdigest reciently (after Nov 23, last observed compression)? If so, there is a problem (or was) with logdigest where it chokes on *extra* empty lines at bottom of the file.

On my 9.1 Pro system, overall log rotation and compression appear to be configured in "/etc/logrotate.conf". Package-specific configuration is configured in files in "/etc/lograte.d". There is no "/etc/logdigest" (either directory or file).

...

Patrick Shanahan

Randall Schulz

The Friday 2005-01-07 at 10:02 -0400, Jorge Fábregas wrote:

The one who compress/rotates logs is the logrotate program which is invoked daily by cron. Make sure you have /etc/cron.daily/logrotate.

Also, check the logrotate config files in /etc/logrotate.d/

And don't forget to check that "cron" itself is running... once I had a system where it stopped suddenly for no known reason. Also, there might be a clue on the /var/log/messages file. -- Cheers, Carlos Robinson

The Monday 2005-01-10 at 12:11 +0100, Dan wrote:

Thanks for all the replies. They have been helpful. I just manually ran

/etc/cron.daily/logrotate and that rotated (compressed) my logs.

So for some funny reason I think that cron has stopped running the above command even though it is in /etc/cron.daily/

Mmmm. Check to see if it is executable; mine has this permissions: -rwxr-xr-x 1 root root 176 2004-04-06 03:26 /etc/cron.daily/logrotate*

Where can I find the instructions for cron to run the cron.daily commands?

My etc/crontab file contains the following commands: 59 * * * * root rm -f /var/spool/cron/lastrun/cron.hourly 14 4 * * * root rm -f /var/spool/cron/lastrun/cron.daily 29 4 * * 6 root rm -f /var/spool/cron/lastrun/cron.weekly 44 4 1 * * root rm -f /var/spool/cron/lastrun/cron.monthly

It should also contain this line before those: -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 The script run-crons is the master one.

I have other commands in crontab that run daily so I know that etc/crontab is running.

Have a look at the logs (/var/log/messages). Also errors in cron are mailed to root.

Sorry for being a newbie ;-)

Please don't :-) -- Cheers, Carlos Robinson

The Wednesday 2005-01-12 at 13:24 +0100, Dan wrote:

I put it back and get errors again in root mailbox. Here is the error:

Subject:Cron root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 Body: /bin/sh: line 1: root: command not found

Any ideas why my master cron script isn't running? I haven't edited it or anything.

Then we need to have a look at the /usr/lib/cron/run-crons file, the first few lines. Mine (SuSE 9.1) goes like this: #!/bin/bash # # /usr/lib/cron/run-crons # # Copyright (c) 1998-2001 SuSE GmbH Nuernberg, Germany. All rights reserved. # # this script looks into /etc/cron.{hourly,daily,weekly,monthly} for # scripts to be executed. The info about last run is stored in # /var/spool/cron/lastrun # Watch that the first line must be comented out, and exactly like that, because althoug it seems a coment, it is interpreted, telling the system what program should interpret the script. (In SuSE systems, /bin/sh is a symlink to bash) and, after a bunch of comments, the script continues like this - for SuSE 9.1, I don't know what you have: # set to "true" to send a mail even if all scripts returned OK SEND_MAIL_ON_NO_ERROR=false BASENAME=`/usr/bin/basename $0` LOGGER="/bin/logger -t $BASENAME[$$]" export LC_TIME=POSIX TMPDIR=`mktemp -d /tmp/run-crons.XXXXXX` trap "rm -rf $TMPDIR" 0 1 2 3 13 15 # Priority change for sub scripts. # If the file is broken, replace it from the original, in cron-...rpm on your dvd or whatever. You do not need to reinstall the rpm completely if you do not want to: you can simply use "mc", [enter] on the rpm file, browse to the script and copy. Midnight Comander, mc for short, is a magnific text based file browser, and much more. It is a Norton Comander for MsDOS look alike. It is very fast, feature full (edit, open/create compressed archives or rpm packages, ftp...), and can be used remotely, even over a modem link. It is text based, but the mouse works, and it has menues. The only thing it doesn't have is graphics :-) If you are sure you did not modify the script yourself (check the timestamp), check your filesystem for errors (fsck from the rescue system). -- Cheers, Carlos Robinson