Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
"Stalled" system and runaway forking of 'cron' processes on macppc-6.99.28
For the last several weeks, I've been observing the following behavior
on a diskless macppc system (PowerBook G4 667 "TiBook") with native
Xorg:
some rxvt-unicode windows stop updating/repainting text (need to observe
with in-tree xterm).
rapid updating text in rxvt-unicode window appears to crash that process.
(again, need to observe with in-tree xterm).
system appears to stall: idle shell windows will redraw prompt, but not
fork additional processes.
Any interactive applications already running continue to function
(ssh sessions, web browsers, etc.)
Screen savers (xlock, xscreensaver) will activate, but authenticating
to unlock the screen hangs if successful (if unsuccessful, screen saver
resumes as normal).
To try to see what might be going on, I kept a terminal window running
'top' and what I observed is an ever-increasing number of processes
running 'cron'. When I first noticed, there were about 23 of them.
They appear to add 2 processes about every 10 minutes. As a result, my
'top' display now looks like:
load averages: 0.05, 0.04, 0.00; up 0+18:37:21 12:27:57
229 processes: 92 runnable, 135 sleeping, 1 stopped, 1 on CPU
CPU states: 2.6% user, 0.0% nice, 0.6% system, 0.0% interrupt, 96.8% idle
Memory: 205M Act, 96K Inact, 17M Wired, 26M Exec, 63M File, 725M Free
Swap: 1024M Total, 1024M Free
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
1107 jdbaker 85 0 44M 36M select 8:25 0.00% 0.00% links
887 root 85 0 56M 42M select 6:31 0.00% 0.00% Xorg
0 root 96 0 0K 7720K sopendfr 1:24 0.00% 0.00% [system]
378 jdbaker 43 0 4740K 2564K CPU 0:44 0.00% 0.00% top
842 jdbaker 85 0 12M 6064K select 0:42 0.00% 0.00% xclock
1484 jdbaker 85 0 23M 16M select 0:29 0.00% 0.00% xv
134 jdbaker 85 0 6980K 2976K select 0:14 0.00% 0.00% FvwmPager
947 jdbaker 85 0 8532K 4172K select 0:07 0.00% 0.00% fvwm
280 ntpd 85 0 8228K 7944K pause 0:05 0.00% 0.00% ntpd
690 jdbaker 85 0 27M 8844K kqueue 0:04 0.00% 0.00% urxvt
1214 jdbaker 85 0 27M 9080K kqueue 0:03 0.00% 0.00% urxvt
389 jdbaker 85 0 8924K 3412K select 0:03 0.00% 0.00% xload
97 jdbaker 85 0 6908K 2936K select 0:03 0.00% 0.00% FvwmIconMan
357 root 85 0 7932K 9404K select 0:02 0.00% 0.00% amd
699 root 85 0 11M 2488K kqueue 0:02 0.00% 0.00% master
1590 jdbaker 85 0 27M 9060K kqueue 0:01 0.00% 0.00% urxvt
1814 jdbaker 85 0 10M 4840K select 0:01 0.00% 0.00% ssh
323 jdbaker 85 0 8924K 3412K select 0:01 0.00% 0.00% xbiff
21592 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
21401 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
23121 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22351 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
1609 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22291 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22019 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22139 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
1017 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
1271 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
21749 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
1268 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
23152 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22126 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
21996 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
481 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
23519 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
3037 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
24028 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
23126 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
1108 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
11720 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
12998 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22468 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
707 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
831 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
23997 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
827 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
20793 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
22071 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
1717 root 0 0 0K 0K RUN 0:00 0.00% 0.00% cron
I don't know whether this is just a symptom or a cause of the "stall".
Most of the time, the system indicates 100% idle (the 96.8% above likely
is due to the clipboard operation to copy/paste the display).
I need to get a better picture of just how soon the behavior starts.
Right now, I don't think it's related to high-load activity such as
the nightly maintenance operations as I think it started before then.
An interesting side effect seems to be that in this state, the mouse
pointer remains functional (before this started happening, it would lose
one or both directions, behaving as though it were constantly being moved
to the top, left or top-left of the display after about an hour).
--
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD
| X No HTML/proprietary data in email. BSD just sits there and works!
|/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Home |
Main Index |
Thread Index |
Old Index