I have a couple of questions about sosreport on rhel 6.

1.How to stop sosreport? If I kill the process, it will just run a new one.


2.I cannot exclude any plugin, it will hang whatever I run like "sosreport -n rpm" . Since I cannot stop sosreport, how can I resolve the problem?


3.My "yum clean all" command hangs. I can sosreport open some files in /var/lib/rpm. This is the reason I am looking into sosreport. Is there any way to

work around without resolving the sosreport problems?


Thanks so much in advance.

Nope...it runs once. Read the man page on the sosreport command.
Again, sosreport runs ONCE and that's it. And the -n option doesn't do what you think it does, based on what you posted...again, read the man page.
'Hangs' how? For how long? You DO know it takes a bit, right???? Solutions are covered here: https://access.redhat.com/solutions/1989973
No idea what you're saying here; an sosreport has little to do with /var/lib/rpm, unless you tell it to put the report file there. Did you read the RHEL documentation? https://access.redhat.com/solutions/3592

And the best way for you to get these problems resolved is to CALL RED HAT SUPPORT...you are PAYING FOR RHEL 6 right???? Because the sosreport is made to be sent to RHEL for analysis, and yum will only work if you pay for RHN access.

Sorry, I missed one word in the last statement. This is what I was going to say: "3.My "yum clean all" command hangs. I can see that sosreport open some files in /var/lib/rpm. This is the reason I am looking into sosreport. Is there any way to work around without resolving the sosreport problems?

Ths sosreport process is running for ever. It won't stop.

"Yum clean all" ran more than 5 minutes. I think it has hung.

I checked on other servers, there is no sosreport running. I guess it can be disable but don't know how to do i.t

When did you START the sosreport? And you can just go to another terminal, type in "ps -ef | grep -i sosreport", and then kill the associated process(es), just like any other program
AGAIN, you do not 'disable' an sosreport...it's a program. If it's not responding correctly, kill it. AGAIN, "yum clean all" MAY run for a while.

And AGAIN, since you didn't acknowledge this before, HAVE YOU CALLED RED HAT SUPPORT FOR RHEL 6??? If not, why? Again, SOSreports are by and FOR RHEL support...they will tell you nothing. Likewise, yum won't work correctly, unless you're paying for RHN access.

1 members found this post helpful.

TB0ne is right; SOS reports have nothing to do with RPM. However, to solve any issues regarding a corrupted RPM DB, I've used this:

rm –f /var/lib/rpm/__*

rpm –rebuilddb –v –v

yum clean all

Removes and rebuilds the RPM DB and then you clean up any remnants of the previous YUM cache.