• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

PleskMainDBException: MySQL query failed: Data truncated for column 'fp' at row 1

D

dickyj

Guest
Hi,
We are using Plesk 8.1 and we did some mySQL performance tuning and we suspect somehow it breaks Plesk. Right now, we cannot successfully create a domain. We keep getting these errors, can someone point us to the right fix for this problem? The last time we had this error, we have to re-install the whole server, we hope we do not have to resort to that again. Thanks.

Here is the details of the error:

0: /usr/local/psa/admin/plib/common_func.php3:211
db_query(string 'replace hosting set `dom_id`='5', `sys_user_id`='10', `ip_address_id`='2', `ssl`='true', `same_ssl`='true', `fp`='', `fp_ssl`='', `fp_enable`='', `fp_adm`='', `fp_pass`='', `ssi`='', `php`='', `php_safe_mode`='true', `cgi`='', `perl`='', `python`='', `fastcgi`='', `miva`='', `coldfusion`='', `asp`='', `asp_dot_net`='', `webstat`='none', `at_domains`=''')
1: /usr/local/psa/admin/plib/class.Table.php:328
Table->update(array)
2: /usr/local/psa/admin/plib/class.cObject.php:347
cObject->update()
3: /usr/local/psa/admin/plib/class.PHosting.php:776
PHosting->update()
4: /usr/local/psa/admin/plib/class.PHostingManager.php:610
PHostingManager->update()
5: /usr/local/psa/admin/htdocs/domains/hosting/phosting_setup.php:217
 
It is something of the sql-mode. I had same case with a client and they have set these modes in my.cnf

sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

I believe it is caused but the STRICT_TRANS_TABLES
I commented that line , restarted mysql and it worked fine.
 
Back
Top