Friday, 11 July 2014

Best budget phone gets even better with 4G LTE, but a little pricier too

The Good The Motorola Moto G has one of the best screens you can get for the price, plenty of power for the everyday essentials, an easy to use, near-stock version of Android KitKat and the addition of 4G LTE and expandable storage are extremely welcome.
The Bad The camera isn't up to anything more than the odd snap in good lighting, and the addition of 4G LTE means its once "unbelievable bargain" price is now only "good value".
The Bottom Line Although the Motorola Moto G with 4G LTE is a bit pricier than its 3G-only sibling, it still has one of the best displays in the budget arena, its processor makes operation enjoyably smooth and its rounded, compact body is both comfortable and attractive. If you're after an affordable all-round entrance into the high speeds of 4G, you've come to the right place.
With the Moto G, Motorola threw a giant spanner in the works of the mobile world. Its lineup of mid-range specs were paired with an amazingly low price, making it the best value phone by a country mile. It made reviewing phones somewhat repetitive -- time after time I was forced to conclude, "This phone is fine, but the Moto G offers the same performance for much less money."
Its only downsides were a lack of expandable storage and no 4G LTE. In the UK, that wasn't much of a problem as 4G was still very new and still rather expensive. In the US, 4G was much more common, so its omission was more of an issue. Motorola has rectified both, adding 4G and a microSD card slot to this new revamped version of the Moto G.
It remains the same in every other respect, except price -- you still get the best screen at the price, a very capable quad-core processor, a 5-megapixel camera and the latest version of Android, 4.4.3 KitKat.
It's on sale now in the UK for free on contracts starting from £19 per month at retailers such as Phones 4U, or SIM-free for £149 with 8GB of built-in storage from Amazon. In the US, you can get the phonedirectly from Motorola's online store for $219 off-contract. In Australia, the Moto G is AU$299 -- just AU$50 more than the non-4G original.
That's a small increase on the 3G Moto G's price of £119 or $179 unlocked, with the older version continuing to be on sale alongside the new one. Motorola also has another new phone for you, though, and it's even cheaper: the $130/£90/AU$179 Moto E. You can read all about the Moto E here.

Design and display

Although it now packs a 4G LTE radio inside, the Moto G remains physically unchanged. I found the older Moto G's 4.5-inch body to be very comfortable to hold, thanks to its curved back, which fits snugly into your palm. The new model is exactly as comfortable. It's also not so big as to make you dislocate your thumb every time you try to type with one hand.
The plastic back panels are interchangeable and there are a host of different colours available, along with ruggedised cases and flip covers that protect the screen. The Moto G is also now in white, although the white model is not quite as widely available. I was keen on the new hue at the launch event -- it definitely brightens it up, particularly when it's paired with a light-coloured back, so I'm hoping it becomes easier to get hold of soon.
Underneath the swappable cover is the microSD card slot. The lack of expandable storage was a disappointment on the older Moto G, as it was only available with 8 or 16GB. While 16GB is probably adequate for most people, if you were shopping on a budget and only wanted to spring for the 8GB model, you'd quickly find yourself running out of space once you've downloaded your favourite apps and songs. The new model comes with only 8GB, but with the option to pop in 32GB microSD cards (available for around £10, or $15), storage shouldn't be an issue.
The 4.5-inch display has a 1,280x720-pixel resolution, giving a really good density of 326 pixels per inch. Couple that with its high brightness, vivid colours and decent viewing angles, and the Moto G has easily the best screen available on a budget phone.
Motorola doesn't seem to have fiddled with the display on the 4G model, which still looks every bit as crisp and bold as before, outperforming similar budget 4G phones such as the EE Kestrel (which is UK-only) and the Nokia Lumia 635. Both those phones can be picked up for £100 (around $170, although US prices are yet to be confirmed), which is a decent chunk of cash.

Android KitKat software

The Moto G first launched last year with Android 4.3 Jelly Bean on board, but was updated to 4.4.2 KitKat in January. The 4G model comes with KitKat as standard, with new features such as the ability to display video and games at full screen without the navigation buttons taking up space. It also lets you search for local businesses directly from the contacts app.
Unlike most manufacturers, who like to put their own stamp on Android, Motorola has done very little to the interface. In fact, it's pretty much stock Android, so if you've ever used an Android device before, there'll be nothing new here for you to get your head around. The G does have a couple of additions, including Motorola Assist, which performs set tasks such as automatically silencing your phone when you have a meeting scheduled.
Thanks to the almost complete lack of any interface tweaks by Motorola, the Android experience is extremely easy to get to grips with, whether you're an Android veteran or completely new to the smartphone world.

