• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

[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