Search Engine: Elastic

Article ID: 123722, created on Nov 28, 2014, last review on Aug 24, 2016

  • Applies to:
  • Odin Business Automation Standard


I have a Container on one of Virtuozzo nodes registered in OBAS that in not present neither on its node nor in the Conflicts Resolver.


  1. Task Detected newly appeared Virtuozzo VE conflicts have not yet collected conflicts for a hardware node where the container is located.

  2. PVA Agent reached user_session_limit parameter and can not create more sessions on a hardware node where the container is located.


  1. By default the task runs once in four hours. Please wait for four hours for the Container to appear in Conflicts Resolver or just run the task manually if you need to speed it up.

    You can also increase the task frequency from default four hours to a lesser value if the issue is regular.

  2. Check the amount of sessions and apply a solution from the following KB article.

See also

A task fails with error: "500 read timeout at"

Virtuozzo node becomes Unavailable regularly

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF