Article ID: 118808, created on Nov 22, 2013, last review on Oct 8, 2015

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Operations Automation 5.3


You cannot install/remove packages on a node in the Operations Automation (OA) Provider Control Panel (PCP), or you are unable to remove the node from OA as the corresponding task keeps failing with this error:

Output  : Other packaging operation is already in progress on host <hostname>


  • The necessary package operations on the host have not completed yet. Once they do, the task will complete successfully.
  • The install/remove operation has finished on the destination node, but POA did not receive a callback saying that the job is done. As a result, it still reports that the "package operations on the host have not completed yet."


Wait for the task to complete successfully. It may take from several minutes to an hour, depending on server load.

To check if there are any active package operations running on the node, log in to the destination node and run the following:

# ps aux | egrep 'yum|dpkg|apt' | grep -v 'grep'

On a Windows target node, open Task Manager and check for msiexec processes.

If there are no such processes, it means that the package operation completed but OA did not receive the callback. As a result, the package operation is stuck in the OA queue and a restart of the PEM service on the OA management node is required.

# service pem restart
Stopping pleskd:                                           [  OK  ]
Starting pleskd:                                           [  OK  ]

See KB #4642 regarding restarts of POA services.

After restarting pem service, it will be possible to install/remove the package, or to finish the cleanup packages task on the host.

Search Words

Install package IIsWebServer


Applications tab is empty for Hardware Nodes

cleanup packages on host

Other packaging operation is already in progress

creating a mailbox fialed

pleskd- from repo-id-39 has depsolving problems

creating a mailbox failed


a8cdca46e4357a6e38fded820770e272 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899 5b048d9bddf8048a00aba7e0bdadef37 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF