Topic: 4 am what is going on.

[ephraims]

I have found that all of a sudden my computer processor is taking forever to run jobs at 4am. It used to only take about .5 to 1 hour to run the /etc/cron.daily jobs now it is taking hours only of a few days ago and it is hindering other jobs. Does anybody have any ideas. The jobs in my cron.daily are Dancron, clean.problems, clean.quarantine, logorate, makewhatis.con, rpm, run_usa, clocate.cron, supdate.cron, tmpwatch, tmpwatch-formmagic. How do i know wich of these are doing it and how do i stop or slow down the process.
Thanks for your help Jason

[ephraims]

i have found that the problem is with the logrotate. this process starts at 4 am and gets stuck on what i do not know. does anybody have any ideas on how to trouble shoot this problem

[ephraims]

I have found that if i try to logroate anything in /etc/logrotate.d logrotate gets stuck. the command i use is logrotate -d --force amavis-ng and it sticks the same thing happens with any files in the directory as soon as i run the command the processor goes to 100 percent and stays there. I ran this command on another machine not as fast and bang finished in 2 sec. How do i fix logrotate program

[thecat]

Please if you sort this problem outside these forums can you report back here? As I am having the exact same drama

[ephraims]

/var/lib/logrotate.status
This file had gotten very big i mean like 19mb big causing logrotate to use up the processor. i moved the file to a diffrent location ran logrotate and all good. I will monitor this file to see if it continues to grow. My other server only has a small logrotate file and it has been up longer than this server. If anybody has any other suggestion please post.

[ephraims]

i moved the file by - mv /var/lib/logrotate.status /home/e-smith/files/ibays/(Ibayname)/files
I suppose i could have just deleted the file but i prefer to move and see if i need it later

[RavenIV]

my file "/var/lib/logrotate.status" is 400 byte in size and i found nothing spectacular in it.
i think this is normal.

any idea why your file is so big?

cheers