Article ID: 127260, created on Oct 27, 2015, last review on Oct 27, 2015

  • Applies to:
  • Operations Automation

Symptoms

OACI IM fails to start with the following message:

[root@im ~]# /etc/init.d/PACI-im status
vm2vf-daemon (pid 904 901) is running...
im-daemon is stopped
[root@im ~]# /etc/init.d/PACI-im start
Reusing running vm2vf service (901)
Starting PACI IM service: PACI: Instance Manager failed
PACI: IM failing too often, stopping

Cause

Inconsistent cache of terracota.

Resolution

After stopping the services, clear terracotta cache.

[root@im ~]# /etc/init.d/PACI-im upgrade-stop
[root@im ~]# /etc/init.d/terracotta stop
[root@im ~]# /etc/init.d/activemq-server stop
[root@im ~]# /etc/init.d/terracotta clearcache
[root@im ~]# /etc/init.d/activemq-server start
[root@im ~]# /etc/init.d/terracotta start
[root@im ~]# /etc/init.d/PACI-im start
Starting PACI vm2vf service:                               [  OK  ]
Starting PACI IM service:                                  [  OK  ]

upgrade-stop above enforces a timeout of 5 minute.

Check OACI IM log (/var/log/IM/PACI-im-startup.log) for

To avoid this problem in future make sure that RAM is 8 GB or more and swap is double the size of RAM as mentioned in the Hardware Requirements

[root@im ~]# free -m
         total       used       free     shared    buffers     cached
Mem:          8192       1456       6735          0          0        270
-/+ buffers/cache:       1185       7006
Swap:          512          0        512 <---

Search Words

paci-im

oaci-im

paci

-

PACI IM manager not starting

oaciim

POA PACI

paciim

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF