Resolved psa binary location on Debian 11 ?

[Pascal_Netenvie]

Server operating system version

Debian 11.6

Plesk version and microupdate number

18.0.50 u2

Hello,
On Debian 9 & 10 i can use this command :
/etc/init.d/psa stopall

But on Debian 11 it's not working ...
Where is that binary now ?

 

[Peter Debik]

You can use
# service psa stopall
instead.

 

[Pascal_Netenvie]

Already tried before posting ... No it don't work ...

 

[Peter Debik]

As I tested it on Debian 11, maybe something is wrong with the installation in general? Have you tried to (as root) plesk repair installation?

 

[Pascal_Netenvie]

I just runned it and this is output :

Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

 Finishing up upgrade procedures and rerunning previously failed upgrade actions...

**** Product repair started.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

 Trying to start service mariadb... active
done
 Trying to establish test connection... connected
done
 Trying to find Plesk database psa... version is 018000000
 Trying to backup MySQL database... done
 MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.18.0.50-18.0.50.20230223-114909.dump.gz
 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
 Trying to add supplementary group 'lock-manager' for user 'psaadm'...  already there
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
 Trying to backup MySQL database... done
 MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.18.0.50-18.0.50.20230223-114912.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Dropping phpMyAdmin '' DB and '' DB user

Warning: phpMyAdmin was configured without configuration storage in database

===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.50-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
 Reconfiguring mail subsystem...
 Reconfiguring Apache web server...
 Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
 Reconfiguring AWStats web statistics...
 Reconfiguring WatchDog...
 Restoring SELinux contexts...
Synchronizing state of networking.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable networking
insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
insserv: FATAL: service mountkernfs has to be enabled to use service networking
insserv: FATAL: service urandom has to be enabled to use service networking
 Reconfiguring SSL ciphers and protocols...
 Regenerating web servers' configuration files...
 Cleaning active Panel sessions...
 Fixing permissions on Panel packages files
Downloading file products.inf3: 0%
...
...
...
Bootstrapper repair finished.
If problems persist, please check installer logs ('/var/log/plesk/install/plesk_18.0.50_repair.log' and '/var/log/plesk/install/plesk_18.0.50_repair_problems.log') for errors.
If you can't resolve the issue on your own, please address Plesk support.
*****  problem report *****
Warning: phpMyAdmin was configured without configuration storage in database

And after that "service psa stopall' command still don't work ...

 

[Pascal_Netenvie]

I installed Plesk on this server with standard procedure from Plesk website ...

 

[Peter Debik]

@Pascal_Netenvie I was wrong. Sorry for that. I tested "service psa status", because I did not want to kill my test instance altogether. The status indeed worked, but the "service psa stopall" had been removed since version 18.0.46 for various reasons. One of them being that the command did not stop some services reliably so that users did not get the result that they could legitimately expect from a "stopall".

My more knowledgable colleagues gave me a workaround that I'd like to pass on to you here. You can use

# /usr/lib/plesk-9.0/psa_service stopall

We have an open case [PPP-57841] that a new function shall replace the old one, but as other tasks with even higher priority had to be completed first, this had to be postponed. Plesk is aware that this function is needed, so we'll have a replacement in a future update.

 

[Pascal_Netenvie]

Ok, thanks.
So it work also to startall ?
Like :

# /usr/lib/plesk-9.0/psa_service startall

 

[Pascal_Netenvie]

Yes it run ok !