The CROND's without a PPID of 1 are the children of the master CROND process. They are trying to launch a command for you. Determine what that command is first. There is no info herein that defines that. 1) check the log file for CRON. See if you can determine what process is being launched here. 2) dont think the problem really relates to the MTU change, but a 9000 MTU seems kinda high for gigabit. I could be wrong. I would have to check, but I vaguely recall a recommended max MTU on my Antares GE cards of around 4KB. The change probably triggered an existing bug in one of the programs cron is spawning for you. You might want to recheck that setting for correctness. MTU's are usually in multiples of 1K less the ethernet mac packet header size as I recall. Just make sure you are not setting above the maxmium limity allowed. 3) a ps -ef or equivalent will show you the children and parents. do a ps -ef | grep [a crond child pid] and see if there is a child process hanging off the CROND sub child process ) using some sample PIDs from your PS below (master CROND (PID = 2415 (example), PPID = 1) -Forks-> Child CROND service process (PID = 2426 from your list, PPID = 2415) So what process if any if 2426 forking off here? 4) Your real problem seems to be that VMware PID 2003 is absorbing 99% of the CPU doing "something". I dont know from your info here If this is a CRON launched process or if this is a separate process launched by INITD. But this is probably the real issue. It is probably stopping the CROND from getting enough kernel time to launch. But cant tell what is really going on here from your info. But check into the VMWARE behaviour - Log Files? I dont know about vmware so cant help you there. > -----Original Message----- > From: redhat-list-admin@xxxxxxxxxx > [mailto:redhat-list-admin@xxxxxxxxxx]On Behalf Of Cove Schneider > Sent: Thursday, October 23, 2003 6:10 PM > To: redhat-list@xxxxxxxxxx > Subject: Many instances of CROND running, load raised (RH9) > > > Hello, > > For some reason a number of our servers seem to have started forking > too many CROND processes. This appears to have coincided > with changing > their interface MTUs to 9000 (Gig ethernet), but now that > I've set it > back to 1500 one of the machines is still having this > problem. The load > is very high on the machine, but it's perfectly responsive. > > Does anyone have any ideas? > > Linux seq 2.4.20-20.9smp #1 SMP Mon Aug 18 11:32:15 EDT 2003 > i686 i686 > i386 GNU/Linux > > 15:07:39 up 13 days, 4:21, 1 user, load average: 51.02, 51.05, > 51.06 > 170 processes: 169 sleeping, 1 running, 0 zombie, 0 stopped > CPU0 states: 0.0% user 100.0% system 0.0% nice 0.0% iowait > 0.0% idle > CPU1 states: 1.0% user 3.0% system 0.0% nice 0.0% iowait > 94.0% idle > Mem: 513168k av, 498860k used, 14308k free, 0k shrd, > 18572k buff > 322052k actv, 53360k in_d, 10964k in_c > Swap: 1044216k av, 48356k used, 995860k free > 429540k cached > > PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU > COMMAND > 2003 vmware 5 -10 1552 1008 704 S < 98.9 0.1 18553m 0 > vmware-vmx > 7550 root 20 0 1040 1040 704 R 3.8 0.2 > 0:00 1 top > 1950 vmware 5 -10 27876 26M 27012 S < 1.9 5.3 1192m 1 > vmware-vmx > 2034 vmware 5 -10 81276 78M 80360 S < 0.9 15.7 1132m 0 > vmware-vmx > > From the the ps man page, the "D" flag means "uninterruptible sleep > (usually IO)". > > # ps auxw|grep CROND > root 2415 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2426 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2442 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2453 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2455 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2466 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2480 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2491 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2502 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2515 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2529 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2531 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2542 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2553 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2567 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2578 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2591 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2606 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2608 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2619 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2630 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2644 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2655 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2668 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2682 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2684 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2695 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2706 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2720 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2731 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2744 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2758 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2760 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2771 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2782 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2796 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2818 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2832 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2834 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2845 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2856 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2870 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2881 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2892 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2907 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2909 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2920 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2931 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2943 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > root 2807 0.0 0.0 4292 4 ? D Oct21 0:00 CROND > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
