• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Daily Maintenance Script failing - debug attached

TimMcTPC

Basic Pleskian
Hello,

We have a Plesk 11.0.9 MU #56 server with 3663 subscriptions, although most are simple domains with no services, just DNS.
Statistics weren't updating for customers with hosting, so I added commands to send output info from the daily maintenance file to a log, here is the contents:

Code:
+ export PLESK_DEBUG_LEVEL=4
+ PLESK_DEBUG_LEVEL=4
+ /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 Starting: Daily Maintainance
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 == Begin Check for updates
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 Last updates or upgrades check has been made at 2013-08-14T04:03:27+01:00
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 == End Check for updates
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 == Begin Installation of updates
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 == End Installation of updates
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 == Begin Update keys
[Fri, 16 Aug 2013 04:03:03 +0100] > 0 updating scheduled keys
[Fri, 16 Aug 2013 04:03:04 +0100] > 0 update resultCode=2 resultDesc=Key update disabled
[Fri, 16 Aug 2013 04:03:04 +0100] > 0 == End Update keys
[Fri, 16 Aug 2013 04:03:04 +0100] > 0 == Begin Collect Plesk usage statistics
[Fri, 16 Aug 2013 04:03:09 +0100] > 0 == End Collect Plesk usage statistics
[Fri, 16 Aug 2013 04:03:09 +0100] > 0 == Begin Process autoreports
[Fri, 16 Aug 2013 04:03:09 +0100] > 0 == End Process autoreports
[Fri, 16 Aug 2013 04:03:09 +0100] > 0 == Begin Sitebuilder management
[Fri, 16 Aug 2013 04:03:09 +0100] > 0 == End Sitebuilder management
[Fri, 16 Aug 2013 04:03:09 +0100] > 0 == Begin Mail boxes usage
[Fri, 16 Aug 2013 04:03:14 +0100] > 0 == End Mail boxes usage
[Fri, 16 Aug 2013 04:03:14 +0100] > 0 == Begin Execute statistics backend
[Fri, 16 Aug 2013 05:22:51 +0100] > 0 == End Execute statistics backend
[Fri, 16 Aug 2013 05:22:51 +0100] > 0 == Begin Optimize statistics
[Fri, 16 Aug 2013 05:22:51 +0100] > 0 Calc client traffic.
[Fri, 16 Aug 2013 05:22:52 +0100] > 0 Remove expired client traffic.
[Fri, 16 Aug 2013 05:22:52 +0100] > 0 Collapse domain traffic.
[Fri, 16 Aug 2013 05:22:52 +0100] > 0 Collapse client traffic.
[Fri, 16 Aug 2013 05:22:52 +0100] > 0 == End Optimize statistics
[Fri, 16 Aug 2013 05:22:52 +0100] > 0 == Begin Analyse domain statistics
[Fri, 16 Aug 2013 05:22:52 +0100] > 0 processing domains
[Fri, 16 Aug 2013 05:22:52 +0100] o 0 domain1.com
[Fri, 16 Aug 2013 05:22:52 +0100] o 0 domain2.com
[Fri, 16 Aug 2013 05:22:52 +0100] o 0 domain3.com
[Fri, 16 Aug 2013 05:22:52 +0100] o 0 domain4.com

The pattern of domains is repeated for a good while until:

Code:
PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 71 bytes) in /usr/local/psa/admin/plib/Limits/DomainLimitsManager.php on line 686

This issue occurs daily and appears at around the same point each time. Can you give me any recommendations on how to best fix this issue, please?

Regards
 
Code:
[root@p ~]# php -i | grep memory
PHP Deprecated:  Directive 'safe_mode' is deprecated in PHP 5.3 and greater in Unknown on line 0
memory_limit => 128M => 128M
 
Try to increase memory limit on your server

yes, of course, but 128MB is quite a large limit anyway. prevention is better than cure - can this script be fixed to release memory rather than consuming more and more during running?
 
Further looking at this, the limit is 256MB, thus the panel isn't using the limit defined in your command above. Anyone else have any ideas?
 
Back
Top