Processor and battery performance

The 4G Moto G has the same Qualcomm Snapdragon 400 processor as the previous version. It's a 1.2GHz quad-core affair, backed up by 1GB of RAM, and I found it to be more than powerful enough for most common tasks. Instagramming food and sending horrific selfies over WhatsApp were handled without any issue.
It turned its hand to demanding games like Asphalt 8 fairly well, although frame rates did drop at times -- more basic games like Cut The Rope are well within its capabilities.
General navigation is swift too, thanks in part to Motorola's software tweaks, which the company reckons make the phone extremely efficient with its power resources. Whatever it's done, it's worked -- apps and menus open quickly and the camera starts up and is ready to shoot in only a couple of seconds.
Inside is a 2,070mAh battery, which is the same size cell you'll find in the regular Moto G. That's a little concerning, as 4G LTE is a larger power drain than 3G. After looping an hour and a half of YouTube video streamed over 4G, the power had dropped from full to 74 percent remaining, which is fairly average. I've seen similar efforts from 3G-only phones, so the added 4G doesn't seem to have had a massive impact on battery life.
If you spend the day streaming TV shows over Netflix or playing online games like Shadowgun over 4G, you should expect to give the battery a boost in the afternoon if you want any power left to call a cab after the pub. If you're cautious with your use -- keep Wi-Fi and GPS off, avoid demanding tasks and keep the screen brightness down -- you should be able to get a full day of use out of it.

Camera

The back is home to a 5-megapixel camera, which again has remained unchanged from the original Moto G. Its results are generally unimpressive. My test shots were often underexposed, and the HDR mode gave some shots a high-contrast, unnatural look. The low resolution means that there's an overall lack of clarity and sharpness. Below are a selection of my tests.
st-pauls-moto-g-4g.jpg
Motorola Moto G camera testAndrew Hoyle/CNET
st-pauls-hdr-moto-g-4g.jpg
Motorola Moto G camera test with HDRAndrew Hoyle/CNET
river-moto-g-4g.jpg
Motorola Moto G camera testAndrew Hoyle/CNET
river-hdr-moto-g-4g.jpg
Motorola Moto G camera test with HDRAndrew Hoyle/CNET
flowers-moto-g-4g.jpg
Motorola Moto G camera testAndrew Hoyle/CNET
flowers-hdr-moto-g-4g.jpg
Motorola Moto G camera test with HDRAndrew Hoyle/CNET
img20140627114635413.jpg
Motorola Moto G camera testAndrew Hoyle/CNET
img20140627120721972.jpg
Motorola Moto G camera testAndrew Hoyle/CNET
pub-moto-g-4g.jpg
Motorola Moto G camera testAndrew Hoyle/CNET
If you're out in the park with your friends, bathed in glorious sunshine, then the phone should be able to get some snaps good enough to make your office-bound Facebook friends jealous. Even so, this is not a phone to go for if photography is important to you. The camera interface is, at least, extremely simple to use. There are very few settings, so it's really a case of pointing it at your subject and tapping the screen. Settings like HDR are hidden out of the way when not in use.

Conclusion

With its decent specs and rock-bottom price, the Motorola Moto G was already a fantastic bargain, not only outpacing its low-end rivals, but offering much more than most mid-range mobiles. The addition of 4G LTE and expandable storage addresses our two original quibbles with the Moto G.
There's been a small price increase, meaning it doesn't have the same bargain bragging rights as its 3G-only sibling. With its excellent display, easy to use version of Android KitKat, expandable storage and comfortable design however, it's one of the best all-round budget phones you can get. It's certainly worth a look if you're after a 4G phone without a top-end price.


source: http://www.cnet.com/products/motorola-moto-g-4g-lte/2/

How to Add Linux Host to Nagios Monitoring Server Using NRPE Plugin

