• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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