Re: Frenzying disk activity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 28 Jul 2004, Alexander Apprich wrote:

> If you know the time when this happens, check /var/log/messages to see
> if the application(s) did some logging.

These are the kernel messages from today's frenzy. There are similar
records for the other days too:

Jul 27 19:34:13 localhost kernel: tg3: eth0: Link is down.
Jul 28 05:51:41 localhost kernel: eth0: no IPv6 routers present
Jul 28 06:53:34 localhost kernel: Out of Memory: Killed process 3771
(kdeinit).
Jul 28 07:01:33 localhost kernel: Out of Memory: Killed process 3784
(kdeinit).
Jul 28 07:12:16 localhost kernel: Out of Memory: Killed process 3781
(kdeinit).
Jul 28 07:21:21 localhost kernel: Out of Memory: Killed process 3775
(kdeinit).
Jul 28 07:25:24 localhost kernel: Out of Memory: Killed process 5138
(kdesktop_lock).
Jul 28 07:30:47 localhost kernel: Out of Memory: Killed process 3756
(kdeinit).
Jul 28 07:32:03 localhost kernel: Out of Memory: Killed process 3777
(kdeinit).
Jul 28 07:36:08 localhost kernel: Out of Memory: Killed process 3780
(kdeinit).
Jul 28 07:40:20 localhost kernel: Out of Memory: Killed process 3774
(kdeinit).
Jul 28 07:44:27 localhost kernel: Out of Memory: Killed process 3785
(kdeinit).
Jul 28 07:47:21 localhost kernel: Out of Memory: Killed process 3754
(kdeinit).
Jul 28 07:50:05 localhost kernel: Out of Memory: Killed process 3751
(kdeinit).
Jul 28 07:51:45 localhost kernel: Out of Memory: Killed process 3794
(gaim).
Jul 28 07:54:31 localhost kernel: Out of Memory: Killed process 3793
(eggcups).
Jul 28 07:56:47 localhost kernel: Out of Memory: Killed process 7816
(xscreensaver-ge).
Jul 28 08:00:40 localhost kernel: Out of Memory: Killed process 3759
(kdeinit).
Jul 28 08:03:10 localhost kernel: tg3: eth0: Link is up at 100 Mbps, full
duplex.
Jul 28 08:03:10 localhost kernel: tg3: eth0: Flow control is on for TX and
on for RX.

Hmm, it seems that memory is leaking somehow, somewhere. It happens after
about 8 hours of inactivity.


> Also check for root's and other users crontab to see if there is
> something scheduled for the night...

I checked the crontab in an xterm like this:

[catalin@localhost catalin]$ crontab -l
no crontab for catalin
[catalin@localhost catalin]$ su -
Password:
[root@localhost root]# crontab -l
no crontab for root
[root@localhost root]#

Shouldn't I have some jobs done during the night, like updatedb and the
like?

Very interesting, to say the least...


Catalin



-- 

        <<<< ================================== >>>>
        <<     We are what we repeatedly do.      >>
        <<  Excellence, therefore, is not an act  >>
        <<             but a habit.               >>
        <<<< ================================== >>>>



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux