thanks for your reply. i'm well aware of the fact that this suse verion is really too old, but as we're having a major upgrade round in half a year, i want to wait until then. and, besides that: it has always been running perfectly, so why change a winning team..? (apache is upgraded to the latest version, btw...) anyway: thanks for you suggestions, but they did not solve the problem. any other suggestions? (otherwise, i guess that maybe i should manually compress the files then every now and then.) thanks for having taken the time to reply. yours, mourik jan
-----Original Message----- From: Togan Muftuoglu [mailto:toganm@dinamizm.com] Sent: Monday, November 25, 2002 11:06 To: suse-linux-e@suse.com Subject: Re: [SLE] REPOST: log rotate suse 6.2 stopped working
* Heupink, Mourik Jan C.;
on 25 Nov, 2002 wrote: I have posted this same question last week, and did not get any responses. I wonder if i missed something really obvious that nobody cares to share with me, or if really nobody knows the answer, or has any ideas how to solve this issue...
IMHO the SuSE version you are using far too old and hence no response
yet, it does not compress. Even when I run the /etc/cron.daily/aaa_base by hand, it does not display any errors, yet the file has not been compressed. root also doesn't get any messages from the script. though it does seem to be running for a while, and the system is quite buzy, while the script runs.
What could be wrong? Any ideas?
Two options
a) add a "-x" parameter to aaa_base and capture the output to a file so you can have a look what is going on
b) restart cron and see if it does work
--
Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
HMJC> anyway: thanks for you suggestions, but they did not solve the problem. any HMJC> other suggestions? (otherwise, i guess that maybe i should manually compress HMJC> the files then every now and then.) I've never had the version of SuSE you are running, but I checked some things on my system. Maybe some of these thoughts will help (and maybe not) :-o First thing, can you recall if you changed anything on your system? I don't know if this is it, I'm just throwing it out there, as is --- I had the recent experience of MySQL and logrotate and having changed roots password. There was a hidden, read only, file in the root home that contained the pwd. Argh! I got an email with an error message. I forward all roots mail to another id than root. Does logrotate have a configuration file, you might want to view it to see if there is anything in there that might indicate what is wrong? Next, is there a man page for your logrotate? There is on my 8.1 system and there is a debug option. You mentioned running your script outside of cron. I don't recall reading if you used this option. You might want to read the man page to see if there is a similar option and try it to get some diagnostics. This might help you figure out what is going on. Good Luck. -- __________________________ DJ mailto: linux_programmer@hotmail.com
The 02.11.26 at 11:50, Heupink, Mourik Jan C. wrote:
From: "Heupink, Mourik Jan C."
Reply-To: suse-linux-e@suse.com To: 'Togan Muftuoglu' , suse-linux-e@suse.com
[...]
anyway: thanks for you suggestions, but they did not solve the problem. any other suggestions? (otherwise, i guess that maybe i should manually compress the files then every now and then.)
Inserting -x at the top of the script will not solve the problem: you have to manually run the script and find out yourself what is going wrong. It is a debug option. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R.
-
DJ
-
Heupink, Mourik Jan C.