In our first part of this article, we’ve explained in detail on how to install and configure latestNagios Core 4.0.1 on CentOS 6.4 server. In this article we will show you how to addRemote Linux machine and it’s services to Nagios Monitoring host using NRPE agent.
We hope you already having Nagios installed and running properly. If not, please use the following installation guide to install it on the system.
  1. Nagios 4.0.1 Installation Guide on RHEL/CentOS 6.x/5.x & Fedora 19/18/17
  2. How to Add Windows Host to Nagios Monitoring Server
Once you’ve installed, you can proceed further to install NRPE agent on your Remote Linuxhost. Before heading further, let us give you a short description about NRPE.

What is NRPE?

The NRPE (Nagios Remote Plugin Executor) plugin allows you to monitor any remoteLinux/Unix services or network devices. This NRPE add-on allows Nagios to monitor any local resources like CPU loadSwapMemory usageOnline users, etc. on remote Linux machines. After all, these local resources are not mostly exposed to external machines, anNRPE agent must be installed and configured on the remote machines.
Note: The NRPE addon requires that Nagios Plugins must be installed on the remote Linux machine. Without these, the NRPE daemon will not work and will not monitor anything.

Installation of NRPE Plugin

To use the NRPE, you will need to do some additional tasks on both the Nagios Monitoring Host and Remote Linux Host that the NRPE installed on. We will be covering both the installation parts separately.
We assume that you are installing the NRPE on a host that supports TCP wrappers andXinted daemon installed on it. Today, most of the modern Linux distributions have these two installed by default. If not, we will install it later during the installation when required.

On Remote Linux Host

Please use the below instructions to install Nagios Plugins and NRPE daemon on theRemote Linux Host.
Step 1: Install Required Dependencies
We need to install required libraries like gccglibcglibc-common and GD and its development libraries before installing.
[root@tecmint]# yum install -y gcc glibc glibc-common gd gd-devel make net-snmp openssl-devel
Step 2: Create Nagios User
Create a new nagios user account and set a password.
[root@tecmint]# useradd nagios
[root@tecmint]# passwd nagios
Step 3: Install the Nagios Plugins
Create a directory for installation and all its future downloads.
[root@tecmint]# cd /root/nagios
Now download latest Nagios Plugins 1.5 package with wget command.
[root@tecmint nagios~]# wget https://www.nagios-plugins.org/download/nagios-plugins-1.5.tar.gz
Step 4: Extract Nagios Plugins
Run the following tar command to extract the source code tarball.
[root@tecmint nagios~]# tar –xvf nagios-plugins-1.5.tar.gz
After, extracting one new folder will appear in that directory.
[root@tecmint nagios ~]# ll

drwxr-xr-x 15    200    300    4096 Oct  2 20:57 nagios-plugins-1.5
-rw-r--r--  1 root   root   2428258 Oct  2 20:57 nagios-plugins-1.5.tar.gz
Step 5: Compile and Install Nagios Plugins
Next, compile and install using following commands
[root@tecmint nagios]# cd nagios-plugins-1.5
[root@tecmint nagios]# ./configure 
[root@tecmint nagios]# make
[root@tecmint nagios]# make install
Set the permissions on the plugin directory.
[root@tecmint nagios]# chown nagios.nagios /usr/local/nagios
[root@tecmint nagios]# chown -R nagios.nagios /usr/local/nagios/libexec
Step 6: Install Xinetd
Most of the systems, its by default installed. If not, install xinetd package using following yumcommand.
[root@tecmint nagios]# yum install xinetd
Step 7: Install NRPE Plugin
Download latest NRPE Plugin 2.15 packages with wget command.
[root@tecmint]# cd /root/nagios
[root@tecmint]# wget http://garr.dl.sourceforge.net/project/nagios/nrpe-2.x/nrpe-2.15/nrpe-2.15.tar.gz
Unpack the NRPE source code tarball.
[root@tecmint]# tar xzf nrpe-2.15.tar.gz
[root@tecmint]# cd nrpe-2.15
Compile and install the NRPE addon.
[root@tecmint]# ./configure
[root@tecmint]# make all
Next, install the NRPE plugin daemon, and sample daemon config file.
[root@tecmint]# make install-plugin
[root@tecmint]# make install-daemon
[root@tecmint]# make install-daemon-config
Install the NRPE daemon under xinetd as a service.
[root@tecmint]# make install-xinetd
Now open /etc/xinetd.d/nrpe file and add the localhost and IP address of the Nagios Monitoring Server.
only_from = 127.0.0.1 localhost <nagios_ip_address>
Next, open /etc/services file add the following entry for the NRPE daemon at the bottom of the file.
nrpe            5666/tcp                 NRPE
Restart the xinetd service.
[root@tecmint]# service xinetd restart
Step 8: Verify NRPE Daemon Locally
Run the following command to verify the NRPE daemon working correctly under xinetd.
[root@tecmint]# netstat -at | grep nrpe

