• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue centos 7.3 systemd warnings

Linulex

Silver Pleskian
plesk 12.5.30 #MU57

Just to let you know so plesk can fix this log-polution
On centos 7.3 systemd gives following warnings

Code:
Jan 20 17:40:42 server systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jan 20 17:40:42 server systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jan 20 17:40:42 server systemd: Configuration file /usr/lib/systemd/system/qmail.service is marked executable. Please remove executable permission bits. Proceeding anyway.

regards
Jan
 
Hello,

This is systemd that complains about bad file permissions of some systemd service configuration files. These are warnings and nothing to worry about, your system will work without problems.

If you want to stop those warnings then please execute:

chmod 0644 /usr/lib/systemd/system/psa.service
chmod 0644 /usr/lib/systemd/system/qmail.service

Thanks,
 
I know and i did, but it doesn't help, its back after the next mu is installed. Its something plesk configures, so plesk should fix this.
Its log-polution, a waist of space and makes it harder to find the log lines one really needs.

MU 59 now and

Code:
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 01:19:00 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 03:16:15 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 03:16:15 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb  4 03:16:15 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb  4 03:16:15 kvmtest244 systemd: Configuration file /usr/lib/systemd/system/psa.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.

regards
Jan
 
Hello,

You can check the below article to enable Logrotation .

You can set the following parameters of logs rotation:

  • Log rotation condition. This may be one of the following:
    • Size - Plesk rotates logs when their size exceeds a particular limit.
    • Time - daily, weekly, or monthly logs rotation.
  • Maximum number of log files.
  • Log compression. Enable this, if you want Plesk to compress log files to gzip archives.
  • Email to which Plesk should send processed log files.
https://docs.plesk.com/en-US/12.5/a...linux/statistics-and-logs/log-rotation.68648/
 
Maybe i was not clear on what is happening:

every mu that gets installed, the install sets /usr/lib/systemd/system/psa.service and /usr/lib/systemd/system/qmail.service (if that is updated) to 0750
That fills /var/log/messages with unwanted warnings

/var/log/messages is a system log and standard rotated weekly, nothing to do with the plesk logs. on a small vps, a log of 1GB can be a serious problem. especially if the log entries are avoidable warnings.
Yes, it is possible to set it manual to 644, but it will be 750 again after the next MU is installed and not everyone has the knowledge to do this.

regard
Jan
 
Back
Top