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

Error dropping database

vuong184

New Pleskian
Hello everyboy!

I'm a newbie using plesk 12 for vps linux. I'm using server at server4you.com with panel is plesk 12 for centos 6.
I have a problem with deleted database is can't delete it and error is:
Error dropping database (can't rmdir './911tool/', errno: 17)
Search for related Knowledge Base articles
Please help me delete a database not user. and when i login Webadmin i have a error from PhpMyadmin:
Welcome to phpMyAdmin

You probably did not create a configuration file. You might want to use the setup script to create one.

Error
MySQL said:

Cannot connect: invalid settings.
Please help me login to phpmyadmin and backup database.

Thanks!
 
@vuong184 This code means "file exists". In most cases the directory contains some MySQL file that MySQL doesn't feel about deleting. Such files could have been created by a SELECT ... INTO OUTFILE "filename"; command where filename had no path. In this case, the MySQL process creates them in its current working directory, which is the data directory of the database, e.g. /var/lib/mysql/data/nameofdatabase or by another reason. Or it could be another file in /var/lib/mysql/nameofdatabase

Move the file(s) from console outside (or delete if not needed) and retry. Also, determine why they were created in the first place - it could point to a bug in some application.
 
Back
Top