Applicable to:
- Plesk for Linux
Symptoms
-
An email notification that contains the following error notification is received often:
CONFIG_TEXT: error: state file /var/lib/logrotate/status is already locked
logrotate does not support parallel execution on the same set of logfiles.
Cause
The error is related to the execution of the /usr/share/imunify360-wafd/logrotate
cron task.
The message you are encountering typically arises when two separate logrotate
processes are executed simultaneously, due to which one of them fails to be executed, since the execution itself requires certain files to be locked for use temporarily and it is not possible for them to be locked by two separate processes simultaneously.
Resolution
The error itself has no actual impact and can be safely ignored. This issue was caused by a bug within Imunify360 extension, designated by Imunify's team as DEF-34536 and it has been fixed in webshield-1.34.3
component update.
Update the Imunify extension to install the updated component and resolve this issue.
If the issue persists after even after updating Imunify, try force-updating the webshield
component with the following command:
# wget -O ./imunify-force-update.sh https://repo.imunify360.cloudlinux.com/defence360/imunify-force-update.sh && bash ./imunify-force-update.sh
If the issue persists even after that, share the ticket with CloudLinux for further investigation.
Their article for reference (note: the release versions and ETAs are outdated): https://cloudlinux.zendesk.com/hc/en-us/articles/20251320172956-Notifications-from-cron-flock-w-5-usr-share-imunify360-wafd-logrotate-logrotate-usr-share-imunify360-wafd-logrotate
Comments
0 comments
Please sign in to leave a comment.