• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Cron Hourly Error Email: /etc/cron.hourly/plesk-php-cleanuper

tetrahall

Regular Pleskian
Hi
I am receiving CRON emails every hour like this:-
/etc/cron.hourly/plesk-php-cleanuper:
/usr/lib64/plesk-9.0/maxlifetime: line 16: [: Unable to start builtin modules: integer expression expected
/usr/lib64/plesk-9.0/maxlifetime: line 16: [: Unable to start builtin modules: integer expression expected

Apparently executing the below command in /etc/cron.hourly/plesk-php-cleanuper
[ -x /usr/lib64/plesk-9.0/maxlifetime ] && [ -d /var/lib/php/session ] && /usr/lib64/plesk-9.0/php_session_cleaner /var/lib/php/session $(/usr/lib64/plesk-9.0/maxlifetime)

causes the errors mentioned in the emails.

Line 16 in file /usr/lib64/plesk-9.0/maxlifetime is this:-
[ ! "${cur:-0}" -gt "$max" ] || max="$cur"

How can the error be prevented, please?
 
Resolved:
Uninstalling older versions of PHP has solved the problem.
No more CRON messages are received!
 
Back
Top