• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

[URGENT] Domains/Clients not expiring after update

L

lucasl

Guest
Hi,

None of our clients / domains expire after having performed the update! Nor any notification e-mails are sent out warning of an expiration limit, which is also the case for client limits (bandwidth, space, etc)

I'm driving myself crazy looking for what could be wrong. Any ideas? Is there a specific plesk cron job that should be running and maybe is not?

Thanks
 
Please anyone has any idea of what could be wrong?

Any particular cron jobs that check for client limits/expirations that may have been disabled after the upgrade?

This is pretty urgent :-/

Thanks for your time!
/L
 
Thank you so much for no support at all, no replies!

If this happens to someone else, you need to reboot! My server had a great uptime but this time you need to reboot, and wait for the next morning when all the PSA cron scripts are run. That should fix it!
 
Please anyone has any idea of what could be wrong?

Any particular cron jobs that check for client limits/expirations that may have been disabled after the upgrade?

This is pretty urgent :-/

Thanks for your time!
/L

Expirations are cheched inside statistics utility, which is executed by cron on daily basis.
(/usr/local/psa/bin/run-parts.sh /etc/psa/plesk-cron.daily task)

Check crontab for user root.

Also the reason can be in statistics utility crash.
Check the output of /usr/local/psa/admin/sbin/statistics command. Are there any errors?
 
Back
Top