• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

"0upgrade: integer expression expected" on upgrade from 10.4.4 to 11.0.9

LarsenD

Regular Pleskian
The upgrade seems to finish fine and I couldn´t find any problems so far, but there is an error message shown while the upgrade is running:

Preparing to replace php5-ioncube-loader 4.0.7-11102413 (using .../php5-ioncube-loader_4.0.14-12050719_amd64.deb) ...
Unpacking replacement php5-ioncube-loader ...
/var/lib/dpkg/info/php5-ioncube-loader.postrm: line 3: [: 0upgrade: integer expression expected

Happened on every server I updated. This message originates from an Ubuntu 10.04.4. On Debian 6 the part with "postrm" was missing.

This should be fixed for the next version.
 
Preparing to replace php5-ioncube-loader 4.0.7-11102413 (using .../php5-ioncube-loader_4.0.14-12050719_amd64.deb) ...
Unpacking replacement php5-ioncube-loader ...
/var/lib/dpkg/info/php5-ioncube-loader.postrm: line 3: [: 0upgrade: integer expression expected

Happened on every server I updated. This message originates from an Ubuntu 10.04.4. On Debian 6 the part with "postrm" was missing.

This should be fixed for the next version.

Funny, but in a sense it will be fixed no matter what, since this is a bug in a previous version (i.e. for Plesk 10.4.4, the script with error belongs to the old ionCube package). Also it seems like a minor dash incompatibility, rather than a general bug.
 
Larsen for the sake for others, do you mind sharing how you resolved that problem?
 
Back
Top