Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-13-2002, 01:31 PM
|
#1
|
Member
Registered: Aug 2001
Distribution: Debian Etch
Posts: 510
Rep:
|
Need help with logrotate process eating 99.9% CPU
logrotate process on my server is taking 99.9% CPU time.
This is a bugzilla server with redhat 7.2. It had an uptime of 109 days until I rebooted it yesterday because of this logrotate problem.
But I came in this morning and it's happening again. I looked in my /var/logs and there are alot of big logs and lots of log files.
I don't know how to fix this logrotate problem, can anyone help? Thanks.
|
|
|
11-13-2002, 02:31 PM
|
#2
|
Moderator
Registered: May 2001
Posts: 29,417
|
Not to cramp your style but since you've got +300 posts you'd know by now you should provide more info than "I've got error X". I'm thinking what's running (under logrotate), what part exactly was sucking up CPU at the reboot moment, what big logs and do they hold any clue to the cron-driven processes.
The Logrotate cronscript only is executing stuff there's a script for in /etc/logrotate.d. Let it run in verbose mode and check those scripts and the logs.
|
|
|
11-13-2002, 02:35 PM
|
#3
|
Member
Registered: Aug 2001
Distribution: Debian Etch
Posts: 510
Original Poster
Rep:
|
Quote:
Not to cramp your style but since you've got +300 posts you'd know by now you should provide more info than "I've got error X".
|
Excuse me, I believe that I did provide more information than "I've got error X".
|
|
|
11-13-2002, 04:07 PM
|
#4
|
Moderator
Registered: May 2001
Posts: 29,417
|
Plz *do* look further than the first line
|
|
|
11-14-2002, 11:57 AM
|
#5
|
Member
Registered: Aug 2001
Distribution: Debian Etch
Posts: 510
Original Poster
Rep:
|
unSpawn, what's with your attitude? I don't come here to be berated.
You seriously need to ease up.
|
|
|
12-30-2002, 08:02 PM
|
#6
|
LQ Newbie
Registered: Oct 2002
Location: New Jersey
Distribution: Red Hat 8.0
Posts: 20
Rep:
|
I had the same problem and someone figured out the solution. It was the 'mailman' process. Check out the end of this thread for more info...
http://www.linuxquestions.org/questi...threadid=34695
Once I removed 'mailman' from my system, and removed the /var/logs/mailman directory, this same problem stopped for me.
|
|
|
All times are GMT -5. The time now is 03:10 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|