tcp        0      0 *:nrpe                      *:*                         LISTEN
If you get output similar to above, means it working correctly. If not, make sure to check the following things.
  1. Check you’ve added nrpe entry correctly in /etc/services file
  2. The only_from contains an entry for “nagios_ip_address” in the /etc/xinetd.d/nrpefile.
  3. The xinetd is installed and started.
  4. Check for the errors in the system log files for about xinetd or nrpe and fix those problems.
Next, verify the NRPE daemon is functioning properly. Run the “check_nrpe” command that was installed earlier for testing purposes.
[root@tecmint]# /usr/local/nagios/libexec/check_nrpe -H localhost
You will get a following string on the screen, it shows you what version of NRPE is installed:
NRPE v2.15
Step 9: Configure Firewall Rules
Make sure that the Firewall on the local machine will allow the NRPE daemon to be accessed from remote servers. To do this, run the following iptables command.
[root@tecmint]# iptables -A INPUT -p tcp -m tcp --dport 5666 -j ACCEPT
Run the following command to Save the new iptables rule so it will survive at system reboots.
[root@tecmint]# service iptables save
Step 10: Customize NRPE commands
The default NRPE configuration file that got installed has several command definitions that will be used to monitor this machine. The sample configuration file located at.
[root@tecmint]# vi /usr/local/nagios/etc/nrpe.cfg
The following are the default command definitions that are located at the bottom of the configuration file. For the time being, we assume you are using these commands. You can check them by using the following commands.
# /usr/local/nagios/libexec/check_nrpe -H localhost -c check_users

USERS OK - 1 users currently logged in |users=1;5;10;0
# /usr/local/nagios/libexec/check_nrpe -H localhost -c check_load

OK - load average: 3.90, 4.37, 3.94|load1=3.900;15.000;30.000;0; load5=4.370;10.000;25.000;0; load15=3.940;5.000;20.000;0;
# /usr/local/nagios/libexec/check_nrpe -H localhost -c check_hda1

DISK OK - free space: /boot 154 MB (84% inode=99%);| /boot=29MB;154;173;0;193
# /usr/local/nagios/libexec/check_nrpe -H localhost -c check_total_procs

PROCS CRITICAL: 297 processes
# /usr/local/nagios/libexec/check_nrpe -H localhost -c check_zombie_procs

PROCS OK: 0 processes with STATE = Z
You can edit and add new command definitions by editing the NRPE config file. Finally, you’ve successfully installed and configured NRPE agent on the Remote Linux Host. Now it’s time to install a NRPE component and add some services on your Nagios Monitoring Server

On Nagios Monitoring Server

Now login into your Nagios Monitoring Server. Here you will need to do following things:
  1. Install the check_nrpe plugin.
  2. Create a Nagios command definition using the check_nrpe plugin.
  3. Create Nagios host and add service definitions for monitoring the remote Linux host.
Step 1: Install NRPE Plugin
Go to the nagios download directory and download latest NRPE Plugin with wget command.
[root@tecmint]# cd /root/nagios
[root@tecmint]# wget http://garr.dl.sourceforge.net/project/nagios/nrpe-2.x/nrpe-2.15/nrpe-2.15.tar.gz
Unpack the NRPE source code tarball.
[root@tecmint]# tar xzf nrpe-2.15.tar.gz
[root@tecmint]# cd nrpe-2.15
Compile and install the NRPE addon.
[root@tecmint]# ./configure
[root@tecmint]# make all
[root@tecmint]# make install-daemon
Step 2: Verify NRPE Daemon Remotely
Make sure that the check_nrpe plugin can communicate with the NRPE daemon on the remote Linux host. Add the IP address in the command below with the IP address of your Remote Linux host.
[root@tecmint]# /usr/local/nagios/libexec/check_nrpe -H <remote_linux_ip_address>
You will get a string back that shows you what version of NRPE is installed on the remote host, like this:
NRPE v2.15
If your receive a plugin time-out error, then check the following things.
  1. Make sure your firewall isn’t blocking the communication between the remote host and the monitoring host.
  2. Make sure that the NRPE daemon is installed correctly under xinetd.
  3. Make sure that the remote Linux host firewall rules blocking the monitoring serverfrom communicating to the NRPE daemon.

