• 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 logrotate service fail, plesk-ext-monitoring-hcd.service

daniellee100

New Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.58 Update #2
Can you help me with the errors please


Execution status has failed with exit code 3, stdout: × logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Mon 2024-02-12 00:00:16 UTC; 12h ago
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Main PID: 3623490 (code=exited, status=1/FAILURE)
CPU: 5.572s

Feb 12 00:00:01 ***myserver** logrotate[3623540]: Error: SiteDomain parameter not defined in your config/domain file. You must edit it for using this version of AWStats.
Feb 12 00:00:01 ***myserver** logrotate[3623540]: Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be wrong.
Feb 12 00:00:01 ***myserver** logrotate[3623540]: Check config file, permissions and AWStats documentation (in 'docs' directory).
Feb 12 00:00:01 ***myserver** su[3623501]: pam_unix(su-l:session): session closed for user www-data
Feb 12 00:00:08 ***myserver** logrotate[3623490]: error: error renaming /usr/local/maldetect/logs/clamscan_log.4.gz to /usr/local/maldetect/logs/clamscan_log.5.gz: Read-only file system
Feb 12 00:00:08 ***myserver** logrotate[3623490]: error: error renaming /usr/local/maldetect/logs/inotify_log.4.gz to /usr/local/maldetect/logs/inotify_log.5.gz: Read-only file system
Feb 12 00:00:16 ***myserver** systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Feb 12 00:00:16 ***myserver** systemd[1]: logrotate.service: Failed with result 'exit-code'.
Feb 12 00:00:16 ***myserver** systemd[1]: Failed to start Rotate log files.
Feb 12 00:00:16 ***myserver** systemd[1]: logrotate.service: Consumed 5.572s CPU time.
, stderr:


Execution status has failed with exit code 3, stdout: × plesk-ext-monitoring-hcd.service - Hardware changes detector for the Plesk Monitoring
Loaded: loaded (/lib/systemd/system/plesk-ext-monitoring-hcd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2024-02-01 22:46:20 UTC; 1 week 3 days ago
Main PID: 1527 (code=exited, status=1/FAILURE)
CPU: 3.551s

Notice: journal has been rotated since unit was started, output may be incomplete.
, stderr:


OS
Ubuntu 22.04.3 LTS
Product
Plesk Obsidian
Version 18.0.58 Update #2,
 
There are some specific instructions in the error message like

"SiteDomain parameter not defined in your config/domain file. You must edit it for using this version of AWStats."
"Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be wrong."
"Check config file, permissions and AWStats documentation (in 'docs' directory)."

Did you by chance install your own AWStats? Did you check the contents of /etc/awstats? Do they correspond to your domains?

There seems to be another log access error regarding maldetect, a software not managed by Plesk. Maybe the symptoms point to a general permission issue with log paths?
 
There are some specific instructions in the error message like

"SiteDomain parameter not defined in your config/domain file. You must edit it for using this version of AWStats."
"Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be wrong."
"Check config file, permissions and AWStats documentation (in 'docs' directory)."

Did you by chance install your own AWStats? Did you check the contents of /etc/awstats? Do they correspond to your domains?

There seems to be another log access error regarding maldetect, a software not managed by Plesk. Maybe the symptoms point to a general permission issue with log paths?
hi Peter,

i'm not aware of installing my own awstats.

I checked /etc/awstats and here is the content:
1707747886226.png

also checked the config and sitedomain isn't defined, but it's also not defined on my other vps older one and it works fine over there.

the maldetect could be the sentinel anti malware
 
Back
Top