Revision as of 12:59, 30 May 2018

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#Remote_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 article is incomplete. Remote logging happens when the operating system logs events and errors to a different machine (server) over the network. This test case shows whether remote logging can be set up in a Fedora Server environment using system packages available after the installation.

Setup

Run the default installation of Fedora Server on two different machines, either bare metal or virtual.
When the systems are installed, check the following steps (3 and 4) on both machines.
Check that rsyslog is installed on both machines.
```
rpm -qi rsyslog
```
Check that the rsyslog.service is up and running.
```
systemctl status rsyslog.service
```

If not, enable the service and start it.

systemctl enable rsyslog.service

systemctl start rsyslog.service

On the server, edit the /etc/rsyslog.conf file.
```
vi /etc/rsyslog.conf
```

In the file, uncomment the following lines:

module(load="imudp")

input(type="imudp" port="514")

On the server, open the UDP port 514 for incoming traffic.

firewall-cmd --permanent --add-port=514/udp

firewall-cmd --reload

On the server, restart the rsyslog.service.
```
systemctl restart rsyslog.service
```
On the server, display the /var/log/messages so that it continues in the console.
```
tail -f /var/log/messages
```
On the client, edit the /etc/rsyslog.conf file.
```
vi /etc/rsyslog.conf
```
In the file, make sure, you have the following lines uncommented with proper settings included, such as
```
action(type="omfwd"
```
```
Target=192.168.122.201 Port="514" Protocol="udp")
```
On the client, restart the rsyslog.service.
```
systemctl restart rsyslog.service
```

How to test

On the client, run the following command to log a testing message.
```
logger user.warn This is a testing machine from the client.
```
On the server, check that the message appears at the end of the /var/log/messages file.

Expected Results

The test should be considered successful, if the following is true.

The rsyslog service is installed.
If rsyslog.service is not running by default, it can be started without any errors.
After you edit the configuration files, the service must be restarted without any errors.
The client sends log messages to the server which displays them in the /var/log/messages.

Optional

You can also try sending log messages via the tcp protocol. In that case:

The server's /etc/rsyslog.conf should have different lines uncommented, i.e.
```
module(load="imtcp")
```
```
input(type="imtcp" port="514")
```
The server's firewall needs to have a tcp port 514 opened.
```
firewall-cmd --permanent --add-port=514/tcp
```
The client's configuration has the Protocol property set to tcp.

@@ Line 3: / Line 3: @@
 {{QA/Test_Case
 |description=This article is '''incomplete'''. Remote logging happens when the operating system logs events and errors to a different machine (server) over the network. This test case shows whether remote logging can be set up in a Fedora Server environment using system packages available after the installation.
-|actions=
+|setup=
 # Run the default installation of Fedora Server on two different machines, either bare metal or virtual.
 # When the systems are installed, check the following steps (3 and 4) on both machines.
@@ Line 17: / Line 17: @@
 # In the file, make sure, you have the following lines uncommented with proper settings included, such as <pre>action(type="omfwd"</pre><pre>Target=192.168.122.201 Port="514" Protocol="udp")</pre>
 # On the client, restart the <code>rsyslog.service</code>. <pre>systemctl restart rsyslog.service</pre>
+|actions=
 # On the client, run the following command to log a testing message. <pre>logger user.warn This is a testing machine from the client.</pre>
 # On the server, check that the message appears at the end of the <code>/var/log/messages</code> file.

Search

QA:Testcase Remote Logging: Difference between revisions