From Fedora Project Wiki

(remove remnants of old instructions, use journalctl -ab)
m (since we speak about last entries, automatically scroll to the end)
Line 9: Line 9:
 
# If you are using a graphical environment, open a terminal window.
 
# If you are using a graphical environment, open a terminal window.
 
# Check if system logging facility is working:  
 
# Check if system logging facility is working:  
## {{command| su -c 'journalctl -ab'}}  
+
## {{command| su -c 'journalctl -aeb'}}  
 
# If rsyslog is installed (for example, on the Server Edition), check:
 
# If rsyslog is installed (for example, on the Server Edition), check:
 
## {{command| su -c 'tail /var/log/secure'}}  
 
## {{command| su -c 'tail /var/log/secure'}}  

Revision as of 11:45, 23 March 2016

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#system-logging release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case tests if system logging infrastructure is available and working as expected.

Setup

  1. Install Fedora according to QA:Testcase_Boot_default_install, using one of the release-blocking media (e.g. Workstation live image or Server DVD).
  2. If necessary, reboot your system after the installation.

How to test

  1. If you are using a graphical environment, open a terminal window.
  2. Check if system logging facility is working:
    1. su -c 'journalctl -aeb'
  3. If rsyslog is installed (for example, on the Server Edition), check:
    1. su -c 'tail /var/log/secure'

Expected Results

  1. Log files should not be empty.
  2. The last entries in logs should correspond to the current date and time.