- Plesk for Linux
Note: This article has the reference to the issues with the fixes available:
- #PPPM-10220 "Cannot Update Plesk with DUMP_D on NFS share because of perhaps unnecessary chown? (as PPP-41230)"
- Plesk Obsidian Release Candidate 1.0 04 June 2019
- #PPP-41230 "Plesk updates no longer fail when Plesk legitimate NFS share is used as DUMP_D."
Plesk cannot be updated with the following error:
CONFIG_TEXT: ***** problem report *****
ERROR while trying to backup MySQL database
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.11_installation.log), fix and try again
Bootstrapper has finished action (exec time: 1 sec.): parent_name='PLESK_17_8_11', sequence='prep', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; rm -f /var/lock/parallels-panel-upgrade-failure.flag; /etc/init.d/psa restart; :'', m_arch='', output: ~empty
Error: An error occurred during performing of installation PREP actions (see log for details). Installation was rolled back.
Warning! Not all packages were installed.
DUMP_D parameter is pointing to NFS share:
# grep DUMP_D /etc/psa/psa.conf
NFS share has
# mount | grep /mnt/share
203.0.113.2:/mnt/pool01/bk-plesk-chili/psaadm on /mnt/bk-chili type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=203.0.113.2,local_lock=none,addr=203.0.113.2)
It is a Plesk bug with ID #PPPM-10220. It will be fixed in one of the next Plesk updates.
Connect to the server via SSH and use one of the following workarounds:
Re-mount NFS storage as NFS3 storage using this command:
# umount /mnt/share
# mount -t nfs -o vers=3 SERVER:PATH /mnt/share
Disable idmapping for nfs4 share:
# echo "options nfs nfs4_disable_idmapping=1" >> /etc/modprobe.d/nfs.conf