A task invoked by crond is stuck in a zombie state due to a pipe event

Solution Unverified - Updated -

Issue

  • The tasks invoked from crond get stuck in a Zombie state forever even after reboot.
$ grep -e COMM -e Zs ps
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
xxxxxx    2302  0.0  0.0      0     0 ?        Zs   16:16   0:00 [sh] <defunct>
xxxxxx    2303  0.0  0.0      0     0 ?        Zs   16:16   0:00 [sh] <defunct>
xxxxxx    2304  0.0  0.0      0     0 ?        Zs   16:16   0:00 [sh] <defunct>
xxxxxx    2305  0.0  0.0      0     0 ?        Zs   16:16   0:00 [sh] <defunct>
xxxxxx    2306  0.0  0.0      0     0 ?        Zs   16:16   0:00 [sh] <defunct>
xxxxxx    2307  0.0  0.0      0     0 ?        Zs   16:16   0:00 [sh] <defunct>

$ pstree 

           |-crond(2109)-+-crond(2283)-+-sendmail(2592)---postdrop(2593)
           |             |             `-sh(2303)
           |             |-crond(2284)-+-sendmail(3008)---postdrop(3009)
           |             |             `-sh(2307)
           |             |-crond(2285)-+-sendmail(2972)---postdrop(2976)
           |             |             `-sh(2305)
           |             |-crond(2286)-+-sendmail(2999)---postdrop(3001)
           |             |             `-sh(2306)
           |             |-crond(2287)-+-sendmail(2971)---postdrop(2978)
           |             |             `-sh(2302)
           |             `-crond(2288)-+-sendmail(2957)---postdrop(2959)
           |                           `-sh(2304)

Environment

  • Red Hat Enterprise Linux 7.9
  • Third-party Java

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content