I know my site doesn’t have any advertisements and I like to keep it that way, so my users aren’t distracted by annoying ads that might not interest them anyway. With that being said, I created this post to advertise 3 games the company I work for, indiePub, has developed, and hopefully I can get my users, you, to download these games and support us. 2 of these games are free and won’t cost you anything, and the other is a paid game. All 3 games are worth your time and I really appreciate it if you could at least download the free ones.
This is another quick tutorial, this time I’ll show you how to configure your server to allow zabbix to monitor Nginx and PHP-FPM. This tutorial assumes you’ve already installed zabbix on your monitoring server and also the server to be monitored. For simplicity sake, let’s call your zabbix server (the one doing the monitoring) zabbix_mon and let’s call the server you would like to monitor, server1. Zabbix is an open source monitoring solution available here, Nginx is an httpd and reverse proxy server, found here and php-fpm is an alternative PHP FastCGI found here.
Ok, with that out of the way, let set this up.
This is another quick one. I wanted to insert a JSON array into MySQL with a single insert and, on duplicate key update. This is how you get it done:
Say you have a JSON array like this:
JMeter is an open source application written in Java, developed by the folks from The Apache Software Foundation, which allows one to perform load tests against their webservers.
JMeter allows you to run tests from you workstation against your servers, but you can also setup virtual test servers that would allow you to run a heavier load.
If you run JMeter from your machine, you’ll probably end up consuming tons of cpu and memory, depending on how large your tests are, so, to avoid that, you can seetup your workstation as a JMeter MASTER and any number of virtual machines as JMeter SLAVES, which you will be able to control from your workstation. This setup is called Distributed JMeter Testing and that is what I’ll walk you through in this tutorial.
To continue from where I’ve left off on my previous post, this time we’ll setup heartbeat to monitor both of our load balancers, thus allowing us to have what one may call high availability/ failover, between both our load balancers. This method can be used on any server you wish, you can for example have Heartbeat monitor mysql, apache or any other server. In this example, we’ll set up Heartbeat to monitor our crossroads load balancer.