Adding Remote Linux Host to Nagios Monitoring Server

To add a remote host you need to create a two new files “hosts.cfg” and “services.cfg” under “/usr/local/nagios/etc/” location.
[root@tecmint]# cd /usr/local/nagios/etc/
[root@tecmint]# touch hosts.cfg
[root@tecmint]# touch services.cfg
Now add these two files to main Nagios configuration file. Open nagios.cfg file with any editor.
[root@tecmint]# vi /usr/local/nagios/etc/nagios.cfg
Now add the two newly created files as shown below.
# You can specify individual object config files as shown below:
cfg_file=/usr/local/nagios/etc/hosts.cfg
cfg_file=/usr/local/nagios/etc/services.cfg
Now open hosts.cfg file and add the default host template name and define remote hosts as shown below. Make sure to replace host_namealias and address with your remote host server details.
[root@tecmint]# vi /usr/local/nagios/etc/hosts.cfg
## Default Linux Host Template ##
define host{
name                            linux-box               ; Name of this template
use                             generic-host            ; Inherit default values
check_period                    24x7        
check_interval                  5       
retry_interval                  1       
max_check_attempts              10      
check_command                   check-host-alive
notification_period             24x7    
notification_interval           30      
notification_options            d,r     
contact_groups                  admins  
register                        0                       ; DONT REGISTER THIS - ITS A TEMPLATE
}

## Default
define host{
use                             linux-box               ; Inherit default values from a template
host_name                       tecmint          ; The name we're giving to this server
alias                           CentOS 6                ; A longer name for the server
address                         5.175.142.66            ; IP address of Remote Linux host
}
Next open services.cfg file add the following services to be monitored.
[root@tecmint]# vi /usr/local/nagios/etc/services.cfg
define service{
        use                     generic-service
        host_name               tecmint
        service_description     CPU Load
        check_command           check_nrpe!check_load
        }

define service{
        use                     generic-service
        host_name               tecmint
        service_description     Total Processes
        check_command           check_nrpe!check_total_procs
        }

define service{
        use                     generic-service
        host_name               tecmint
        service_description     Current Users
        check_command           check_nrpe!check_users
        }

define service{
        use                     generic-service
        host_name               tecmint
        service_description     SSH Monitoring
        check_command           check_nrpe!check_ssh
        }

define service{
        use                     generic-service
        host_name               tecmint
        service_description     FTP Monitoring
        check_command           check_nrpe!check_ftp
        }
Now NRPE command definition needs to be created in commands.cfg file.
[root@tecmint]# vi /usr/local/nagios/etc/objects/commands.cfg
Add the following NRPE command definition at the bottom of the file.
###############################################################################
# NRPE CHECK COMMAND
#
# Command to use NRPE to check remote host systems
###############################################################################

define command{
        command_name check_nrpe
        command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$
        }
Finally, verify Nagios Configuration files for any errors.
[root@tecmint]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Total Warnings: 0
Total Errors:   0
Restart Nagios:
[root@tecmint]# service nagios restart
That’s it. Now go to Nagios Monitoring Web interface at “http://Your-server-IP-address/nagios” or “http://FQDN/nagios” and Provide the username “nagiosadmin” andpassword. Check that the Remote Linux Host was added and is being monitored.
Nagios Remote Host Monitoring
Nagios Remote Host Monitoring
That’s it! for now, in our my up-coming article I will show you how to add Windows host toNagios monitoring Server. If you’re facing any difficulties while adding remote host toNagios. Please do comment your queries or problem via comment section, till then stay tuned to Tecmint.com for more such valuable articles.


#Source : http://www.tecmint.com/how-to-add-linux-host-to-nagios-monitoring-server/