Hello,
We're using Plesk 11 with a planned migration before the end of the year. A customer complained his log files are not rotating, causing his disk usage to increase. After checking, we noticed that there is one large log file going back many months. Setting the logs to rotate by size or time doesn't make a difference.
While trying the steps found at https://kb.plesk.com/en/124610 we get the following output...
The /usr/local/psa/var/logrotate.status file appears to be recreated and we will wait several days to see if the logs start rotating.
My current question is, should we be concerned by the xargs error message that is displayed when manually running the daily maintenance script? Could that be the cause of the log rotation issue? If so, how might we fix it?
We're using Plesk 11 with a planned migration before the end of the year. A customer complained his log files are not rotating, causing his disk usage to increase. After checking, we noticed that there is one large log file going back many months. Setting the logs to rotate by size or time doesn't make a difference.
While trying the steps found at https://kb.plesk.com/en/124610 we get the following output...
Code:
# mv /usr/local/psa/var/logrotate.status /usr/local/psa/var/logrotate.status_old
# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php
xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
The /usr/local/psa/var/logrotate.status file appears to be recreated and we will wait several days to see if the logs start rotating.
My current question is, should we be concerned by the xargs error message that is displayed when manually running the daily maintenance script? Could that be the cause of the log rotation issue? If so, how might we fix it?