Search Engine: Elastic

Article ID: 119853, created on Jan 28, 2014, last review on May 10, 2014

  • Applies to:
  • Plesk Automation 11.5


  1. PPA upgrade to version 11.5 fails with the following error message:

    [LOGTEE]: 2014-01-21 16:31:00.884  INFO Upgrading packages on host: (2)...
    [LOGTEE]: 2014-01-21 16:32:46.882 ERROR Error trace:
    [LOGTEE]: 2014-01-21 16:32:46.882 ERROR ppacommon.errors.PPAUpdaterError
    [LOGTEE]: Failed to update service node '' (2). Full update command output is saved to '/tmp/tmpYPwWiuppa_upgrade'.
    [LOGTEE]:       See update log files '/tmp/autoinstaller3.log', '/tmp/ppa_install.log', '/tmp/plesk_*_installation.log' on the host ''
    [LOGTEE]: 2014-01-21 16:32:46.900 ERROR ppacommon.errors.PPAUpdaterError occurred during executing atomic action 157100-PPA-144336-1-upgrade-apache-nodes owner PleskIntegration
  2. When you have opened temporary file /tmp/tmpYPwWiuppa_upgrade you see the error:

    Fatal error during packages installation: Test Transaction Errors:   installing package drweb-bases- needs 13MB on the / filesystem
    YumTestTransactionError: Test Transaction Errors:   installing package drweb-bases- needs 13MB on the / filesystem
    ERROR: Failed to run the Yum utility.
    The Yum utility failed to install the required packages.
    Attention! Your software might be inoperable.
    Please, contact product technical support.
    [Tue 21 Jan 2014 04:33:33 PM CET][ERROR] Unable to upgrade packages. See installation log file '/tmp/ppa_install.log' for details on the host ''


It is not enough free diskspace on required service node for install additional packages during upgrade.


  1. Log in to the required service node

  2. Check the available diskspace: df -h
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/sda1       7.9G  7.4G   92M  99% /
    tmpfs           939M     0  939M   0% /dev/shm
    /dev/sda2       4.0G  143M  3.6G   4% /tmp
    /dev/sda4        36G  1.3G   33G   4% /var 
  3. Increase available disk space up to 5 Gb at least.

  4. Re-initiate the upgrade.

33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF