System logs on a Plesk server are not populating

Wondering why system logs on a Plesk server are not populating? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team help a customer  deal with this plesk error.

How to resolve System logs on a Plesk server are not populating?

Usually, system logs such as /var/log/maillog, /var/log/secure or /var/log/messages are empty and not populating.

When activating Fail2Ban at Tools & Settings > IP Address Banning (Fail2Ban) > Settings, the operation is successful, but the option Enable intrusion detection is still disable.

The following error message appears in the service status:

service fail2ban status
…
ERROR Failed during configuration: Have not found any log file for ssh jaiCopy Code

Issue occurs if system package rsyslog which is responsible for logging is not install on the server.

on CentOS/RHEL-based distributions

#rpm -qa | grep rsyslogCopy Code

on Debian/Ubuntu-based distributions

#dpkg -l | grep rsyslogCopy Code

Please note the rsyslog package does not come by default on AlmaLinux installations.

Today, let us see the steps followed by our Support Techs to resolve it.

1. Firstly, connect to the Plesk server via SSH.

2. Then, install the rsyslog package:

on CentOS/RHEL-base distributions

yum install rsyslogCopy Code

or the command below, if DNF package manager is used:

dnf install rsyslogCopy Code

on Debian/Ubuntu-base distributions

apt install rsyslogCopy Code

3. Finally, start the rsyslog service:

systemctl start rsyslogCopy Code

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw steps followed by our Support Engineers to resolve System logs on a Plesk server are not populating issue.