DIRACGrid/DIRAC — Issue #547: Something wrong with DIRAC processes
Author: msapunov
Created: 2012-02-28 10:34:58+00:00
State: open

Part of an output of ps command at machine on which i have freshly installed pre10:

S 3631 \_ runsv WorkloadManagement_TaskQueueDirectorFormation
S 3633 | \_ svlogd .
SNl 29385 | \_ python /opt/dirac/pro/DIRAC/Core/scripts/dirac-agent.py Workl
ZN 29413 | \_ [ldconfig]
S 3632 \_ runsv WorkloadManagement_TaskQueueDirectorFrancegrilles
S 3634 | \_ svlogd .
SNl 29392 | \_ python /opt/dirac/pro/DIRAC/Core/scripts/dirac-agent.py Workl
ZN 29417 | \_ [ldconfig]
S 3636 \_ runsv WorkloadManagement_TaskQueueDirectorCPPM
S 3638 | \_ svlogd .
SNl 30466 | \_ python /opt/dirac/pro/DIRAC/Core/scripts/dirac-agent.py Workl
ZN 30486 | \_ [ldconfig]
S 25371 \_ runsv WorkloadManagement_SandboxStore
S 25372 | \_ svlogd .
Sl 27647 | \_ python /opt/dirac/pro/DIRAC/Core/scripts/dirac-service.py Wor
Z 28085 | \_ [ldconfig]
S 14188 \_ runsv DataManagement_StorageElement
S 14189 \_ svlogd .
Sl 14190 \_ python /opt/dirac/pro/DIRAC/Core/scripts/dirac-service.py Dat
Z 14209 \_ [ldconfig]

Note, that each any every DIRAC process has a zombie child. So far i have 34 zombie processes on the machine and all of them were spawned by DIRAC processes.
This is a common pattern, we have the same problem at volhcb17 or at DIRAC instance in Lyon.
Could this problem triggered by recent changes in DISET protocol?