• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

logrotate fail

EnriqueR

Regular Pleskian
I've checked all my subscriptions and I've noticed that one of them has the access_log.processed 21GB file when I have put in rotation all my subscriptions maximum is 400MB. What is happening with this subscripción? Is there any way to recalculate the subscription logrotate correctly?
 
I think I found the problem. For some reason in /usr/local/psa/etc/logrotate.d/ path not found some subscriptions. Does anyone know what may be the reason? I do not know how often is calling logrotate by default. I'll wait a few days to see if that was the problem.
 
Where the affected subscriptions migrated or did their primary domains change at some point? I believe that log rotations are part of a daily process but I could be wrong.
 
By the way have you tried to run the daily maintenance task via SSH?

/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php
 
The problem was solved when accessing the subscription, disable log rotation and re-activate again.
Now I have found that Plesk stores the logs in two different paths: /var/www/vhost/domain.tld/logs/ and /var/www/vhost/system/domain.tld/logs/
Is that true? This system is wasting space resources by having duplicate content.
 
Back
Top