terminate called after throwing an instance of 'RWBoundsErr'

I get the above error at the end of the install and on subsequent startups. Postgres is running, but nothing else.
 
system:
CentOS 6.5 in a KVM (Proxmox) Virtual Machine
10 GB RAM
2-core CPU
 
any ideas?

Find more posts tagged with

Comments

JFreeman

Hi Steve,
 
Could you please provide the output of: ldd ihubd
 
This could be related to a missing dependency issue.

beitinsw

<pre class="_prettyXprint _linenums:0">ldd ihubd
 linux-gate.so.1 => (0x00481000)
 libxerces-c1_4.so => not found
 libsoapendpoint.so => not found
 libservermon.so => not found
 libsoapserializer.so => not found
 libacrwtool.so => not found
 libutil.so => not found
 libutilserver.so => not found
 libosd.so => not found
 libi18n.so => not found
 libacnls.so => not found
 libnsl.so.1 => /lib/libnsl.so.1 (0x00fc8000)
 libdl.so.2 => /lib/libdl.so.2 (0x00f88000)
 librt.so.1 => /lib/librt.so.1 (0x008a4000)
 libpthread.so.0 => /lib/libpthread.so.0 (0x005ac000)
 libcrypto.so.1.0.0 => not found
 libssl.so.1.0.0 => not found
 libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00cf2000)
 libm.so.6 => /lib/libm.so.6 (0x00f50000)
 libc.so.6 => /lib/libc.so.6 (0x005c7000)
 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00a6d000)
 /lib/ld-linux.so.2 (0x00368000)

</pre>

JFreeman

Thank you for the requested ldd output. Based on this output, I do not believe dependencies are a factor for this behavior as the libs which are not found are not required dependencies for core operations.
 
I believe this may be related to the virtualization software you are using (ProxMox). Since this post, I have performed a CentOS 6.5 minimal installation in a VMWare environment and successfully installed BIRT iHub F-Type.
 
I am working towards downloading/configuring a ProxMox environment for testing. In parallel, could you perform the installation in a different virtualization platform such as VMWare Player or VMWare Workstation and let me know the result?

Thanks.

denos

This issue is due to iHub processor checks -- generic KVM, VMware, etc. processors designed to make VMs portable will not work. You need to make sure the virtualization layer is passing through the host's raw processor details as iHub is presumably looking for "AMD" or "Intel".
 
To fix in Proxmox: Select the host, click the Hardware tab, double click processors, set type to "Host".
 
Hopefully a future release removes this problematic requirement.

JFreeman

Thank you for the details on your workaround in a Proxmox environment.
 
The root cause of the issue is related to some logic performed on the physical id output of the processor and not necessarily that it is explicitly looking for "AMD" or "Intel".
 
To my knowledge this issue should be resolved in the most recent iHub 3.1 release.