Search Engine: Elastic

Article ID: 133372, created on Nov 5, 2018, last review on Nov 5, 2018

  • Applies to:
  • Operations Automation 7.4


Provisioning "Panel_6_1" for APS application Cloud Infrastructure task fails with:

APS Application Error: 
500 Internal Server Error
[ApplicationUnknownError] [IM] Exit code != 0.

Body: {
"message": "[IM] Exit code != 0",
"error": "ApplicationUnknownError",
"http_request": "POST /vps/api/panels"

The following error could be found in /var/log/pa/vps.log on Instance Manager node :

`2018-11-05 07:52:51,827 () INFO  Vm2VfApiOperationsReactor [ActiveMQ Session Task-8346] - in-bound request XML
<Envelope xmlns=""><correlationId>CALLBACK_0f4a31ce-c682-4f2b-8ddb-286afdcf89d9</correlationId><kind>1204</kind><payload>
// callback exec_cb exec_done
  "rc" : 0,
  "node_timestamp" : 3298660092525067826,
  "exec_rc" : 1,
  "stdout_str" : null,
  "stderr_str" : "Job for nginx.service failed because the control process exited with error code. See \"systemctl status nginx.service\" and \"journalctl -xe\" for details.\n"

It is not possible to start nginx service on affected server:

# systemctl status nginx.service
● nginx.service - Startup script for nginx service
   Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2018-11-05 02:28:08 EST; 27s ago
  Process: 7963 ExecStartPre=/usr/bin/test $NGINX_ENABLED = yes (code=exited, status=2)


Software-related issue on Plesk application side.


Contact Plesk support to track the status of the issue.

The following workaround could applied to fix the issue:

Connect to the affected virtual server and execute the following command:

# plesk sbin nginxmng --enable

Check if the nginx service started:

# service nginx status
● nginx.service - Startup script for nginx service
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-11-05 03:23:41 EST; 4min 36s ago

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 55fe109b4b4fe3fbb893f22dbb85a41a 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF