Nagios on RHEL 6


For nagios configuration you can click here

Comments

Post a Comment

Popular posts from this blog

Managine Hadoop Cluster

If you are working on Hadoop, you’ll realize there are several shell commands available to manage your Hadoop cluster.  Hadoop administration commands. 1. Name node Commands Command Description hadoop namenode -format Format HDFS filesystem from Namenode hadoop namenode -upgrade Upgrade the NameNode start-dfs.sh Start HDFS Daemons                        stop-dfs.sh Stop HDFS Daemons start-mapred.sh Start MapReduce Daemons stop-mapred.sh Stop MapReduce Daemons hadoop namenode -recover -force Recover namenode metadata after a cluster failure (may lose data) 2. fsck Commands Command Description hadoop fsck / Filesystem check on HDFS hadoop fsck / -files Display files duri...
Read more

Difference between Soft Mount & Hard Mount

The directory /nfs   should be created in your node/server. The nfs mount can be mount as a “soft mount” or as a “hard mount” these mount option define the how the nfs client should be handle nfs crash/failure . We will see the difference between hard mount and soft mount. Soft mount :- suppose you have mount the nfs by using “ soft mount’ when a program request a file from nfs server. Nfs demon will try to retrieve the data from the nfs server. If doesn’t get any response from nfs server due to some failure or crash on nfs server. Then nfs client report an error to the process on the client machine requesting the file access the Advantage “fast responsiveness”   it doesn’t wait to the nfs server to respond. The Main Disadvantage of this method is data corruption or loss of data so this is not the recommended option to use.  [root@sadeek ~]# showmount -e 172.28.50.109 Export list for 192.168.0.105: /nfs * Soft mounting (Temporary Mounting)...
Read more

VENOM Vulnerability

How to Patch and Protect Linux Server against the VENOM Vulnerability # CVE-2015-3456 A very serious security problem has been found in the virtual floppy drive QEMU's code used by many computer virtualization platforms including Xen, KVM, VirtualBox, and the native QEMU client. It is called VENOM vulnerability. How can I fix VENOM vulnerability and protect my Linux server against the attack? How do I verify that my server has been fixed against the VENOM vulnerability? This is tagged as high severity security bug and it was announced on 13th May 2015. The VENOM vulnerability has existed since 2004, when the virtual Floppy Disk Controller was first added to the QEMU codebase. Since the VENOM vulnerability exists in the hypervisor’s codebase, the vulnerability is agnostic of the host operating system (Linux, Windows, Mac OS, etc.). What is the VENOM security bug (CVE-2015-3456)? An out-of-bounds memory access flaw was found in the way QEMU's virtual Floppy Disk Controller (F...
Read more