troff
08-24-2004, 04:33 AM
My Raq was behaving very slow and sick past 2 weeks (web, database and admin slow or inaccessible - thank god SSH was still up)
Finally I went in and did a top and found that the command 'klogd' was taking up 97.4% of the CPU!
I've read this in other posts but all have no resolution or solutions...
The only solution I've read is to have a cron job to restart the Raq every night at 3.00am but I don't think this is the correct way to deal with this...
Anyone want to have a shot at this?
Finally I went in and did a top and found that the command 'klogd' was taking up 97.4% of the CPU!
I've read this in other posts but all have no resolution or solutions...
The only solution I've read is to have a cron job to restart the Raq every night at 3.00am but I don't think this is the correct way to deal with this...
Anyone want to have a shot at this?
