• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question How to restart the Plesk service from command line

NIEL

New Pleskian
Server operating system version
centos 7
Plesk version and microupdate number
Plesk Obsidian for Linux
hi guys
before i was using this command to Start, stop, or restart all plesk services like mysql, apache nginx, php etc now its no more working so what is the alternate command to restart psa services
services psa stopall
services psa restart
 
... but since Plesk 18.0.46 that option is deprecated and will be replaced with a new command in a future Plesk version. The reason for it is that the expected "stopall" does not truly stop all, but only part of the services involved. These are not reliably stopped:
  • nginx
  • PHP-FPM
  • plesk-web-socket
  • plesk-task-manager
  • sw-engine
  • sw-cp-server
  • plesk-repaird
  • xinetd (FTP & Poppassd)
 
... but since Plesk 18.0.46 that option is deprecated and will be replaced with a new command in a future Plesk version. The reason for it is that the expected "stopall" does not truly stop all, but only part of the services involved. These are not reliably stopped:
  • nginx
  • PHP-FPM
  • plesk-web-socket
  • plesk-task-manager
  • sw-engine
  • sw-cp-server
  • plesk-repaird
  • xinetd (FTP & Poppassd)

In addition to what @Peter Debik stated, one has to ask themselves what one wants to achieve : restart Plesk server or restart THE server.

In most cases, the restart of Plesk server is a poor substitute for rebooting THE server OR for restarting individual services.

In essence, it is good practice to identify the individual services that have to be restarted - just try to restart them on an individual basis first!!!

If that does not work, any Plesk based restart is surely not working either ....... and hence the server (soft) reboot becomes a good option.

Again, it has to be emphasized : first attempt to restart individual services first.

Kind regards.....
 
... but since Plesk 18.0.46 that option is deprecated and will be replaced with a new command in a future Plesk version. The reason for it is that the expected "stopall" does not truly stop all, but only part of the services involved. These are not reliably stopped:
  • nginx
  • PHP-FPM
  • plesk-web-socket
  • plesk-task-manager
  • sw-engine
  • sw-cp-server
  • plesk-repaird
  • xinetd (FTP & Poppassd)
For other actions, please try to use systemctl.
[root@deadbox~]# clear
[root@deadbox ~]# service psa stopall
The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl.
 
Back
Top