Line 1: |
Line 1: |
| + | --[[User:Stephdl|Stephdl]] ([[User talk:Stephdl|talk]]) 13:12, 26 January 2014 (MST) Hi daniel, i do not understand why you have removed the chapter on the log file audits, is it for security reason ? |
| + | I have copied here because i use it often when i work on the bugteam side :) |
| | | |
| + | ==Log== |
| + | ===Quick Parse of Log=== |
| + | a quick parse of your log, but you should read the entire log |
| + | less /var/log/messages| grep -iE "uninitialized|WARNING|ERROR" |
| + | ===Deep parse Log to find 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 |
| + | less /var/log/messages| grep -iE "useless|uninitialized|warn|fail|error|disable|unable|exit" |
| + | of course this is for the /var/log/messages |
| + | |
| + | ===Parse all Logs to find errors=== |
| + | Parse all logs and write (under /root) the output to a text file named with the date of day. For example log012214: |
| + | |
| + | find /var/log/ -mtime -2 -print -exec sh -c 'cat "{}" | tai64nlocal | egrep -i "useless|warn|fail|error|disable|remov|unable|exit"' \; > "log$(date +'%m%d%y')" 2>&1 |
| + | then: |
| + | cd /root |
| + | less log012214 |