Issue mailmng-server error: Fatal error: boost::exception_detail::clone_impl

[burnley]

CentOS 7, Version 17.5.3 Update #21, last updated on Sept 11, 2017 10:46 AM. Upgraded from 12.5.30.

/usr/local/psa/admin/bin/mailmng-server --set-max-letter-size --size=78643200
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)

I keep getting this error on all the other 12.5.30 servers whenever I try to change settings in the
Server-Wide Mail Settings page. Been ignoring it hoping that'll get fixed in Onyx, but it appears the bug is still there.

 

[IgorG]

What is output of command

# ls -la /etc/sw/keys/

?

 

[burnley]

ls -la /etc/sw/keys/
total 76
drwxrws--- 8 root swkey-data 4096 Sep 11 14:16 .
drwxr-xr-x 3 root root 4096 Mar 17 20:19 ..
drwxrws--- 2 root swkey-data 4096 Mar 17 20:19 backup
-rw-r--r-- 1 root swkey-data 22 Mar 17 20:19 info
drwxrws--- 2 root swkey-data 4096 Aug 14 2015 instances
drwxrws--- 2 root swkey-data 4096 Mar 17 20:19 keys
drwxrws--- 2 root swkey-data 4096 Sep 11 10:31 lock
-rw-rw---- 1 psaadm swkey-data 37905 Sep 11 14:16 registry.xml
drwxrws--- 2 root swkey-data 4096 Sep 11 10:31 restart
drwxrws--- 2 root swkey-data 4096 Sep 11 14:16 tokens

 

[IgorG]

Try to fix permissions with

# chown psaadm:swkey-data /etc/sw/keys/instances /etc/sw/keys/tokens

And check that you have the same permission here:

# ls -la /etc/sw/keys/keys/
total 20
drwxrws--- 2 root swkey-data 4096 Sep 11 05:28 .
drwxrws--- 8 root swkey-data 4096 Sep 11 05:28 ..
-rw-rw---- 1 psaadm swkey-data 12139 Sep 11 05:28 keyXXanKTgy

 

[burnley]

# ls -la /etc/sw/keys/
total 76
drwxrws--- 8 psaadm swkey-data 4096 Sep 11 14:16 .
drwxr-xr-x 3 root root 4096 Mar 17 20:19 ..
drwxrws--- 2 root swkey-data 4096 Mar 17 20:19 backup
-rw-r--r-- 1 root swkey-data 22 Mar 17 20:19 info
drwxrws--- 2 psaadm swkey-data 4096 Aug 14 2015 instances
drwxrws--- 2 psaadm swkey-data 4096 Mar 17 20:19 keys
drwxrws--- 2 root swkey-data 4096 Sep 11 10:31 lock
-rw-rw---- 1 psaadm swkey-data 37905 Sep 11 14:16 registry.xml
drwxrws--- 2 root swkey-data 4096 Sep 11 10:31 restart
drwxrws--- 2 psaadm swkey-data 4096 Sep 11 14:16 tokens
# ls -la /etc/sw/keys/keys/
total 28
drwxrws--- 2 psaadm swkey-data 4096 Mar 17 20:19 .
drwxrws--- 8 psaadm swkey-data 4096 Sep 11 14:16 ..
-rw-rw---- 1 psaadm swkey-data 4411 Apr 21 11:04 keyXXnG7WCO
-rw-rw---- 1 psaadm swkey-data 11377 Aug 21 07:01 keyXXZU9MLT

 

[IgorG]

Any results after fixing permissions?

 

[burnley]

Oh sorry Igor, no improvement:
/usr/local/psa/admin/bin/mailmng-server --set-max-letter-size --size=78643200
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)

 

[IgorG]

I can't reproduce it on my test server. Have you tried to fix it with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation

?

 

[burnley]

Nope, that didn't help either

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
[...]
Patching file (228 of 228) /usr/local/psa/admin/plib/Repair/Aspect/Fs.php
All patches were applied.


Patches were installed successfully.

The changes were applied successfully.

#
# plesk repair installation

Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp17.5.3-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
Failed to execute operation: File exists
Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_17.5.3_repair.log' and '/var/log/plesk/install/plesk_17.5.3_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Parallels support.

# /usr/local/psa/admin/bin/mailmng-server --set-max-letter-size --size=78643200
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)

 

[burnley]

Ok, thanks to a related thread - Resolved - mailmng-server returns "bad lexical cast" error - where someone else suggested using strace I found what the problem is. mailmng-server crashes on postconf output:

[root@plesk12 ~]# postconf mailbox_size_limit
mailbox_size_limit = $message_size_limit <-- this is valid Postfix configuration.
[root@plesk12 ~]# /usr/local/psa/admin/bin/mailmng-server --get-mailbox-size-limit
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
[root@plesk12 ~]# postconf -e 'mailbox_size_limit=78643200'
--- It will now work: ---
[root@plesk12 ~]# /usr/local/psa/admin/bin/mailmng-server --get-mailbox-size-limit
78643200
[root@plesk12 ~]# /usr/local/psa/admin/bin/mailmng-server --set-max-letter-size --size=78643200
[root@plesk12 ~]# postconf -e 'mailbox_size_limit=$message_size_limit'
--- It will break again ---
[root@plesk12 ~]# /usr/local/psa/admin/bin/mailmng-server --get-mailbox-size-limit
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
[root@plesk12 ~]# /usr/local/psa/admin/bin/mailmng-server --set-max-letter-size --size=78643200
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)
Fatal error: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >(bad lexical cast: source type value could not be interpreted as target)

Bug?

 

[IgorG]

Bug?

I can't reproduce it.
I can only recommend creating a request to support team to do the in-depth investigation to find the reason and to fix it. Please create a ticket to support at Plesk Help Center

 

[burnley]

Igor, all due respect but that support site is c.r.a.p. You really need to offer your clients a better way of submitting bugs, otherwise people will just p*** off and you won't get them reported. Here's what I get when entering the key:
We identified that the Plesk license was purchased not directly from Plesk but through one of the Plesk Resellers.
In this case, you need to contact your license provider for support service.
Plesk Partners (Resellers) are fully trained by Plesk and deliver best-in-the-industry support for Plesk products running on their infrastructure.
Ridiculous. Even after filling in the mandatory fields I don't seem the be able to submit the bug, there's no submit button. How else can I submit Plesk bugs and have them actually tracked properly?

 

[burnley]

Igor, to try and reproduce, try to set "mailbox_size_limit=$message_size_limit" in /etc/postfix/main.cf, then run the command
Meanwhile I've created mailmng-server error: Fatal error: boost::exception_detail::clone_impl

 

[IgorG]

First of all - until it is not confirmed by Plesk supporters or Plesk developers - it is not a bug. We know a huge number of examples where what customers called a bug was in fact either their mistake or an incorrect configuration or customization, which they simply forgot about.
Second - you really need contact support of your service provider if your Plesk license was not purchased directly from Plesk. If your service provider support can't resolve your issue - they should submit ticket to Plesk support and forward their solution to you.
Third - In the worst case, if your service provider support do not want to or can not create a ticket to Plesk support team for you, you can contact Plesk Support directly according to KB article How to get support directly from Plesk?
And finally, the fourth - you can always submit your report with the desired action from Plesk Service Team here - Reports

I believe that it is a good, suitable and comprehensive workflow for all Plesk customers. Isn't it?

 

[burnley]

No Igor, it's not. This is a technical problem which smells like a bug, walks like a bug and quacks like a bug, so it's probably a bug which I can replicate easily following the steps already published. And I can't see how someone else, partner/reseller/etc can fix a technical problem in the product that only Plesk technical people can. If Plesk is using the term "hosting provider" to hide behind it and defer the flagged issues hoping they'll just go away, well this is very poor customer support.
Now, back to the license issue, I've just checked with our accounts and the license I tried to use on that support page has been purchased directly from Plesk site Plesk Partner Central where we have an account and we also appear to be a Plesk partner ourselves. So how on earth does this license thing work? If we're a Plesk partner, shouldn't Plesk detect this from the license and allow us to submit bugs?
C'mon, I need to fix a technical problem in the product and now we're arguing about workflow & such. It's nothing but time wasted, sorry

 

[IgorG]

C'mon, I need to fix a technical problem in the product and now we're arguing about workflow & such. It's nothing but time wasted, sorry

Ok. Your report was forwarded to developers for investigation. Now you have to wait for their reply. I just thought that it is urgent issue for you and you will prefer fast solution from Plesk Support Team. But it's up to you, of course.

 

[IgorG]

Now, back to the license issue, I've just checked with our accounts and the license I tried to use on that support page has been purchased directly from Plesk site Plesk Partner Central where we have an account and we also appear to be a Plesk partner ourselves. So how on earth does this license thing work? If we're a Plesk partner, shouldn't Plesk detect this from the license and allow us to submit bugs?

Please ask it here Licensing and Purchase support - Plesk

 

[burnley]

Thanks for forwarding it Igor, but the fast response from Plesk is exactly what I'm after And I need to be able to use the right channels in order to have the issues addressed asap, this is why I don't understand why the support page you gave me doesn't accept my license which was purchased from Plesk directly. Is this another bug, perhaps in the license check code itself?