Why sosreport process is listed in ps output even if it has successfully completed its execution ?
Issue
Sosreportprocess is listed inpsoutput even if it has successfully completed its execution and generatedsosreportin/tmp
[root@localhost ~]# ps -ef | grep sosreport
root 23093 23083 0 17:16 ? 00:00:00 /bin/sh -c nice sosreport --tmp-dir "$DUMP_DIR" --batch \? --only=anaconda --only=bootloader --only=devicemapper \? --only=filesys --only=hardware --only=kernel --only=libraries \? --only=memory --only=networking --only=nfsserver --only=pam \? --only=process --only=rpm -k rpm.rpmva=off --only=ssh \? --only=startup --only=yum --only=general --only=x11 \? >sosreport.log 2>&1 \? && {? rm sosreport.log? rm sosreport*.md5? mv sosreport*.tar.bz2 sosreport.tar.bz2? mv sosreport*.tar.xz sosreport.tar.xz? exit 0? } 2>/dev/null? # Error in sosreport run. Let user see the problem.? echo "sosreport run failed with exit code $?, log follows:"? # sosreport prints many useless empty lines, nuke them:? # it looks awful in syslog otherwise.? cat sosreport.log | sed 's/ *$//' | grep -v '^$'? rm sosreport.log? exit 1
root 23094 23093 2 17:16 ? 00:00:03 /usr/bin/python /usr/sbin/sosreport --tmp-dir /var/spool/abrt/pyhook-2014-05-20-17:16:28-22860 --batch --only=anaconda --only=bootloader --only=devicemapper --only=filesys --only=hardware --only=kernel --only=libraries --only=memory --only=networking --only=nfsserver --only=pam --only=process --only=rpm -k rpm.rpmva=off --only=ssh --only=startup --only=yum --only=general --only=x11
root 25940 16108 0 17:18 pts/1 00:00:00 grep sosreport
Environment
- Red Hat Enterprise Linux 6.4
- sos-2.2-47.el6.noarch
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
