• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

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

tetrahall

Basic 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