Search Engine: Elastic

Article ID: 132004, created on Jan 3, 2018, last review on Jan 4, 2018

  • Applies to:
  • Operations Automation 7.2
  • Operations Automation 6.0


Webhosting Plesk tasks periodically fail with the following error message:

"code": 500,
"error": "Rest::RestException",
"message": "Connection error: "Empty reply from server". Was trying to connect to \"\".",
"http_request": "DELETE /web/SiteWeb/47d95a0a-...-fba21ff01b32"

Webhosting Plesk management node /var/log/shm-dispatcher/dispatcher.log error:

dispatcher_exceptions.CRITICAL: Execution context [DELETE (ID: 6d3a37...ed7de)]
Exception Rest\RestException occurred: "Connection error: "Empty reply from server".
Was trying to connect to "".
At /opt/shm-dispatcher/vendor/odin/aps/2/apsc.php line 398.
#0 /opt/shm-dispatcher/vendor/odin/aps/2/apsc.php(940): APS\Proto->sendRequest('GET', 'aps/2/resources...')
#1 /opt/shm-dispatcher/vendor/odin/aps/2/aps.php(742): APS\ControllerProxy->getResource('47d95a0a-af73-4...')

I.e. Webhosting Plesk management node cannot reach APSC interface on OA management node sometimes.

Also, in case OA Management Node is based on VZ Container architecture, /proc/user_beancounters file ( as on example below) contains non-zero failures count:

[root@osscore ~]# cat /proc/user_beancounters 
Version: 2.5
uid       resource   held   maxheld   barrier   limit   failcnt
5363854:  kmemsize   60604  60852     9223307   922307  0
          physpages  47032  47137     62956     62956   143
          vmguarpages  0     0        62356     62356   0
          oomguarpages 493  40227     62456     62456   70

Column name failcnt stands for failures counter.


Lack of OA Management Node resources.


Adjust the following parameter values which have non-zero failures count:

  • physpages: overall amount of RAM set for container.
  • oomguarpages: guaranteed amount of RAM (measured in 4kb blocks), exceeding which will cause OOM outage.

Refer to the Virtuozzo Users Guide for additional information and commands.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 31987597efff5a3a9ce779cc203bbe5e 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF