• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Forwarded to devs mailmng-server error: Fatal error: boost::exception_detail::clone_impl

burnley

Regular Pleskian
TITLE:
mailmng-server error: Fatal error: boost::exception_detail::clone_impl
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CentOS 7 Plesk Onyx Version 17.5.3 Update #21, last updated on Sept 11, 2017 05:02 PM
PROBLEM DESCRIPTION:
/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.​
STEPS TO REPRODUCE:
[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)​
ACTUAL RESULT:
/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)​
EXPECTED RESULT:
No crash​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Thank you for report.
Bug was confirmed and submitted as PPP-32487
 
Back
Top