• 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.

Resolved Backup fails

Nicola Urbinati

Basic Pleskian
Hi,

I have the following problems during backup:
Warning: Database "dreamlordpress_dlp"
Unable to make database dump. Error: Failed to exec mysqldump: mysqldump: Couldn't execute 'SHOW FIELDS FROM `tmp_view`': View 'tmp_db.tmp_view' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them (1356)
Warning: Extension "Patchman automatic integration"
Unable to back up data. Error: Failed to create archive: Transport error: File or dir not exists

How can I resolve them?

Thank you.
 
I have no solution for either issue, but this might help you for further investigation:

Database issue: "Views" are sometimes limited to only being able to be read and used by a specific user. When the backup system tries to read these data with its "admin" user it might fail. They can only be accessed by the "root" user, however that is not used in Plesk. You might want to try to change the views in a way that they allow other users to access them, including the database user named "admin".

Extension issue: In another thread something similar was mentioned recently. Here it was advised that probably the extension has its files not in the expected locations/paths, but this error does not do any harm to the integrity of the backup.
 
Actually, found out that the wordpress DB underlying the view actually changed the name of a table column, breaking the view.

I now dropped the view as not really necesary.

Thank you very much, I'll also be more watchful to premissions next time.
 
Back
Top