Submitted by hescominsoon on Fri, 07/18/2014 - 17:44 Pro Licensee
I get the following error..it's some work and some don't./ This is right after the upgrade to the latest virtualmin. I need to move my stuff this weekend.
SQL show index from wp_wfNet404s failed : Can't find file: 'wp_wfNet404s' (errno: 2)
Status:
Closed (fixed)
Comments
Submitted by hescominsoon on Fri, 07/18/2014 - 17:51 Pro Licensee Comment #1
ok now it is occurring on all databases. I cannot access the databases using virtualmin at all now.
Submitted by hescominsoon on Fri, 07/18/2014 - 17:53 Pro Licensee Comment #2
Now it's back to some of them..something is really weird with this.
Submitted by andreychek on Fri, 07/18/2014 - 18:00 Comment #3
Howdy -- it looks like you're seeing a MySQL table issue there, that's not related to a Webmin or Virtualmin upgrade.
What you're seeing is an error being thrown by MySQL, while trying to access/export the tables.
Since you're using Virtualmin GPL, and you're not seeing a Virtualmin bug, the best place to help you out would be over in the Forums.
If you could, open up a new Forum post, and in that post, include the following --
What is the output of the command "mysql -V"?
What tool are you using that generates the above error?
If you use Virtualmin to generate backups for your domains, do those backups get created successfully? If not -- when was the most recent successful backup created?
Lastly -- what is the output of this command: "dmesg | tail -30"
If you could open up a new Forum post, and answer those questions there, that'd be super. Thanks!
Submitted by hescominsoon on Fri, 07/18/2014 - 19:27 Pro Licensee Comment #4
I am attempting to manage the databases with virtualmin...
Submitted by hescominsoon on Fri, 07/18/2014 - 19:29 Pro Licensee Comment #5
googling doesn't show much about this being a mysql error..and it only started with a 10k update to virtualmin that i instlaled right before this started..everything was working fine otherwise. Hence why i am starting the ticket here..only after upgrading to the latest virtualmin did this start.
Submitted by hescominsoon on Fri, 07/18/2014 - 19:31 Pro Licensee Comment #6
case in point. I tried to open gfcblog..it failed with the above error. I then waited 5 minutes and it worked. I highly doubt it's an issue with the databases.
Submitted by hescominsoon on Fri, 07/18/2014 - 19:33 Pro Licensee Comment #7
no backups randomly fail when that error gets thrown as the backup script tries to access the databases. I rna a backup a few hours ago before the latest version of virtualmin came out(it was a 10k patch). Something got broken.;
Submitted by andreychek on Fri, 07/18/2014 - 19:46 Comment #8
The errors you're seeing are errors being thrown by MySQL. You would see the same errors if you were using other tools, such as phpMyAdmin. Virtualmin uses standard MySQL tools, and standard SQL, to interact with the databases on your system.
Performing a Virtualmin upgrade doesn't affect your databases.
We can help you out, but the best place to do that is in the Forums. Let us know the answer to the above questions in a new Forum thread, and we can begin the troubleshooting process. Thanks!
Submitted by hescominsoon on Fri, 07/18/2014 - 19:57 Pro Licensee Comment #9
Well isn't that interesting....i got my backup done this time without error....i'll run it again and see if it barfs.
Submitted by hescominsoon on Fri, 07/18/2014 - 20:02 Pro Licensee Comment #10
sorry..but this ONLY STARTED after the last virtualmin upgrade...something in your code is not playing nice with mysql causing mysql to throw these errors. The chain of events points to this. I know you aren't going to investigate this now that i got my backups done....
Submitted by andreychek on Sat, 07/19/2014 - 00:28 Comment #11
We're sorry that you're experiencing problems, and we know it's frustrating.
We're not trying to ignore your concerns, but there's a few problems with what you're describing.
I just sent Joe and Jamie an email to verify this, but to my knowledge we haven't actually pushed out a Webmin or Virtualmin release since May.
However, even if there were one, the errors you're getting are indicating missing/corrupt data in MySQL.
Virtualmin just uses standard SQL statements, and in some cases uses MySQL-supplied tools such as "mysqldump".
If running SQL code generates any kind of data loss, that's points towards a MySQL bug, not a Virtualmin bug. It shouldn't be possible to execute SQL that causes data loss.
My concern is that you may be seeing some other kind of problem, one that just happened to start recently.
We're not saying that we won't look into it; but the best place to troubleshoot this with you is using the Forums, since it's unlikely to be a Virtualmin-specific issue. However, if we were to determine it was Virtualmin-related, we can certainly continue here in the support tracker.
If you notice MySQL-related problems again, please feel free to open up a new Forum thread, and let us know the answers to the above questions. We do monitor the Forums, along with lots of wonderful folks in the community. Thanks!