Many crond process were in D state, had to reboot the server to recover from them.

Solution Verified - Updated -

Issue

  • Many crond process were in D state with following backtraces
Backtrace:
#0  schedule at ffffffff80062fa0
#1  pipe_wait at ffffffff80047c7a
#2  pipe_readv at ffffffff8002e959
#3  pipe_read at ffffffff800eb6bc
#4  vfs_read at ffffffff8000b735
#5  sys_read at ffffffff80011d8a
#6  tracesys at ffffffff8005d28d (via system_call)
  • Rebooted the system to recover.

Environment

  • Red Hat Enterprise Linux 5.8
  • Dell PowerEdge R620

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.