[katello-devel] What data do we need to capture to debug stuff?

Cliff Perry cperry at redhat.com
Wed Nov 9 17:50:13 UTC 2011


On 11/09/2011 04:34 AM, Lukas Zapletal wrote:
> On Mon, Nov 07, 2011 at 04:15:07PM -0500, Clifford Perry wrote:
>> [Resending to correct list - katello-devel]
>>
>> I have a backlog item for a sosreport or spacewalk-debug type tooling
>> for Katello. Here is my initial list of files or directories to capture.
>>
>> Assume sosreport captures ps output, rpm -Va, rpm -qa, lots of general
>> config from /etc/ and logs from /var/ already so trying not to duplicate
>> sos, but capture beyond it.
>>
>> What is missing?
>>
>> Candlepin + Tomcat
>> /etc/candlepin/
>> /etc/tomcat6/
>> /var/log/candlepin/
>> /var/log/tomcat6/
>>
>> Pulp, grinder, mongodb
>> /etc/grinder/
>> /etc/mongodb.conf
>> /etc/pulp/
>> /etc/qpid/
>> /etc/qpidd.conf
>> /var/log/mongodb/
>> /var/log/pulp/
> 
> Pulp also logs here:
> /var/log/httpd/
> 
>> Katello + PostgreSQL
>> /etc/httpd/conf*
>> /etc/katello/
>> /etc/sudoers
>> /etc/sysconfig/katello
>> /var/lib/pgsql/data/pg_hba.conf
>> /var/lib/pgsql/data/postgresql.conf
>> /var/log/httpd/
>> /var/log/katello/
>> /var/log/puppet/
> 
> Sudoers? What for?

Just cos we edit it during install to allow cpsetup to run. We *may*
need it if debugging installation issues and it fails in cpsetup. But I
*think* sos captures that anyway, so I'd likely not worry about it.

Cliff
> 
> Looks good.
> 
> LZ
> 




More information about the katello-devel mailing list