Unable update mailbox: mailmng failed: Empty error message from utility

[Tozz]

Ah, good find. You are correct goodiiii. According to the .inf file I got from the autoinstall server, the filenames are all i386 filenames.

<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/mailmng_domain_rename" target="/usr/local/psa/tmp/qmail-mailmng_domain_rename" md5="7e$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/authpsa" target="/usr/local/psa/tmp/qmail-authpsa" md5="8979b440c7bc36bebd9518f9edf883$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/mailsrv_conf_init" target="/usr/local/psa/tmp/qmail-mailsrv_conf_init" md5="1e35534e3b$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/mailmng_domain_toggle" target="/usr/local/psa/tmp/qmail-mailmng_domain_toggle" md5="ef$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/mailmng" target="/usr/local/psa/tmp/qmail-mailmng" md5="1d3f2b1a7369d951e48d20b067c5ea$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/mailsrv_entities_dump" target="/usr/local/psa/tmp/qmail-mailsrv_entities_dump" md5="9a$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/smtp_auth" target="/var/qmail/bin/smtp_auth" md5="6804e099be4540bcf27348f11c1251b0" cr$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/qmail/cmd5checkpw" target="/var/qmail/bin/cmd5checkpw" md5="3d17ee84a3843a1bd6f654f023887c69$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/mailmng_domain_rename" target="/usr/local/psa/tmp/postfix-mailmng_domain_rename" md5$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/authpsa" target="/usr/local/psa/tmp/postfix-authpsa" md5="38520b09a4de8e66ceead3153c$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/mailsrv_conf_init" target="/usr/local/psa/tmp/postfix-mailsrv_conf_init" md5="ecdd7c$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/mailmng_domain_toggle" target="/usr/local/psa/tmp/postfix-mailmng_domain_toggle" md5$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/mailmng" target="/usr/local/psa/tmp/postfix-mailmng" md5="30fe88e09f8e03fde412ac1dee$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/mailsrv_entities_dump" target="/usr/local/psa/tmp/postfix-mailsrv_entities_dump" md5$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/libpleskauxprop.so" target="/usr/lib/sasl2/libpleskauxprop.so" md5="775f4b9d0f15220f$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/postfix/plesk_saslauthd" target="/usr/lib/postfix/plesk_saslauthd" md5="7fde8fbed7cc0a0be3ee$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/common/poppassd" target="/usr/local/psa/admin/sbin/poppassd" md5="bbed887f185f641a214fd4f7f0$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/common/mail_grey_restore" target="/usr/lib/plesk-9.0/mail_grey_restore" md5="e7c517afda05193$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/common/mail_auth_dump" target="/usr/lib/plesk-9.0/mail_auth_dump" md5="2ab87d8427861a595c69a$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/common/mail_auth_view" target="/usr/lib/plesk-9.0/mail_auth_view" md5="4795ea1450f01b7283856$
<file name="microupdates/MU30/dist-deb-Debian-6.0-i386/common/pam_plesk.so" target="/lib/security/pam_plesk.so" md5="4c40ddf286660998111f5c1d5f0060$
<file name="microupdates/scripts/MU-mail_replace.sh" target="/usr/local/psa/tmp/MU-mail_rep

 

[IgorG]

Maybe it's only fixed for x32

Exactly. This MU#30 is only for Debian x32

 

[GiorgosP]

Exactly. This MU#30 is only for Debian x32

Since we all here are paying customers, I would expect a little more effort to respond accurately in the first place, instead of letting us lose time searching for the non-existent MU...

In addition, I wouldn't mind having a time-plan for the release of the x64 fix...

 

[IgorG]

In addition, I wouldn't mind having a time-plan for the release of the x64 fix...

I hope that fix for x64 will be included to MU which will be released this week.

 

[Tozz]

WHAT? You release a patch for 32-bit systems no-one hardly uses anymore, and you need A WEEK to fix an issue that causes showstopping issues in your software? This is bad.

Why you need a week to recompile a hand full of binaries?

 

[IgorG]

Initially this issue has been reproduced only for Debian x32. Therefore we have released MU only for Debian x32. After that we have reproduced issue for x64 too and will release fix in MU tomorrow I think.
Note that Plesk supports many OSes and tests stage of each release takes enough time. So, we can't release fix immediately after your request. Sorry.

 

[Tozz]

Parallels bugfixing and testing has been an issue for years. New major releases have always had critical bugs that could have been easily found by proper testing. Plesk 9 was horrible the first few releases. This became better with Plesk 10 and Plesk 11, althought its still not as good as it should be.

If Parallels cannot maintain the amount of OS'es its currently supports it should drop some of them in favor of better testing and faster bug fixing.

Also, Debian's 32-bit packages are the same versions as their 64-bit counterparts, only recompiled with 64-bit flags. That means if something breaks in 32-bit, it will also brake in 64-bit systems. I assume Parallels does the same (1 codebase, compiled with different flags) so IMHO it is just stupid to believe the issue was limited to 32-bit systems.

Because its the same codebase I also do not understand why you need to re-test 64-bit versions of the same code, if you've already tested the 32-bit versions.

 

[jmin]

Same problem, Centos 6, Plesk 11.0.9 update #29

Hello,
Is there any workarround for we people under Centos 6?
Thanks!

 

[IgorG]

Fix for Debian x64 is available in MU#31 - http://kb.parallels.com/115293

 

[jmin]

Hello,
What about Centos?
Have we any hope?

 

[IgorG]

Hello,
What about Centos?
Have we any hope?

Is libmysqlclient_16 package was updated by OS vendor too and caused the same error? Need more details.

 

[jmin]

Hi Igor,

As per YUM, this lib is up to date (mysqlclient16-5.1.59-2.el6.art.x86_64)
But mysql server is 5.5.27.
Would it be the problem?

 

[IgorG]

Hi Igor,

As per YUM, this lib is up to date (mysqlclient16-5.1.59-2.el6.art.x86_64)
But mysql server is 5.5.27.
Would it be the problem?

I can say nothing without details, logs, etc. AFAIK this problem affects only Debian Plesk servers but not CentOS. A lot of people use Ples on CentOS. Much more than Debian. But only you talk about this issue on CentOS.

 

[papak]

I saw this error today. Plesk on CentOS 6.3. It's also not only Debian.

BS CentOS 6.3 (Final)
Panel-Version 11.0.9 Update #29, zuletzt aktualisiert am Dez 12, 2012 03:47 AM

 

[jmin]

Yes, same config here.

mayday Igor, mayday!

 

[IgorG]

You can check that you have affected version of libmysql if you haven't any output in command

# nm -D /usr/lib/libmysqlclient.so.16.0.0 | grep EVP_CIPHER_CTX_init

 

[papak]

Output:

[root mysql]# nm -D /usr/lib64/mysql/libmysqlclient.so.16.0.0 | grep EVP_CIPHER_CTX_init
[root mysql]#

Update #31 installed.

And what now?

 

[IgorG]

Output:

[root mysql]# nm -D /usr/lib64/mysql/libmysqlclient.so.16.0.0 | grep EVP_CIPHER_CTX_init
[root mysql]#

Update #31 installed.

And what now?

Thanks. I have informed developers. I think that they will release fix soon.

 

[papak]

Thanks. I have informed developers. I think that they will release fix soon.

Many thanks Igor.

 

[IgorG]

Many thanks Igor.

Could you please show me output of command

# rpm -qf /usr/lib64/mysql/libmysqlclient.so.16.0.0

I would like to know what is package of libmysql you have.