Posts

Showing posts from 2017

How to fix /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

I encountered several days ago this error on a fresh installed CentOS 6 – 64 bit machine while installing IBM LSF. This will happen only on 64 bit systems, the cause is the fact that 32 bit libraries are missing from the system, so you can easily fix this issue by installing the 32 bit libraries on your system. So if you encounter this error  /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory  this is how you can fix it: On any RPM based distribution (CentOS/RedHat/Fedora/Suse/Mandriva): yum -y install glibc.i686 On any DEB based distribution (Debian/Ubuntu/Mint/Crunchbang): apt-get update apt-get install ia32-libs

InfoSphere Information Server installer hangs

Problem(Abstract) InfoSphere Information Server (IS) installer hangs when you attempt to restart a failed installation attempt. Symptom IS installer simply hangs at the Installation screen. If you inspect the IS Install log, it is not updated. Cause IS installer hangs at a place where it finds an existing inprogress directory and it assumes that previous installation is still pending and tries to resume it with the help of response file, but it fails since there was no response file provided. Environment Restarting a previously failed IS install attempt without providing that response file. Diagnosing the problem IS Installer log contains the entries similar to below. 2015-06-30T10:56:49.98, SEVERE: com.ibm.is.install.atlasinstaller.ui.control.InstallEngineMonitor com.ibm.is.install.exception.InstallException: java.lang.NullPointerException at com.ibm.is.install.AbstractInstaller.checkInprogressDirEx...

pnp4Nagios Installation configuration Step by step Guide

Image
Pnp4Nagios is an tool which will store performance data into RRD (Round Robin Database) and show in graphical representation. Its easy to understand and represent the values in graphs. Let's see pnp4nagios installation configuration Step by Step guide. Perf Data Flow to RRD Database is below pnp4nagios data flow There are three modes of data collection Using pnp4nagios Default mode Bulk Mode Bulk with NPCD mode Configure   Local Yum Repository   and Install rrdtool necessary (dependency)  # yum install rrdtool # yum install ruby xorg-x11-fonts-Type1 rrdtool verification # cd /tmp # wget https://sourceforge.net/projects/pnp4nagios/files/PNP-0.6/pnp4nagios-0.6.25.tar.gz # tar -xvf pnp4nagios-0.6.25 # cd pnp4nagios-0.6.25 # ./configure --with-rrdtool=/usr/bin/rrdtool pnp4nagios installation Note:   Do not download pnp-0.4-14 which does not work properly Download pnp4nagios # make all # make fullinstall Sure that No errors while installing  Edit the /usr/local/nagios/etc/nagios....

How to manually checkpoint Secondary Name Node

There are scenarios when checkpointing fails ( due to various reasons, for example network issues ). In those cases we can manually run checkpointing to allow NameNode and Secondary NameNode to sync in the metadata. Manual steps to checkpoint is as below: 1. On primary NameNode, we will try to save latest metadata to the fsimage as : hdfs dfsadmin -safemode enter   hdfs dfsadmin -saveNamespace   hdfs dfsadmin -safemode leave  2. we will now run manual checkpointing:  Stop secondary NN or HDFS service or Cluster . Now execute following command on the Secondary NameNode: mv /data/dfs/snn /data/dfs/snn.old hdfs secondarynamenode -checkpoint force Start the SNN  or HDFS service or Cluster   .

Collibra DGC installation error Could not initialize class java.awt.Toolkit

root@dgc:~# ./dgc_linux_5_2_1-FINAL.sh Unpacking JRE ... Preparing JRE ... Starting Installer ... java.lang.NoClassDefFoundError: Could not initialize class java.awt.Toolkit         at java.awt.Component.<clinit>(Component.java:593)         at javax.swing.ImageIcon$2.run(ImageIcon.java:130)         at javax.swing.ImageIcon$2.run(ImageIcon.java:128)         at java.security.AccessController.doPrivileged(Native Method)         at javax.swing.ImageIcon.createNoPermsComponent(ImageIcon.java:127)         at javax.swing.ImageIcon.access$000(ImageIcon.java:69)         at javax.swing.ImageIcon$1.run(ImageIcon.java:103)         at javax.swing.ImageIcon$1.run(ImageIcon.java:100)         at java.security.AccessController.doPrivileged(Native Method)         at javax.swing.ImageIcon.<clinit>(ImageIcon.java:100)         at com.install4j.runtime.installer.frontend.GUIHelper.loadIcon(GUIHelper.java:175)         at com.install4j.runtime.installer.frontend.GUIHelper.<clinit>(GUIHelper....

Why no more “python-support” in 16.04?

Had the same issue when trying to install GateOne on 16.04. Solved it with: wget http :// launchpadlibrarian . net / 109052632 / python - support_1 . 0.15 _all . deb sudo dpkg - i python - support_1 . 0.15 _all . deb Source:  https://github.com/ajenti/ajenti/issues/903#issuecomment-215569332

Install and Configure Jenkins thinBackup and Upgrade Jenkins

Image
Today I get opportunity to upgrade jenkins,  Jenkins  is a very important tool for continuous integration and continuous delivery. All the Jenkins data i.e, jobs and configs are stored in JENKINS_HOME directory. Taking a periodic backup of JENKINS_HOME directory is one the best practice of Jenkins Managment. Jenkins can be extended with plugins for extra features. There is a plugin called Jenkins  thinBackup Plugin . This helps in automate the backup of JENKINS_HOME Directory. Install and Configure Jenkins thinBackup Plugin for Backup Strategy Steps to Install the thinBackup Plugin. 1) Go to Manage Jenkins 2) Click Manage Plugins 3) Under Available Plugins tab select ThinBackup 4) Click on Install without restart button. Steps to Configure thinBackup Plugin 1) Go to Manage Jenkins 2) Click thinBackup option 3) Click settings to configure the backup options as shown below. 4) Schedule the automated backups as shown sample below. All the configuration is self-explanatory. Download New Je...

Shrinking AWS EC2 root EBS volume

When you wish to shrink an EBS root volume, you will need to start a new, small EC2 instance that you can attach the volume you wish to resize. A t2.micro instance should be more than sufficient for this task. Once you have this instance created, proceed with the following steps. Take a backup Create a new EBS volume that is the size you wish to shrink to, do this by creating a new t2.micro EC2 instance...ensure delete on termination is not enabled. After instance is created you will have an EBS volume that is partitioned and has valid boot partition. Terminate the temporary instance. Detach the volume you wish to resize from the current EC2 instance and attach both volumes to the new, small EC2 instance you created Mount the old volume as /dev/sdf (this becomes /dev/xvdf) Mount the new volume as /dev/sdg (this becomes /dev/xvdg) Power on the new, small instance and wait for it to come online SSH into the instance and run the following commands To ensure that the file...