Symptoms
OACI does not send notification regarding VE creation.
In /var/log/pa/vps.log
the callback timeout can be found:
2017-05-31 17:47:28,549 (CALLBACK_434301a9-c414-4dfe-86f3-d38ca774062f) INFO CallbackProxy [ActiveMQ Session Task-9875] - Invoking com.parallels.c2u.vm2vf.corba.Vm2VfAuxiliaryOperations.set_handle(...) for reqId = 70864, ctxId = (02d9c95e-2ff8-4ff8-9fac-2f2f66c4eb41)
...
2017-05-31 17:52:32,878 () INFO CallbackProxy [pool-5-thread-3] - Invoking com.parallels.c2u.vm2vf.corba.AbortableOperations.timeout(...) for reqId = 70864, ctxId = (02d9c95e-2ff8-4ff8-9fac-2f2f66c4eb41)
VM2VF
callback timeout is more than 5 minutes:
[root@oaci-im ~]# grep callback-timeout /usr/local/share/PACI-im/IM-config.xml
<vm2vf callback-timeout-min="600" log="true" mode="on-node">
Cause
VM2VF
service sends periodic notifications regarding operation status.
If the time between such notifications became higher than the maxInactivityDuration
parameter, the protocol error
will be met during next report:
2017-05-31 17:52:53,391 (CALLBACK_434301a9-c414-4dfe-86f3-d38ca774062f) WARN Vm2VfApiOperationsReactor [ActiveMQ Session Task-9879] - protocol error particular callback already expired: interface com.parallels.c2u.vm2vf.corba.CallbackWithCapacityAndId
2017-05-31 17:52:53,392 () INFO Vm2VfApiOperationsReactor [ActiveMQ Session Task-9879] - in-bound request XML
Usually such behaviour points on the performance issues on the Virtuozzo node.
The default value of the parameter maxInactivityDuration is 5 minutes.
This time limit should be enough to send the notification from the VM2VF
side.
Resolution
If the performance issues cannot be resolved right away, the maxInactivityDuration
parameter may be increased.
It is located in the broker
block of the main Instance Manager configuration file:
[root@oaci-im ~]# grep maxInactivityDuration /usr/local/share/PACI-im/IM-config.xml
<broker data-dir="activemq-data/kahadb" embedded="true" maxConnections="100" maxOutstandingMessages="-1" maxSessionsPerConnection="50" uri="tcp://0.0.0.0:61616" uri_="failover:(tcp://localhost:61616?trace=false&soTimeout=60000&wireFormat.maxInactivityDuration=300000)?timeout=5000&maxReconnectAttempts=-1" />
Value should be set in the milliseconds.
The adjusted value should not exceed 600000
ms, otherwise this may led to the system instability.
Once the value is changed, the Instance manager should be restarted.