Creating Cron Jobs in Windows 10 and Windows Server 2016

I recently made the switch from a Linux LAMP server to a Windows Server 2016.  It didn’t take me too long to figure out I forgot to transfer my cron jobs for my PHP pages. I went to start the transfer and I soon realized that Windows does not support cron jobs. However, I did find the Windows version of Cron jobs. Below is what I did to create these cron jobs so my PHP crons will continue run on schedule. This trick will really work in all versions of Windows, but you must get to it different methods.

Continue reading “Creating Cron Jobs in Windows 10 and Windows Server 2016”

How to start your own blog

When you are looking to start a blog of your own, it can seem like a daunting task. In reality, if you take it one step at a time and with the right instructions, you can easily create your own blog in just a couple minutes. The hardest part is choosing your website name and creating content. But if you are serious about it, in just a few minutes you can be on your way to creating your first blog post.

Step 1 – Choose a provider

The first thing you want to do is pick out a hosting provider. A hosting provider is who will actually store the files for the website and who will make it available for people on the internet.

I, myself, am a hosting provider, therefore I host my own sites. If you are interested in using me as your hosting provider, you can signup at https://axelwebhosting.com and use the coupon code “1STMONTHHALF” and you get your first month 50% off. This tutorial will show you how to setup a WordPress blog on my hosting platform using the WordPress easy installer. Continue reading “How to start your own blog”

DigitalOcean VPS Hosting Review

I have been using DigitalOcean for nearly 6 months now to host my websites and online services. They are a premium Virtual Private Hosting provider that offers many types of configurations in many geographic regions. In 55 seconds, you can have a VPS created and up and running with you ready to login and start hosting. DigitalOcean has many features to offer and they are always expanding on their features:

Continue reading “DigitalOcean VPS Hosting Review”

MySQL – Too many files open

I run my servers on CentOS using cPanel/WHM. When I first started running my own server, it did not take long for me to see how little I know about Linux. I had a funky problem with my MySQL dropping out after so much time. It seemed like the more people I had on my sites, the faster it would go down. But after I rebooted the server, it all started working fine again… For a while anyway.

I got to looking around to see if there is a error log for MySQL. And sure enough there is. By default, the error log is located at:

/var/lib/mysql/**HOSTNAME**.err

The **HOSTNAME** would be your server’s hostname, (if you do not know your hostname, simply use the command “hostname” and it will output your hostname)

To view the last 500 lines of your error log, simply use:

tail -500 /var/lib/mysql/**HOSTNAME**.err

In my error log, I began to see this:

130925 12:39:23 [ERROR] Error in accept: Too many open files
130925 12:43:39 [ERROR] Error in accept: Too many open files
130925 12:47:55 [ERROR] Error in accept: Too many open files
130925 12:52:11 [ERROR] Error in accept: Too many open files
130925 12:56:27 [ERROR] Error in accept: Too many open files
130925 13:00:43 [ERROR] Error in accept: Too many open files
130925 13:04:59 [ERROR] Error in accept: Too many open files
130925 13:09:15 [ERROR] Error in accept: Too many open files
130925 13:13:31 [ERROR] Error in accept: Too many open files
130925 13:17:47 [ERROR] Error in accept: Too many open files
130925 13:22:03 [ERROR] Error in accept: Too many open files
130925 13:26:19 [ERROR] Error in accept: Too many open files
130925 13:30:35 [ERROR] Error in accept: Too many open files

 

Did a little bit of googling, and discovered that by default, centOS has a hard limit of the amount of files that can be opened at a time, which causes MySQL to error out until you reboot the server. However, this can be fixed by running the doing the following:

nano /etc/sysctl.conf

Add this line at the bottom of the config file:

fs.file-max = 100000

 

Save and close the file, then reboot the server.

After you rebbot your server, you will want to run the following command to verify that your settings was saved and correct:

sysctl fs.file-max

If it reads 10000, then your server is now ready to handle MySQL!