Before InnoDB, indexes would get corrupted, updates meant table locks—not just row locks, and there was no support for transactions. Since the advent of InnoDB we’ve come a long way. Sites that don’t use InnoDB are missing out on performance and stability gains. As part of our Launch Check for new sites, we check the engineRead more about Convert MySQL Tables From MyISAM to InnoDB[…]
After all these years of using Cpanel, I finally have had a disaster using Easyapache.
Here are my details:
OK, our high load server went down this evening and Apache was spitting out these “Too many open file” error messages. Then asking me to increase the file descriptors.
Note: We have over 7000 virtualhosts on this server, so that’s a lot of logfiles open! Before anyone says i’m crazy, I’m not. The server load is absolutely fine and it’s not even breaking a sweat. IO times are fine also.
Read more about Apache error – “Too many open files” …
When you add additional http authentication to the WordPress admin dashboard or the wp-admin directory, there are chances that you get any of the following errorr when trying to access the WordPress wp-admin directory; The page isn’t redirecting properly, This web page has a redirect loop, Error 310 (net::ERR_TOO_MANY_REDIRECTS) or an HTTP 404 error as seen in the below screenshot.
This guide is a companion to the Postfix, Dovecot, and MySQL installation guide. Because setting up a mail server is tricky, we’ve created this companion troubleshooting guide to help you work through and resolve any problems you might be experiencing. By the time you reach the end of this guide, you’ll know how to debug problems with your Postfix, Dovecot, and MySQL mail server.
The first section, Troubleshooting Checklist_, has a top-down approach to troubleshooting that will help you find specific errors for your mail server. The second section, Step-by-Step Configuration_, uses a bottom-up approach that shows you how to get a basic mail server functioning and then gradually add more features.
Recently when working on an OpenVZ container I was attempting to create a backup. While doing so I kept running into a problem where the server wouldn’t let me unmount the container in order to create the backup. The error you may see in this instance would say “Can’t umount /var/lib/vz/root/OpenVZID device or resource busy”, or “Can’t umount /var/lib/vz/root/100: Device or resource busy TASK ERROR: command ‘vzctl umount 100’ failed: exit code 51″, in this case the container being 100. Here’s how I was able to fix it …