• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 115609, created on Feb 27, 2013, last review on May 11, 2014

  • Applies to:
  • Operations Automation 5.4
  • Operations Automation 5.3


After upgrading Java on the Instance Manager node, the PACI-im service does not start:
[root@api ~]# /etc/init.d/terracotta restart
2013-02-03 15:39:36,910 INFO - Terracotta 3.6.1, as of 20120125-115706 (Revision 19619 by cruise@rh5vmo105.terracotta.lan from 3.6.1)
2013-02-03 15:39:36,924 INFO - No host or port provided. Stopping the Terracotta server instance at 'localhost', port 9520 by default.
Stopping PACI Instance Manager                          [ OK ]
Stopping PACI vm2vf daemon/etc/init.d/PACI-im: line 200: kill: (22720) - No such process
                                                        [ OK ]
Starting PACI vm2vf daemon                              [ OK ]
Starting PACI Instance Manager                          [ FAIL ]

A similar exception is observed in /var/log/IM/PACI-im-startup.log:
Caused by: com.tc.config.schema.setup.ConfigurationSetupException:
Incompatible boot jar JVM version; expected 'hotspot_linux_160_24' but was (in boot jar) 'hotspot_linux_160_22'; Please regenerate the DSO boot jar to match this VM, or switch to a VM compatible with this boot jar


Run the following command on the Instance Manager node:
env JAVA_HOME=/usr/lib/jvm/jre-1.6.0-openjdk.x86_64 /usr/local/terracotta-3.6.1/platform/bin/make-boot-jar.sh

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e a8cdca46e4357a6e38fded820770e272 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF