Changes

Jump to navigation Jump to search
How to report a problem
==Contents==

===How to debug===

I wrote this many moons ago. It has many links that are worth reading.

https://gist.github.com/reetp/a66149d5f060f260643a353ca7067a98

How to Report Bugs Effectively
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Asking mart questions
http://www.catb.org/esr/faqs/smart-questions.html

A good bug reporting example
https://github.com/RocketChat/Rocket.Chat/issues/13069


===History===
Tell us about your server history - upgrades/updates and what you have installed, and then some debugging output.

===Debug output===

Run these commands in a terminal:

/sbin/e-smith/audittools/newrpms
/sbin/e-smith/audittools/repositories
/sbin/e-smith/audittools/templates

db configuration show

Or go to server-manager, Miscellaneous, Report a bug, Create Configuration report.

[[Warning box|Remove anything sensitive like passwords and public IPs!!]]

You might want to put this on somewhere like pastebin as it will likely be long.

===Searching logs for errors===

You can also look in your logs for errors:

https://wiki.koozali.org/Log_Files

You can see how to search here:

https://wiki.koozali.org/Useful_Commands#Parse_Log_files_to_search_for_errors

When you want to test the SME Product it can be useful to see what it occurs. This CL can help you, but you should read the entire log

grep -iE "uninitialized|WARNING|ERROR" /var/log/messages

Or if you want to parse all logs

grep -iE "uninitialized|WARNING|ERROR" /var/log/*

===Old how to===

----
[[Category:Howto]]

Navigation menu