• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

[solved] Plesk Update Error - 12.5.30 MU#19

Elompenta

Regular Pleskian
I update from 12.5.30 MU#18 to 12.5.30 MU#19 on Debian Machine

I recieve the following error:
Code:
Errors were encountered while processing:
 sasl2-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_12_5_30', sequence='pkgs', 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; touch /var/lock/parallels-panel-upgrade-failure.flag; :'', m_arch='', output: ~empty
[2016-01-22 17:54:00.556705] Execute command /opt/psa/admin/bin/send-error-report install --version 12.5.30
[2016-01-22 17:54:00.562577] Error: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

Any ideas how i can fix it?
 
If i try to install manual i get the following error:

Code:
root@venus:~# apt-get install sasl2-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
sasl2-bin is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 60 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up sasl2-bin (2.1.25.dfsg1-6+deb7u1) ...
saslpasswd2: user not found
dpkg: error processing sasl2-bin (--configure):
 subprocess installed post-installation script returned error exit status 20
Errors were encountered while processing:
 sasl2-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@venus:~#
 
i've fixed this issue with the following workaround.
After the quick fix - update works fine

Code:
root@venus:~# sasldbconverter2
This program will take the sasldb file specified on the
command line and convert it to a new sasldb file in the default
location (usually /etc/sasldb2). It is STRONGLY RECOMMENDED that you
backup sasldb before allowing this program to run

We are going to convert /etc/sasldb2 and our output will be in /etc/sasldb2

Press return to continue
root@venus:~# sasldblistusers2
-> no errormessage - sasl works fine

root@venus:~# apt-get install sasl2-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
sasl2-bin is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 60 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up sasl2-bin (2.1.25.dfsg1-6+deb7u1) ...
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match saslauthd Default-Stop values (1)
[warn] To enable saslauthd, edit /etc/default/saslauthd and set START=yes ... (warning).
 
@Elompenta,

Recalling your post about a failure to compile memcache modules, I stumbled upon this post.

I am pretty sure that you should NOT install sasl2-bin: Plesk does not come with this package by default (it should only contain libauthen-sasl-perl package).

Having a "non-standard" package installed with Plesk can become very troublesome, since conflicts between packages can arise (now and in the future).

Please remove the "non-standard" packages and re-run the autoinstaller from the command line (i.e. to force a proper installation or update of packages).

Regards...
 
Back
Top