Search Engine: Elastic

Article ID: 131393, created on Aug 31, 2017, last review on Aug 31, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1

Symptoms

After installing a new version of paci_im package in scope of OA update or upgrade, OACI Instance Manager service does not start. The following message is recorded in /var/log/pa/vps.log:

2017-08-31 15:27:55,571 () ERROR JMSModule [main] - Failed to create embedded ActiveMQ broker
java.io.IOException: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.net.BindException: Address already in use (Bind failed)
        at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:34) ~[activemq-client-5.14.0.jar:5.14.0]
        at org.apache.activemq.transport.tcp.TcpTransportServer.bind(TcpTransportServer.java:143) ~[activemq-client-5.14.0.jar:5.14.0]
        at org.apache.activemq.transport.tcp.TcpTransportFactory.doBind(TcpTransportFactory.java:62) ~[activemq-client-5.14.0.jar:5.14.0]
        at org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40) ~[activemq-broker-5.14.0.jar:5.14.0]

Instance Manager node has paci_im and paci_mq packages installed.

Cause

paci_mq package is obsolete since OA 7.0 and should not exist on the Instance Manager node. The dependency on paci_im package remained since 6.0, and this is recognized as a software issue CCU-13088.

Resolution

Contact Odin Technical Support to apply the resolution and prevent the issue from reoccurrence.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF