Before you begin, you’ll need:
- Root access
- Port 5000 open
Run the rsyslog configuration script
<<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.
<<LISTENER-HOST>> with the host for your region. For example,
listener.logz.io if your account is hosted on AWS US East, or
listener-nl.logz.io if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
curl -sLO https://github.com/logzio/logzio-shipper/raw/master/dist/logzio-rsyslog.tar.gz \ && tar xzf logzio-rsyslog.tar.gz \ && sudo rsyslog/install.sh -t linux -a "<<LOG-SHIPPING-TOKEN>>" -l "<<LISTENER-HOST>>"
The above assumes the following defaults:
- Log location -
- Log type -
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Open Search Dashboards. You can search for
type:syslog to filter for your logs.
If you still don’t see your logs, see log shipping troubleshooting.
This section contains some guidelines for handling errors that you may encounter when trying to collect logs for Rsyslog - SELinux configuration.
SELinux is a Linux feature that allows you to implement access control security policies in Linux systems. In distributions such as Fedora and RHEL, SELinux is in Enforcing mode by default.
Rsyslog is one of the system processes protected by SELinux. This means that rsyslog by default is not allowed to send to a port other than 514/udp (the standard syslog port) has limited access to other files and directories outside of their initial configurations.
To send information to Logz.io properly in a SELinux environment, it is necessary to add exceptions to allow:
- rsyslog to communicate with logz.io through the desired port
- rsyslog to access the files and directories needed for it to work properly
On this page:
- Possible cause - issue not related to SELinux
- Possible cause - need exceptions to SELinux for Logz.io
Possible cause - issue not related to SELinux
The issue may not be caused by SELinux.
Disable SELinux temporarily and see if that solves the problem.
Run the following command to check the current status of SELinux:
SElinux’s status can be in any of the following states:
- Enforcing: SELinux is active and blocking the actions that do not match the policy
- Permissive: SELinux is active but is not blocking the actions that do not match the policy -- it only leaves logs indicating which actions had been performed
- Disable: SELinux is disabled
If SELinux is not in Enforcing mode, no other action is needed because it is not blocking communication to Logz.io
If SELinux is Enforced, try to disable it temporally and then restart rsyslog:
$ sudo setenforce 0 $ sudo service rsyslog restart
Check if rsyslog is working and that you see the logs in you account.
To re-enable SELinux, run:
$ sudo setenforce 1 $ sudo service rsyslog restart
The above command only disables SELinux temporarily. To disable it completely, you will have to edit its configuration file. Although from a security point of view it’s not recommended, if you want the changes to be permanent, edit the /etc/selinux/config file and restart the machine:
Possible cause - need exceptions to SELinux for Logz.io
You may need to add exception to SELinux configuration to enable Logz.io.
Install the policycoreutils and the setroubleshoot packages
# Installing policycoreutils & setroubleshoot packages $ sudo yum install policycoreutils setroubleshoot
Check which syslog ports are allowed by SELinux
Run the command as in the example below:
$ sudo semanage port -l| grep syslog output: syslogd_port_t udp 514
Add a new port to policy for Logz.io
# Adding a port to SELinux policies $ sudo semanage port -m -t syslogd_port_t -p tcp 5000
Authorize Rsyslog directory
# instructing se to authorize the /var/spool/rsyslog directory $ sudo semanage fcontext -a -t syslogd_var_lib_t "/var/spool/rsyslog/*" $ sudo restorecon -R -v /var/spool/rsyslog
Depending on the distribution, run the following command:
# instructing se to authorize /etc/rsyslog.d/* $ sudo semanage fcontext -a -t syslog_conf_t "/etc/rsyslog.d/" $ sudo restorecon -R -v /etc/rsyslog.d/ $ sudo semanage fcontext -a -t etc_t "/etc/rsyslog.d" $ sudo restorecon -v /etc/rsyslog.d
$ sudo service rsyslog restart