Are you getting tired of sorting out all the problems in Plesk? Here’s one more fix pending!
You were getting a problem with system logs which is not population now. The system logs such as /var/log/messages, /var/log/secure and /var/log/maillog are not populating and empty.
Usually, you will be activating “Fail2Ban” in the section “Tools & Settings”. By tapping on the option “IP Address Banning (Fail2Ban)” and then select “Settings”.
You get an error message:
Check whether rsyslog is installed on the server or not. If not, you will get this error in CentOS and Debian.
RHEL-based CentOS distribution:
Ubuntu-based Debian distribution:
Let’s start fixing this problem:
Step 1: Use SSH for connecting the server.
Step 2: Do install the package rsyslog:
RHEL-based CentOS distribution:
Try by using the command dnf
Ubuntu-based Debian distribution:
Step 3: Start the service rsyslog using the below-mentioned command:
Hereby, it is an easy command execution. You will not get the error “System logs on a Plesk server is not population”!
You were getting a problem with system logs which is not population now. The system logs such as /var/log/messages, /var/log/secure and /var/log/maillog are not populating and empty.
Usually, you will be activating “Fail2Ban” in the section “Tools & Settings”. By tapping on the option “IP Address Banning (Fail2Ban)” and then select “Settings”.
You get an error message:
Code:
service fail2ban status
…
ERROR Failed during configuration: Have not found any log file for ssh jaiRHEL-based CentOS distribution:
Code:
#rpm -qa | grep rsyslog
Code:
#dpkg -l | grep rsyslogStep 1: Use SSH for connecting the server.
Step 2: Do install the package rsyslog:
RHEL-based CentOS distribution:
Code:
yum install rsyslog
Code:
dnf install rsyslog
Code:
apt install rsyslog
Code:
systemctl start rsyslog
