Resolution
UI (Graphical User Interface, Control Panel):
Linux:
Since OA version 7.0:
# service pau restart
Before OA 7.0:
# /etc/init.d/pemui restart
Windows:
To restart the OA UI, use the following commands:
net stop pemui
net start pemui
Management Node:
Linux:
Since OA version 7.0:
# service pa-agent stop
# service pau stop
# service pau start
# service pa-agent start
Note: If any of the above services fails to start, check this article for possible solution:
For OA version 6.0:
# service pem stop
# service pau stop
# service pau start
# service pem start
For OA version 5.5 and earlier:
# service pem restart
This is a graceful restart. If this does not work, OA can be restarted forcibly:
~# killall -9 pem pleskd SoLoader
~# service pem start
These commands should be executed on the Management Node (MN), also known as the OA Core or OA.
Windows:
For OA version 6.0:
net stop pem
net stop pau
net start pau
net start pem
For OA version 5.5 and earlier:
net stop pem
net start pem
If you encounter issues restarting OA, you can kill all SoLoader.exe processes that are still running using Windows Task Manager or any other appropriate tool.
Note: If you restarted the OA Management Node service, it is recommended that you restart the OA UI service as well (see above for instructions).
OA Agent on a managed node:
Linux:
Each OA-managed host has POA Agent installed. To restart it, use the following commands:
Since OA version 7.0:
# service pa-agent restart
For OA version 6.0 and earlier:
~# service pem restart
Windows:
To restart OA Agent, execute the following commands:
net stop pem
net start pem
PVA Agent on a managed Parallels Virtuozzo Containers (PVC) node:
Linux:
# pvaagent restart
Windows:
net stop pvaagent
net start pvaagent