Search Engine: Elastic

Article ID: 130592, created on Apr 7, 2017, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3
  • Operations Automation 6.0
  • Operations Automation 5.5


IM server does not respond.

# curl -uadmin:******  -X GET http://192.168.xx.2:4465/paci/v1.0/vm2vf
curl: (7) couldn't connect to host

OACI IM log contains the error:

2015-06-21 14:10:04,363 () ERROR InstanceManager [RequestController-2] - Uncaught exeception encountered in thread: Thread[RequestController-2,10,main] java.lang.OutOfMemoryError: unable to create new native thread 
at java.lang.Thread.start0(Native Method) ~[na:1.6.0_45]
    at java.lang.Thread.start(Unknown Source) ~[na:1.6.0_45]


The underlying OS did not allow OACI service to create a new thread due to the nproc limit of PACI user.


  1. Set nproc limits for PACI user as unlimited in /etc/security/limits.d/90-nproc.conf:

    # Default limit for number of user's processes to prevent
    # accidental fork bombs.
    # See rhbz #432903 for reasoning.
    *          soft    nproc     1024
    root       soft    nproc     unlimited
    PACI       soft    nproc     unlimited
  2. Restart OACI IM services per the article: How to restart OACI Instance Manager services?

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e dd79f16c76b9dca75205ab5e9f5465ea 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF