Home
Analytics
ihub startup failure
rmwalker
<p>I installed iHub f-type on a linux AWS ec2 instance. It seemed to start fine, but per netstat, it isn't listening on port 8700. I verified that the port is open, but none of the logs I could find showed a problem. Any tips?</p>
Find more posts tagged with
Comments
Clement Wong
<p>The process running on port 8700 is Tomcat, the front-end for iHub. Do you have the other iHub internal process listening on port 8000 or 8432?</p>
<p> </p>
<p>Under /BIRTiHubFType/BIRTiHub/iHub/data/server/log, please check to see if you have an ihubd.pid.hostname.datetimestamp.log file? Or a startsrvr.log? If so, please ZIP up that log directory and you can send that to me so that I can see if there are any issues.</p>
<p> </p>
<p>The BIRT iHub F-Type Quick Start for Linux Guide is here (@ <a data-ipb='nomediaparse' href='
http://www.actuate.com/download/quick-start-install-ftype-linux.pdf'>http://www.actuate.com/download/quick-start-install-ftype-linux.pdf</a>)
. Please review Step 1d since you are using an AWS EC2 instance.</p>
rmwalker
<p>Thanks Clement,</p>
<p> </p>
<p>So I "cheated" with a symlink when I saw the 32-bit libstdc++ req, but obviously I got caught ;-)</p>
<p> </p>
<p><em>error while loading shared libraries: libstdc++.so.6: wrong ELF class: ELFCLASS64</em></p>
<p> </p>
<p>Are there recommendations for obtaining this for Centos ec-2's? I've tried a bunch of things from google but it doesn't appear that amazon's yum repo has it.</p>
<p> </p>
<p>Thanks</p>
rmwalker
<p>After installing compat-libstdc++-33, I got /usr/lib/libstdc++.so.5. I can't find anything about 32-bit libstdc++.so.6 on a google search, nor a newer version compat-libstdc++</p>
Clement Wong
<p>Which specific AMI did you use? We have tested with both Amazon and RedHat Linux AMIs.</p>
<p> </p>
<p>Is your EC2 in a VPC?</p>
<p> </p>
<p>What version of CentOS are you running? What's the output of "cat /etc/centos-release�</p>
<p> </p>
<p>What is the output of "yum install libstdc++.i686"?</p>
<p> </p>
<p>What is the output of "yum repolist all"?</p>
<p> </p>
<p>Have you tried "yum clean all"?</p>
rmwalker
<p><em><span style="font-size:10pt;">Which specific AMI did you use? We have tested with both Amazon and RedHat Linux AMIs.</span></em></p>
<p><span style="font-size:10pt;">3.2.39-6.88.amzn1.x86_64</span></p>
<p> </p>
<p><em>Is your EC2 in a VPC?</em></p>
<p><em>no</em></p>
<p> </p>
<p><em>What version of CentOS are you running? What's the output of "cat /etc/centos-release�</em></p>
<p>> cat /etc/centos-release<br>
cat: /etc/centos-release: No such file or directory</p>
<p> </p>
<p>>uname -a</p>
<p><span style="font-size:10pt;">Linux ip-X-X-X-X 3.2.39-6.88.amzn1.x86_64 #1 SMP Sat Mar 2 05:13:37 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux</span><br>
</p>
<p> </p>
<p><em>What is the output of "yum install libstdc++.i686"?</em></p>
<p>
</p>
<p>> yum list | grep libstdc++</p>
<p>compat-libstdc++-33.i686 3.2.3-69.7.amzn1
@amzn-main<
;br>
libstdc++44.x86_64 4.4.6-4.77.amzn1
@upgrade-main/2010
.11<br>
libstdc++46.x86_64 4.6.2-2.65.amzn1
@upgrade-main/2010
.11<br>
compat-libstdc++-33.x86_64 3.2.3-69.7.amzn1 amzn-main<br>
libstdc++-devel.noarch 4.8.2-3.19.amzn1 amzn-main<br>
libstdc++-docs.x86_64 4.8.2-7.87.amzn1 amzn-main<br>
libstdc++-static.noarch 4.8.2-3.19.amzn1 amzn-main<br>
libstdc++44.i686 4.4.6-4.81.amzn1 amzn-main<br>
libstdc++44.x86_64 4.4.6-4.81.amzn1 amzn-main<br>
libstdc++44-devel.x86_64 4.4.6-4.81.amzn1 amzn-main<br>
libstdc++44-static.x86_64 4.4.6-4.81.amzn1 amzn-main<br>
libstdc++46.i686 4.6.3-2.67.amzn1 amzn-main<br>
libstdc++46.x86_64 4.6.3-2.67.amzn1 amzn-main<br>
libstdc++46-devel.x86_64 4.6.3-2.67.amzn1 amzn-main<br>
libstdc++46-static.x86_64 4.6.3-2.67.amzn1 amzn-main<br>
libstdc++47.i686 4.7.2-8.72.amzn1 amzn-main<br>
libstdc++47.x86_64 4.7.2-8.72.amzn1 amzn-main<br>
libstdc++47-devel.x86_64 4.7.2-8.72.amzn1 amzn-main<br>
libstdc++47-static.x86_64 4.7.2-8.72.amzn1 amzn-main<br>
libstdc++48.i686 4.8.2-7.87.amzn1 amzn-main<br>
libstdc++48.x86_64 4.8.2-7.87.amzn1 amzn-main<br>
libstdc++48-devel.x86_64 4.8.2-7.87.amzn1 amzn-main<br>
libstdc++48-static.x86_64 4.8.2-7.87.amzn1 amzn-main<br>
</p>
<p> </p>
<p><em>What is the output of "yum repolist all"?</em></p>
<p>
</p>
<p>repo id repo name status<br>
amzn amzn-v0.9-Base disabled<br>
amzn-debuginfo amzn-v0.9-debuginfo disabled<br>
amzn-main amzn-main-Base enabled: 4,801<br>
amzn-main-debuginfo amzn-main-debuginfo disabled<br>
amzn-nosrc amzn-nosrc-Base disabled<br>
amzn-preview amzn-preview-Base disabled<br>
amzn-preview-debuginfo amzn-preview-debuginfo disabled<br>
amzn-updates amzn-updates-Base enabled: 1,361<br>
amzn-updates-debuginfo amzn-updates-debuginfo disabled<br>
jpackage-fc JPackage (free) for Fedora Core latest disabled<br>
jpackage-fc-updates JPackage (free) for Fedora Core latest disabled<br>
jpackage-generic JPackage (free), generic enabled: 2,485+822<br>
jpackage-generic-nonfree JPackage (non-free), generic disabled<br>
jpackage-generic-nonfree-updates JPackage (non-free), generic disabled<br>
jpackage-generic-updates JPackage (free), generic enabled: 9+20<br>
jpackage-rhel JPackage (free) for Red Hat Enterprise Linux latest enabled: 8+1<br>
jpackage-rhel-updates JPackage (free) for Red Hat Enterprise Linux latest disabled<br>
newrelic New Relic packages for Enterprise Linux 5 - x86_64 enabled: 23<br>
repolist: 8,687</p>
<p> </p>
<p><em>Have you tried "yum clean all"?</em></p>
<p>no, should I?</p>
Clement Wong
<p>I just tested this on AMI (ami-d13845e1), "Amazon Linux AMI 2014.03.2 (HVM").</p>
<p> </p>
<p>Try "<strong>sudo yum install libstdc++47.i686</strong>". Looks like Amazon Linux requires a rev number it the library names unlike CentOS which it is based on.<br><br>
If you "ls -l /usr/lib/libstd*", you should see that the library is installed.</p>
<pre class="_prettyXprint">
lrwxrwxrwx 1 root root 19 Aug 12 23:28 libstdc++.so.6 -> libstdc++.so.6.0.17
-rwxr-xr-x 1 root root 922216 Mar 19 2013 libstdc++.so.6.0.17
</pre>
<p>Then, I was able to install, start iHub F-Type and get to the activation/welcome page.<br><br>
</p>
rmwalker
<p>I have been out of the office, and just saw this - it worked great, thanks Clement!</p>